sysfs-class-remoteproc 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. What: /sys/class/remoteproc/.../firmware
  2. Date: October 2016
  3. Contact: Matt Redfearn <matt.redfearn@mips.com>
  4. Description: Remote processor firmware
  5. Reports the name of the firmware currently loaded to the
  6. remote processor.
  7. To change the running firmware, ensure the remote processor is
  8. stopped (using /sys/class/remoteproc/.../state) and write a new filename.
  9. What: /sys/class/remoteproc/.../state
  10. Date: October 2016
  11. Contact: Matt Redfearn <matt.redfearn@mips.com>
  12. Description: Remote processor state
  13. Reports the state of the remote processor, which will be one of:
  14. - "offline"
  15. - "suspended"
  16. - "running"
  17. - "crashed"
  18. - "invalid"
  19. "offline" means the remote processor is powered off.
  20. "suspended" means that the remote processor is suspended and
  21. must be woken to receive messages.
  22. "running" is the normal state of an available remote processor
  23. "crashed" indicates that a problem/crash has been detected on
  24. the remote processor.
  25. "invalid" is returned if the remote processor is in an
  26. unknown state.
  27. Writing this file controls the state of the remote processor.
  28. The following states can be written:
  29. - "start"
  30. - "stop"
  31. Writing "start" will attempt to start the processor running the
  32. firmware indicated by, or written to,
  33. /sys/class/remoteproc/.../firmware. The remote processor should
  34. transition to "running" state.
  35. Writing "stop" will attempt to halt the remote processor and
  36. return it to the "offline" state.
  37. What: /sys/class/remoteproc/.../name
  38. Date: August 2019
  39. KernelVersion: 5.4
  40. Contact: Suman Anna <s-anna@ti.com>
  41. Description: Remote processor name
  42. Reports the name of the remote processor. This can be used by
  43. userspace in exactly identifying a remote processor and ease
  44. up the usage in modifying the 'firmware' or 'state' files.
  45. What: /sys/class/remoteproc/.../coredump
  46. Date: July 2020
  47. Contact: Bjorn Andersson <bjorn.andersson@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>
  48. Description: Remote processor coredump configuration
  49. Reports the coredump configuration of the remote processor,
  50. which will be one of:
  51. "disabled"
  52. "enabled"
  53. "inline"
  54. "disabled" means no dump will be collected.
  55. "enabled" means when the remote processor's coredump is
  56. collected it will be copied to a separate buffer and that
  57. buffer is exposed to userspace.
  58. "inline" means when the remote processor's coredump is
  59. collected userspace will directly read from the remote
  60. processor's device memory. Extra buffer will not be used to
  61. copy the dump. Also recovery process will not proceed until
  62. all data is read by usersapce.
  63. What: /sys/class/remoteproc/.../recovery
  64. Date: July 2020
  65. Contact: Bjorn Andersson <bjorn.andersson@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>
  66. Description: Remote processor recovery mechanism
  67. Reports the recovery mechanism of the remote processor,
  68. which will be one of:
  69. "enabled"
  70. "disabled"
  71. "enabled" means, the remote processor will be automatically
  72. recovered whenever it crashes. Moreover, if the remote
  73. processor crashes while recovery is disabled, it will
  74. be automatically recovered too as soon as recovery is enabled.
  75. "disabled" means, a remote processor will remain in a crashed
  76. state if it crashes. This is useful for debugging purposes;
  77. without it, debugging a crash is substantially harder.