sysfs-class-regulator 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312
  1. What: /sys/class/regulator/.../state
  2. Date: April 2008
  3. KernelVersion: 2.6.26
  4. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  5. Description:
  6. Some regulator directories will contain a field called
  7. state. This reports the regulator enable status, for
  8. regulators which can report that value.
  9. This will be one of the following strings:
  10. 'enabled'
  11. 'disabled'
  12. 'unknown'
  13. 'enabled' means the regulator output is ON and is supplying
  14. power to the system.
  15. 'disabled' means the regulator output is OFF and is not
  16. supplying power to the system..
  17. 'unknown' means software cannot determine the state, or
  18. the reported state is invalid.
  19. NOTE: this field can be used in conjunction with microvolts
  20. and microamps to determine regulator output levels.
  21. What: /sys/class/regulator/.../type
  22. Date: April 2008
  23. KernelVersion: 2.6.26
  24. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  25. Description:
  26. Each regulator directory will contain a field called
  27. type. This holds the regulator type.
  28. This will be one of the following strings:
  29. 'voltage'
  30. 'current'
  31. 'unknown'
  32. 'voltage' means the regulator output voltage can be controlled
  33. by software.
  34. 'current' means the regulator output current limit can be
  35. controlled by software.
  36. 'unknown' means software cannot control either voltage or
  37. current limit.
  38. What: /sys/class/regulator/.../microvolts
  39. Date: April 2008
  40. KernelVersion: 2.6.26
  41. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  42. Description:
  43. Some regulator directories will contain a field called
  44. microvolts. This holds the regulator output voltage setting
  45. measured in microvolts (i.e. E-6 Volts), for regulators
  46. which can report that voltage.
  47. NOTE: This value should not be used to determine the regulator
  48. output voltage level as this value is the same regardless of
  49. whether the regulator is enabled or disabled.
  50. What: /sys/class/regulator/.../microamps
  51. Date: April 2008
  52. KernelVersion: 2.6.26
  53. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  54. Description:
  55. Some regulator directories will contain a field called
  56. microamps. This holds the regulator output current limit
  57. setting measured in microamps (i.e. E-6 Amps), for regulators
  58. which can report that current.
  59. NOTE: This value should not be used to determine the regulator
  60. output current level as this value is the same regardless of
  61. whether the regulator is enabled or disabled.
  62. What: /sys/class/regulator/.../opmode
  63. Date: April 2008
  64. KernelVersion: 2.6.26
  65. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  66. Description:
  67. Some regulator directories will contain a field called
  68. opmode. This holds the current regulator operating mode,
  69. for regulators which can report it.
  70. The opmode value can be one of the following strings:
  71. 'fast'
  72. 'normal'
  73. 'idle'
  74. 'standby'
  75. 'unknown'
  76. The modes are described in include/linux/regulator/consumer.h
  77. NOTE: This value should not be used to determine the regulator
  78. output operating mode as this value is the same regardless of
  79. whether the regulator is enabled or disabled.
  80. What: /sys/class/regulator/.../min_microvolts
  81. Date: April 2008
  82. KernelVersion: 2.6.26
  83. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  84. Description:
  85. Some regulator directories will contain a field called
  86. min_microvolts. This holds the minimum safe working regulator
  87. output voltage setting for this domain measured in microvolts,
  88. for regulators which support voltage constraints.
  89. NOTE: this will return the string 'constraint not defined' if
  90. the power domain has no min microvolts constraint defined by
  91. platform code.
  92. What: /sys/class/regulator/.../max_microvolts
  93. Date: April 2008
  94. KernelVersion: 2.6.26
  95. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  96. Description:
  97. Some regulator directories will contain a field called
  98. max_microvolts. This holds the maximum safe working regulator
  99. output voltage setting for this domain measured in microvolts,
  100. for regulators which support voltage constraints.
  101. NOTE: this will return the string 'constraint not defined' if
  102. the power domain has no max microvolts constraint defined by
  103. platform code.
  104. What: /sys/class/regulator/.../min_microamps
  105. Date: April 2008
  106. KernelVersion: 2.6.26
  107. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  108. Description:
  109. Some regulator directories will contain a field called
  110. min_microamps. This holds the minimum safe working regulator
  111. output current limit setting for this domain measured in
  112. microamps, for regulators which support current constraints.
  113. NOTE: this will return the string 'constraint not defined' if
  114. the power domain has no min microamps constraint defined by
  115. platform code.
  116. What: /sys/class/regulator/.../max_microamps
  117. Date: April 2008
  118. KernelVersion: 2.6.26
  119. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  120. Description:
  121. Some regulator directories will contain a field called
  122. max_microamps. This holds the maximum safe working regulator
  123. output current limit setting for this domain measured in
  124. microamps, for regulators which support current constraints.
  125. NOTE: this will return the string 'constraint not defined' if
  126. the power domain has no max microamps constraint defined by
  127. platform code.
  128. What: /sys/class/regulator/.../name
  129. Date: October 2008
  130. KernelVersion: 2.6.28
  131. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  132. Description:
  133. Each regulator directory will contain a field called
  134. name. This holds a string identifying the regulator for
  135. display purposes.
  136. NOTE: this will be empty if no suitable name is provided
  137. by platform or regulator drivers.
  138. What: /sys/class/regulator/.../num_users
  139. Date: April 2008
  140. KernelVersion: 2.6.26
  141. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  142. Description:
  143. Each regulator directory will contain a field called
  144. num_users. This holds the number of consumer devices that
  145. have called regulator_enable() on this regulator.
  146. What: /sys/class/regulator/.../requested_microamps
  147. Date: April 2008
  148. KernelVersion: 2.6.26
  149. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  150. Description:
  151. Some regulator directories will contain a field called
  152. requested_microamps. This holds the total requested load
  153. current in microamps for this regulator from all its consumer
  154. devices.
  155. What: /sys/class/regulator/.../parent
  156. Date: April 2008
  157. KernelVersion: 2.6.26
  158. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  159. Description:
  160. Some regulator directories will contain a link called parent.
  161. This points to the parent or supply regulator if one exists.
  162. What: /sys/class/regulator/.../suspend_mem_microvolts
  163. Date: May 2008
  164. KernelVersion: 2.6.26
  165. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  166. Description:
  167. Some regulator directories will contain a field called
  168. suspend_mem_microvolts. This holds the regulator output
  169. voltage setting for this domain measured in microvolts when
  170. the system is suspended to memory, for voltage regulators
  171. implementing suspend voltage configuration constraints.
  172. What: /sys/class/regulator/.../suspend_disk_microvolts
  173. Date: May 2008
  174. KernelVersion: 2.6.26
  175. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  176. Description:
  177. Some regulator directories will contain a field called
  178. suspend_disk_microvolts. This holds the regulator output
  179. voltage setting for this domain measured in microvolts when
  180. the system is suspended to disk, for voltage regulators
  181. implementing suspend voltage configuration constraints.
  182. What: /sys/class/regulator/.../suspend_standby_microvolts
  183. Date: May 2008
  184. KernelVersion: 2.6.26
  185. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  186. Description:
  187. Some regulator directories will contain a field called
  188. suspend_standby_microvolts. This holds the regulator output
  189. voltage setting for this domain measured in microvolts when
  190. the system is suspended to standby, for voltage regulators
  191. implementing suspend voltage configuration constraints.
  192. What: /sys/class/regulator/.../suspend_mem_mode
  193. Date: May 2008
  194. KernelVersion: 2.6.26
  195. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  196. Description:
  197. Some regulator directories will contain a field called
  198. suspend_mem_mode. This holds the regulator operating mode
  199. setting for this domain when the system is suspended to
  200. memory, for regulators implementing suspend mode
  201. configuration constraints.
  202. What: /sys/class/regulator/.../suspend_disk_mode
  203. Date: May 2008
  204. KernelVersion: 2.6.26
  205. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  206. Description:
  207. Some regulator directories will contain a field called
  208. suspend_disk_mode. This holds the regulator operating mode
  209. setting for this domain when the system is suspended to disk,
  210. for regulators implementing suspend mode configuration
  211. constraints.
  212. What: /sys/class/regulator/.../suspend_standby_mode
  213. Date: May 2008
  214. KernelVersion: 2.6.26
  215. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  216. Description:
  217. Some regulator directories will contain a field called
  218. suspend_standby_mode. This holds the regulator operating mode
  219. setting for this domain when the system is suspended to
  220. standby, for regulators implementing suspend mode
  221. configuration constraints.
  222. What: /sys/class/regulator/.../suspend_mem_state
  223. Date: May 2008
  224. KernelVersion: 2.6.26
  225. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  226. Description:
  227. Some regulator directories will contain a field called
  228. suspend_mem_state. This holds the regulator operating state
  229. when suspended to memory, for regulators implementing suspend
  230. configuration constraints.
  231. This will be one of the same strings reported by
  232. the "state" attribute.
  233. What: /sys/class/regulator/.../suspend_disk_state
  234. Date: May 2008
  235. KernelVersion: 2.6.26
  236. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  237. Description:
  238. Some regulator directories will contain a field called
  239. suspend_disk_state. This holds the regulator operating state
  240. when suspended to disk, for regulators implementing
  241. suspend configuration constraints.
  242. This will be one of the same strings reported by
  243. the "state" attribute.
  244. What: /sys/class/regulator/.../suspend_standby_state
  245. Date: May 2008
  246. KernelVersion: 2.6.26
  247. Contact: Liam Girdwood <lrg@slimlogic.co.uk>
  248. Description:
  249. Some regulator directories will contain a field called
  250. suspend_standby_state. This holds the regulator operating
  251. state when suspended to standby, for regulators implementing
  252. suspend configuration constraints.
  253. This will be one of the same strings reported by
  254. the "state" attribute.