1bcabbccaSOhad Ben-CohenWhat: /sys/bus/rpmsg/devices/.../name 2bcabbccaSOhad Ben-CohenDate: June 2011 3bcabbccaSOhad Ben-CohenKernelVersion: 3.3 4bcabbccaSOhad Ben-CohenContact: Ohad Ben-Cohen <ohad@wizery.com> 5bcabbccaSOhad Ben-CohenDescription: 6bcabbccaSOhad Ben-Cohen Every rpmsg device is a communication channel with a remote 7bcabbccaSOhad Ben-Cohen processor. Channels are identified with a (textual) name, 8bcabbccaSOhad Ben-Cohen which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in 9bcabbccaSOhad Ben-Cohen rpmsg.h). 10bcabbccaSOhad Ben-Cohen 11bcabbccaSOhad Ben-Cohen This sysfs entry contains the name of this channel. 12bcabbccaSOhad Ben-Cohen 13bcabbccaSOhad Ben-CohenWhat: /sys/bus/rpmsg/devices/.../src 14bcabbccaSOhad Ben-CohenDate: June 2011 15bcabbccaSOhad Ben-CohenKernelVersion: 3.3 16bcabbccaSOhad Ben-CohenContact: Ohad Ben-Cohen <ohad@wizery.com> 17bcabbccaSOhad Ben-CohenDescription: 18bcabbccaSOhad Ben-Cohen Every rpmsg device is a communication channel with a remote 19bcabbccaSOhad Ben-Cohen processor. Channels have a local ("source") rpmsg address, 20bcabbccaSOhad Ben-Cohen and remote ("destination") rpmsg address. When an entity 21bcabbccaSOhad Ben-Cohen starts listening on one end of a channel, it assigns it with 22bcabbccaSOhad Ben-Cohen a unique rpmsg address (a 32 bits integer). This way when 23bcabbccaSOhad Ben-Cohen inbound messages arrive to this address, the rpmsg core 24bcabbccaSOhad Ben-Cohen dispatches them to the listening entity (a kernel driver). 25bcabbccaSOhad Ben-Cohen 26bcabbccaSOhad Ben-Cohen This sysfs entry contains the src (local) rpmsg address 27bcabbccaSOhad Ben-Cohen of this channel. If it contains 0xffffffff, then an address 28bcabbccaSOhad Ben-Cohen wasn't assigned (can happen if no driver exists for this 29bcabbccaSOhad Ben-Cohen channel). 30bcabbccaSOhad Ben-Cohen 31bcabbccaSOhad Ben-CohenWhat: /sys/bus/rpmsg/devices/.../dst 32bcabbccaSOhad Ben-CohenDate: June 2011 33bcabbccaSOhad Ben-CohenKernelVersion: 3.3 34bcabbccaSOhad Ben-CohenContact: Ohad Ben-Cohen <ohad@wizery.com> 35bcabbccaSOhad Ben-CohenDescription: 36bcabbccaSOhad Ben-Cohen Every rpmsg device is a communication channel with a remote 37bcabbccaSOhad Ben-Cohen processor. Channels have a local ("source") rpmsg address, 38bcabbccaSOhad Ben-Cohen and remote ("destination") rpmsg address. When an entity 39bcabbccaSOhad Ben-Cohen starts listening on one end of a channel, it assigns it with 40bcabbccaSOhad Ben-Cohen a unique rpmsg address (a 32 bits integer). This way when 41bcabbccaSOhad Ben-Cohen inbound messages arrive to this address, the rpmsg core 42bcabbccaSOhad Ben-Cohen dispatches them to the listening entity. 43bcabbccaSOhad Ben-Cohen 44bcabbccaSOhad Ben-Cohen This sysfs entry contains the dst (remote) rpmsg address 45bcabbccaSOhad Ben-Cohen of this channel. If it contains 0xffffffff, then an address 46bcabbccaSOhad Ben-Cohen wasn't assigned (can happen if the kernel driver that 47bcabbccaSOhad Ben-Cohen is attached to this channel is exposing a service to the 48bcabbccaSOhad Ben-Cohen remote processor. This make it a local rpmsg server, 49bcabbccaSOhad Ben-Cohen and it is listening for inbound messages that may be sent 50bcabbccaSOhad Ben-Cohen from any remote rpmsg client; it is not bound to a single 51bcabbccaSOhad Ben-Cohen remote entity). 52bcabbccaSOhad Ben-Cohen 53bcabbccaSOhad Ben-CohenWhat: /sys/bus/rpmsg/devices/.../announce 54bcabbccaSOhad Ben-CohenDate: June 2011 55bcabbccaSOhad Ben-CohenKernelVersion: 3.3 56bcabbccaSOhad Ben-CohenContact: Ohad Ben-Cohen <ohad@wizery.com> 57bcabbccaSOhad Ben-CohenDescription: 58bcabbccaSOhad Ben-Cohen Every rpmsg device is a communication channel with a remote 59bcabbccaSOhad Ben-Cohen processor. Channels are identified by a textual name (see 60bcabbccaSOhad Ben-Cohen /sys/bus/rpmsg/devices/.../name above) and have a local 61bcabbccaSOhad Ben-Cohen ("source") rpmsg address, and remote ("destination") rpmsg 62bcabbccaSOhad Ben-Cohen address. 63bcabbccaSOhad Ben-Cohen 64bcabbccaSOhad Ben-Cohen A channel is first created when an entity, whether local 65bcabbccaSOhad Ben-Cohen or remote, starts listening on it for messages (and is thus 66bcabbccaSOhad Ben-Cohen called an rpmsg server). 67bcabbccaSOhad Ben-Cohen 68bcabbccaSOhad Ben-Cohen When that happens, a "name service" announcement is sent 69bcabbccaSOhad Ben-Cohen to the other processor, in order to let it know about the 70bcabbccaSOhad Ben-Cohen creation of the channel (this way remote clients know they 71bcabbccaSOhad Ben-Cohen can start sending messages). 72bcabbccaSOhad Ben-Cohen 73bcabbccaSOhad Ben-Cohen This sysfs entry tells us whether the channel is a local 74bcabbccaSOhad Ben-Cohen server channel that is announced (values are either 75bcabbccaSOhad Ben-Cohen true or false). 76