diff options
| author | Anup Patel | 2018-03-23 17:11:17 +0100 |
|---|---|---|
| committer | Bjorn Andersson | 2018-04-26 01:59:53 +0200 |
| commit | 39e47767ec9b22f844c2a07c9d329256960d4021 (patch) | |
| tree | d34066f379c86a35f0a249af39046c784b6a850d /Documentation/ABI/testing/sysfs-bus-rpmsg | |
| parent | Linux 4.17-rc1 (diff) | |
| download | kernel-qcow2-linux-39e47767ec9b22f844c2a07c9d329256960d4021.tar.gz kernel-qcow2-linux-39e47767ec9b22f844c2a07c9d329256960d4021.tar.xz kernel-qcow2-linux-39e47767ec9b22f844c2a07c9d329256960d4021.zip | |
rpmsg: Add driver_override device attribute for rpmsg_device
This patch adds "driver_override" device attribute for rpmsg_device which
will allow users to explicitly specify the rpmsg_driver to be used via
sysfs entry.
The "driver_override" device attribute implemented here is very similar
to "driver_override" implemented for platform, pci, and amba bus types.
One important use-case of "driver_override" device attribute is to force
use of rpmsg_chrdev driver for certain rpmsg_device instances.
Signed-off-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Diffstat (limited to 'Documentation/ABI/testing/sysfs-bus-rpmsg')
| -rw-r--r-- | Documentation/ABI/testing/sysfs-bus-rpmsg | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-bus-rpmsg b/Documentation/ABI/testing/sysfs-bus-rpmsg index 189e419a5a2d..990fcc420935 100644 --- a/Documentation/ABI/testing/sysfs-bus-rpmsg +++ b/Documentation/ABI/testing/sysfs-bus-rpmsg @@ -73,3 +73,23 @@ Description: This sysfs entry tells us whether the channel is a local server channel that is announced (values are either true or false). + +What: /sys/bus/rpmsg/devices/.../driver_override +Date: April 2018 +KernelVersion: 4.18 +Contact: Bjorn Andersson <bjorn.andersson@linaro.org> +Description: + Every rpmsg device is a communication channel with a remote + processor. Channels are identified by a textual name (see + /sys/bus/rpmsg/devices/.../name above) and have a local + ("source") rpmsg address, and remote ("destination") rpmsg + address. + + The listening entity (or client) which communicates with a + remote processor is referred as rpmsg driver. The rpmsg device + and rpmsg driver are matched based on rpmsg device name and + rpmsg driver ID table. + + This sysfs entry allows the rpmsg driver for a rpmsg device + to be specified which will override standard OF, ID table + and name matching. |