]> git.kernelconcepts.de Git - karo-tx-linux.git/commit
greybus: loopback: move sysfs entries to /sys/bus/greybus/devices/endo0
authorBryan O'Donoghue <bryan.odonoghue@linaro.org>
Wed, 23 Sep 2015 16:31:31 +0000 (09:31 -0700)
committerGreg Kroah-Hartman <gregkh@google.com>
Wed, 23 Sep 2015 19:46:16 +0000 (12:46 -0700)
commitf01f7a9851f9c75467373ba7797394dba91825da
treef95932767dc190e79e679823f7a24504e85d358e
parent6872c46129d00d0fcc0b32d73498fc86d6823137
greybus: loopback: move sysfs entries to /sys/bus/greybus/devices/endo0

Currently we have sysfs entries that are created when the first incoming
connection is created as sub-nodes of the module associated with that
connection e.g. /sys/bus/grebus/devices/endo0:X where X is the module
identifier associated with the new connection. This is conceptually
incorrect since the sysfs entries we create actually aren't bound to a
module. Depending on the order connections are brought up we can also have
a situation where /sys/bus/greybus/devices/endo0:X has high-level control
sysfs data-points but /sys/bus/greybus/devices/endo0:Y does not. Rather
than needlessly replicate data-points across each endo0:X, endo0:Y, endo0:Z
sysfs directories it is more sensible to locate the entries in
/sys/bus/greybus/devices/endo0.

Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Reviewed-by: Patrick Titiano <ptitiano@baylibre.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
drivers/staging/greybus/loopback.c