sysfs-class-regulator 9.7 KB

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