summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorAhmad Fatoum <ahmad@a3f.at>2019-11-20 09:35:36 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2019-11-25 09:07:56 +0100
commit350bcb29ec09650bbbbf38683abb25610bd22126 (patch)
tree0b83f5f61ade3894d0539df296ba5b1613f14fd3 /include/linux
parent429c1938ce496fa90a5ddd5d3f1ca6842b58f35f (diff)
downloadbarebox-350bcb29ec09650bbbbf38683abb25610bd22126.tar.gz
barebox-350bcb29ec09650bbbbf38683abb25610bd22126.tar.xz
remoteproc: register a device for new remoteproc instances
struct rproc has a device_d dev field, but so far it was unregistered. The implementation had a few downsides: - dev_printf prints NULL, because the unique_name of the device is NULL - The name used by firmwareload is the device tree node's name, which might be unnecessarily verbose, e.g. mlahb:m4@10000000.of - All remoteproc devices are given the same (unused) name and index Fix these by registering a device for the remoteproc and using it where appropriate. While at it, allow the remoteproc name to come from a device tree alias as well. This breaks user behavior in that firmwareload now uses the alias or remoteprocN to reference the remoteproc instance. This is probably acceptable as the driver is a very recent addition. Cc: Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/remoteproc.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
index feee9ee4ee..c6264d1c0a 100644
--- a/include/linux/remoteproc.h
+++ b/include/linux/remoteproc.h
@@ -38,7 +38,6 @@ struct rproc {
void *priv;
struct rproc_ops *ops;
struct device_d dev;
- int index;
void *fw_buf;
size_t fw_buf_ofs;