96 lines · plain
1What: /sys/bus/rpmsg/devices/.../name2Date: June 20113KernelVersion: 3.34Contact: Ohad Ben-Cohen <ohad@wizery.com>5Description:6 Every rpmsg device is a communication channel with a remote7 processor. Channels are identified with a (textual) name,8 which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in9 rpmsg.h).10 11 This sysfs entry contains the name of this channel.12 13What: /sys/bus/rpmsg/devices/.../src14Date: June 201115KernelVersion: 3.316Contact: Ohad Ben-Cohen <ohad@wizery.com>17Description:18 Every rpmsg device is a communication channel with a remote19 processor. Channels have a local ("source") rpmsg address,20 and remote ("destination") rpmsg address. When an entity21 starts listening on one end of a channel, it assigns it with22 a unique rpmsg address (a 32 bits integer). This way when23 inbound messages arrive to this address, the rpmsg core24 dispatches them to the listening entity (a kernel driver).25 26 This sysfs entry contains the src (local) rpmsg address27 of this channel. If it contains 0xffffffff, then an address28 wasn't assigned (can happen if no driver exists for this29 channel).30 31What: /sys/bus/rpmsg/devices/.../dst32Date: June 201133KernelVersion: 3.334Contact: Ohad Ben-Cohen <ohad@wizery.com>35Description:36 Every rpmsg device is a communication channel with a remote37 processor. Channels have a local ("source") rpmsg address,38 and remote ("destination") rpmsg address. When an entity39 starts listening on one end of a channel, it assigns it with40 a unique rpmsg address (a 32 bits integer). This way when41 inbound messages arrive to this address, the rpmsg core42 dispatches them to the listening entity.43 44 This sysfs entry contains the dst (remote) rpmsg address45 of this channel. If it contains 0xffffffff, then an address46 wasn't assigned (can happen if the kernel driver that47 is attached to this channel is exposing a service to the48 remote processor. This make it a local rpmsg server,49 and it is listening for inbound messages that may be sent50 from any remote rpmsg client; it is not bound to a single51 remote entity).52 53What: /sys/bus/rpmsg/devices/.../announce54Date: June 201155KernelVersion: 3.356Contact: Ohad Ben-Cohen <ohad@wizery.com>57Description:58 Every rpmsg device is a communication channel with a remote59 processor. Channels are identified by a textual name (see60 /sys/bus/rpmsg/devices/.../name above) and have a local61 ("source") rpmsg address, and remote ("destination") rpmsg62 address.63 64 A channel is first created when an entity, whether local65 or remote, starts listening on it for messages (and is thus66 called an rpmsg server).67 68 When that happens, a "name service" announcement is sent69 to the other processor, in order to let it know about the70 creation of the channel (this way remote clients know they71 can start sending messages).72 73 This sysfs entry tells us whether the channel is a local74 server channel that is announced (values are either75 true or false).76 77What: /sys/bus/rpmsg/devices/.../driver_override78Date: April 201879KernelVersion: 4.1880Contact: Bjorn Andersson <bjorn.andersson@linaro.org>81Description:82 Every rpmsg device is a communication channel with a remote83 processor. Channels are identified by a textual name (see84 /sys/bus/rpmsg/devices/.../name above) and have a local85 ("source") rpmsg address, and remote ("destination") rpmsg86 address.87 88 The listening entity (or client) which communicates with a89 remote processor is referred as rpmsg driver. The rpmsg device90 and rpmsg driver are matched based on rpmsg device name and91 rpmsg driver ID table.92 93 This sysfs entry allows the rpmsg driver for a rpmsg device94 to be specified which will override standard OF, ID table95 and name matching.96