Lines Matching +full:rpmsg +full:- +full:channel +full:- +full:name
1 What: /sys/bus/rpmsg/devices/.../name
4 Contact: Ohad Ben-Cohen <ohad@wizery.com>
6 Every rpmsg device is a communication channel with a remote
7 processor. Channels are identified with a (textual) name,
9 rpmsg.h).
11 This sysfs entry contains the name of this channel.
13 What: /sys/bus/rpmsg/devices/.../src
16 Contact: Ohad Ben-Cohen <ohad@wizery.com>
18 Every rpmsg device is a communication channel with a remote
19 processor. Channels have a local ("source") rpmsg address,
20 and remote ("destination") rpmsg address. When an entity
21 starts listening on one end of a channel, it assigns it with
22 a unique rpmsg address (a 32 bits integer). This way when
23 inbound messages arrive to this address, the rpmsg core
26 This sysfs entry contains the src (local) rpmsg address
27 of this channel. If it contains 0xffffffff, then an address
29 channel).
31 What: /sys/bus/rpmsg/devices/.../dst
34 Contact: Ohad Ben-Cohen <ohad@wizery.com>
36 Every rpmsg device is a communication channel with a remote
37 processor. Channels have a local ("source") rpmsg address,
38 and remote ("destination") rpmsg address. When an entity
39 starts listening on one end of a channel, it assigns it with
40 a unique rpmsg address (a 32 bits integer). This way when
41 inbound messages arrive to this address, the rpmsg core
44 This sysfs entry contains the dst (remote) rpmsg address
45 of this channel. If it contains 0xffffffff, then an address
47 is attached to this channel is exposing a service to the
48 remote processor. This make it a local rpmsg server,
50 from any remote rpmsg client; it is not bound to a single
53 What: /sys/bus/rpmsg/devices/.../announce
56 Contact: Ohad Ben-Cohen <ohad@wizery.com>
58 Every rpmsg device is a communication channel with a remote
59 processor. Channels are identified by a textual name (see
60 /sys/bus/rpmsg/devices/.../name above) and have a local
61 ("source") rpmsg address, and remote ("destination") rpmsg
64 A channel is first created when an entity, whether local
66 called an rpmsg server).
68 When that happens, a "name service" announcement is sent
70 creation of the channel (this way remote clients know they
73 This sysfs entry tells us whether the channel is a local
74 server channel that is announced (values are either
77 What: /sys/bus/rpmsg/devices/.../driver_override
82 Every rpmsg device is a communication channel with a remote
83 processor. Channels are identified by a textual name (see
84 /sys/bus/rpmsg/devices/.../name above) and have a local
85 ("source") rpmsg address, and remote ("destination") rpmsg
89 remote processor is referred as rpmsg driver. The rpmsg device
90 and rpmsg driver are matched based on rpmsg device name and
91 rpmsg driver ID table.
93 This sysfs entry allows the rpmsg driver for a rpmsg device
95 and name matching.