Lines Matching full:a

6 		Every rpmsg device is a communication channel with a remote
7 		processor. Channels are identified with a (textual) name,
18 		Every rpmsg device is a communication channel with a remote
19 		processor. Channels have a local ("source") rpmsg address,
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
24 		dispatches them to the listening entity (a kernel driver).
36 		Every rpmsg device is a communication channel with a remote
37 		processor. Channels have a local ("source") rpmsg address,
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
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
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
64 		A channel is first created when an entity, whether local
68 		When that happens, a "name service" announcement is sent
73 		This sysfs entry tells us whether the channel is a local
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
88 		The listening entity (or client) which communicates with a
93 		This sysfs entry allows the rpmsg driver for a rpmsg device