sysfs-bus-rpmsg 3.7 KB

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