0001 What: /sys/bus/rpmsg/devices/.../name
0002 Date: June 2011
0003 KernelVersion: 3.3
0004 Contact: Ohad Ben-Cohen <ohad@wizery.com>
0005 Description:
0006 Every rpmsg device is a communication channel with a remote
0007 processor. Channels are identified with a (textual) name,
0008 which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in
0009 rpmsg.h).
0010
0011 This sysfs entry contains the name of this channel.
0012
0013 What: /sys/bus/rpmsg/devices/.../src
0014 Date: June 2011
0015 KernelVersion: 3.3
0016 Contact: Ohad Ben-Cohen <ohad@wizery.com>
0017 Description:
0018 Every rpmsg device is a communication channel with a remote
0019 processor. Channels have a local ("source") rpmsg address,
0020 and remote ("destination") rpmsg address. When an entity
0021 starts listening on one end of a channel, it assigns it with
0022 a unique rpmsg address (a 32 bits integer). This way when
0023 inbound messages arrive to this address, the rpmsg core
0024 dispatches them to the listening entity (a kernel driver).
0025
0026 This sysfs entry contains the src (local) rpmsg address
0027 of this channel. If it contains 0xffffffff, then an address
0028 wasn't assigned (can happen if no driver exists for this
0029 channel).
0030
0031 What: /sys/bus/rpmsg/devices/.../dst
0032 Date: June 2011
0033 KernelVersion: 3.3
0034 Contact: Ohad Ben-Cohen <ohad@wizery.com>
0035 Description:
0036 Every rpmsg device is a communication channel with a remote
0037 processor. Channels have a local ("source") rpmsg address,
0038 and remote ("destination") rpmsg address. When an entity
0039 starts listening on one end of a channel, it assigns it with
0040 a unique rpmsg address (a 32 bits integer). This way when
0041 inbound messages arrive to this address, the rpmsg core
0042 dispatches them to the listening entity.
0043
0044 This sysfs entry contains the dst (remote) rpmsg address
0045 of this channel. If it contains 0xffffffff, then an address
0046 wasn't assigned (can happen if the kernel driver that
0047 is attached to this channel is exposing a service to the
0048 remote processor. This make it a local rpmsg server,
0049 and it is listening for inbound messages that may be sent
0050 from any remote rpmsg client; it is not bound to a single
0051 remote entity).
0052
0053 What: /sys/bus/rpmsg/devices/.../announce
0054 Date: June 2011
0055 KernelVersion: 3.3
0056 Contact: Ohad Ben-Cohen <ohad@wizery.com>
0057 Description:
0058 Every rpmsg device is a communication channel with a remote
0059 processor. Channels are identified by a textual name (see
0060 /sys/bus/rpmsg/devices/.../name above) and have a local
0061 ("source") rpmsg address, and remote ("destination") rpmsg
0062 address.
0063
0064 A channel is first created when an entity, whether local
0065 or remote, starts listening on it for messages (and is thus
0066 called an rpmsg server).
0067
0068 When that happens, a "name service" announcement is sent
0069 to the other processor, in order to let it know about the
0070 creation of the channel (this way remote clients know they
0071 can start sending messages).
0072
0073 This sysfs entry tells us whether the channel is a local
0074 server channel that is announced (values are either
0075 true or false).
0076
0077 What: /sys/bus/rpmsg/devices/.../driver_override
0078 Date: April 2018
0079 KernelVersion: 4.18
0080 Contact: Bjorn Andersson <bjorn.andersson@linaro.org>
0081 Description:
0082 Every rpmsg device is a communication channel with a remote
0083 processor. Channels are identified by a textual name (see
0084 /sys/bus/rpmsg/devices/.../name above) and have a local
0085 ("source") rpmsg address, and remote ("destination") rpmsg
0086 address.
0087
0088 The listening entity (or client) which communicates with a
0089 remote processor is referred as rpmsg driver. The rpmsg device
0090 and rpmsg driver are matched based on rpmsg device name and
0091 rpmsg driver ID table.
0092
0093 This sysfs entry allows the rpmsg driver for a rpmsg device
0094 to be specified which will override standard OF, ID table
0095 and name matching.
