454 lines · plain
1What: /sys/class/regulator/.../state2Date: April 20083KernelVersion: 2.6.264Contact: Liam Girdwood <lrg@slimlogic.co.uk>5Description:6 Some regulator directories will contain a field called7 state. This reports the regulator enable control, for8 regulators which can report that input value.9 10 This will be one of the following strings:11 12 'enabled'13 'disabled'14 'unknown'15 16 'enabled' means the regulator output is ON and is supplying17 power to the system (assuming no error prevents it).18 19 'disabled' means the regulator output is OFF and is not20 supplying power to the system (unless some non-Linux21 control has enabled it).22 23 'unknown' means software cannot determine the state, or24 the reported state is invalid.25 26 NOTE: this field can be used in conjunction with microvolts27 or microamps to determine configured regulator output levels.28 29 30What: /sys/class/regulator/.../status31Description:32 Some regulator directories will contain a field called33 "status". This reports the current regulator status, for34 regulators which can report that output value.35 36 This will be one of the following strings:37 38 - off39 - on40 - error41 - fast42 - normal43 - idle44 - standby45 46 "off" means the regulator is not supplying power to the47 system.48 49 "on" means the regulator is supplying power to the system,50 and the regulator can't report a detailed operation mode.51 52 "error" indicates an out-of-regulation status such as being53 disabled due to thermal shutdown, or voltage being unstable54 because of problems with the input power supply.55 56 "fast", "normal", "idle", and "standby" are all detailed57 regulator operation modes (described elsewhere). They58 imply "on", but provide more detail.59 60 Note that regulator status is a function of many inputs,61 not limited to control inputs from Linux. For example,62 the actual load presented may trigger "error" status; or63 a regulator may be enabled by another user, even though64 Linux did not enable it.65 66 67What: /sys/class/regulator/.../type68Date: April 200869KernelVersion: 2.6.2670Contact: Liam Girdwood <lrg@slimlogic.co.uk>71Description:72 Each regulator directory will contain a field called73 type. This holds the regulator type.74 75 This will be one of the following strings:76 77 - 'voltage'78 - 'current'79 - 'unknown'80 81 'voltage' means the regulator output voltage can be controlled82 by software.83 84 'current' means the regulator output current limit can be85 controlled by software.86 87 'unknown' means software cannot control either voltage or88 current limit.89 90 91What: /sys/class/regulator/.../microvolts92Date: April 200893KernelVersion: 2.6.2694Contact: Liam Girdwood <lrg@slimlogic.co.uk>95Description:96 Some regulator directories will contain a field called97 microvolts. This holds the regulator output voltage setting98 measured in microvolts (i.e. E-6 Volts), for regulators99 which can report the control input for voltage.100 101 NOTE: This value should not be used to determine the regulator102 output voltage level as this value is the same regardless of103 whether the regulator is enabled or disabled.104 105 106What: /sys/class/regulator/.../microamps107Date: April 2008108KernelVersion: 2.6.26109Contact: Liam Girdwood <lrg@slimlogic.co.uk>110Description:111 Some regulator directories will contain a field called112 microamps. This holds the regulator output current limit113 setting measured in microamps (i.e. E-6 Amps), for regulators114 which can report the control input for a current limit.115 116 NOTE: This value should not be used to determine the regulator117 output current level as this value is the same regardless of118 whether the regulator is enabled or disabled.119 120 121What: /sys/class/regulator/.../opmode122Date: April 2008123KernelVersion: 2.6.26124Contact: Liam Girdwood <lrg@slimlogic.co.uk>125Description:126 Some regulator directories will contain a field called127 opmode. This holds the current regulator operating mode,128 for regulators which can report that control input value.129 130 The opmode value can be one of the following strings:131 132 - 'fast'133 - 'normal'134 - 'idle'135 - 'standby'136 - 'unknown'137 138 The modes are described in include/linux/regulator/consumer.h139 140 NOTE: This value should not be used to determine the regulator141 output operating mode as this value is the same regardless of142 whether the regulator is enabled or disabled. A "status"143 attribute may be available to determine the actual mode.144 145 146What: /sys/class/regulator/.../min_microvolts147Date: April 2008148KernelVersion: 2.6.26149Contact: Liam Girdwood <lrg@slimlogic.co.uk>150Description:151 Some regulator directories will contain a field called152 min_microvolts. This holds the minimum safe working regulator153 output voltage setting for this domain measured in microvolts,154 for regulators which support voltage constraints.155 156 NOTE: this will return the string 'constraint not defined' if157 the power domain has no min microvolts constraint defined by158 platform code.159 160 161What: /sys/class/regulator/.../max_microvolts162Date: April 2008163KernelVersion: 2.6.26164Contact: Liam Girdwood <lrg@slimlogic.co.uk>165Description:166 Some regulator directories will contain a field called167 max_microvolts. This holds the maximum safe working regulator168 output voltage setting for this domain measured in microvolts,169 for regulators which support voltage constraints.170 171 NOTE: this will return the string 'constraint not defined' if172 the power domain has no max microvolts constraint defined by173 platform code.174 175 176What: /sys/class/regulator/.../min_microamps177Date: April 2008178KernelVersion: 2.6.26179Contact: Liam Girdwood <lrg@slimlogic.co.uk>180Description:181 Some regulator directories will contain a field called182 min_microamps. This holds the minimum safe working regulator183 output current limit setting for this domain measured in184 microamps, for regulators which support current constraints.185 186 NOTE: this will return the string 'constraint not defined' if187 the power domain has no min microamps constraint defined by188 platform code.189 190 191What: /sys/class/regulator/.../max_microamps192Date: April 2008193KernelVersion: 2.6.26194Contact: Liam Girdwood <lrg@slimlogic.co.uk>195Description:196 Some regulator directories will contain a field called197 max_microamps. This holds the maximum safe working regulator198 output current limit setting for this domain measured in199 microamps, for regulators which support current constraints.200 201 NOTE: this will return the string 'constraint not defined' if202 the power domain has no max microamps constraint defined by203 platform code.204 205 206What: /sys/class/regulator/.../name207Date: October 2008208KernelVersion: 2.6.28209Contact: Liam Girdwood <lrg@slimlogic.co.uk>210Description:211 Each regulator directory will contain a field called212 name. This holds a string identifying the regulator for213 display purposes.214 215 NOTE: this will be empty if no suitable name is provided216 by platform or regulator drivers.217 218 219What: /sys/class/regulator/.../num_users220Date: April 2008221KernelVersion: 2.6.26222Contact: Liam Girdwood <lrg@slimlogic.co.uk>223Description:224 Each regulator directory will contain a field called225 num_users. This holds the number of consumer devices that226 have called regulator_enable() on this regulator.227 228 229What: /sys/class/regulator/.../requested_microamps230Date: April 2008231KernelVersion: 2.6.26232Contact: Liam Girdwood <lrg@slimlogic.co.uk>233Description:234 Some regulator directories will contain a field called235 requested_microamps. This holds the total requested load236 current in microamps for this regulator from all its consumer237 devices.238 239 240What: /sys/class/regulator/.../parent241Date: April 2008242KernelVersion: 2.6.26243Contact: Liam Girdwood <lrg@slimlogic.co.uk>244Description:245 Some regulator directories will contain a link called parent.246 This points to the parent or supply regulator if one exists.247 248What: /sys/class/regulator/.../suspend_mem_microvolts249Date: May 2008250KernelVersion: 2.6.26251Contact: Liam Girdwood <lrg@slimlogic.co.uk>252Description:253 Some regulator directories will contain a field called254 suspend_mem_microvolts. This holds the regulator output255 voltage setting for this domain measured in microvolts when256 the system is suspended to memory, for voltage regulators257 implementing suspend voltage configuration constraints.258 259What: /sys/class/regulator/.../suspend_disk_microvolts260Date: May 2008261KernelVersion: 2.6.26262Contact: Liam Girdwood <lrg@slimlogic.co.uk>263Description:264 Some regulator directories will contain a field called265 suspend_disk_microvolts. This holds the regulator output266 voltage setting for this domain measured in microvolts when267 the system is suspended to disk, for voltage regulators268 implementing suspend voltage configuration constraints.269 270What: /sys/class/regulator/.../suspend_standby_microvolts271Date: May 2008272KernelVersion: 2.6.26273Contact: Liam Girdwood <lrg@slimlogic.co.uk>274Description:275 Some regulator directories will contain a field called276 suspend_standby_microvolts. This holds the regulator output277 voltage setting for this domain measured in microvolts when278 the system is suspended to standby, for voltage regulators279 implementing suspend voltage configuration constraints.280 281What: /sys/class/regulator/.../suspend_mem_mode282Date: May 2008283KernelVersion: 2.6.26284Contact: Liam Girdwood <lrg@slimlogic.co.uk>285Description:286 Some regulator directories will contain a field called287 suspend_mem_mode. This holds the regulator operating mode288 setting for this domain when the system is suspended to289 memory, for regulators implementing suspend mode290 configuration constraints.291 292What: /sys/class/regulator/.../suspend_disk_mode293Date: May 2008294KernelVersion: 2.6.26295Contact: Liam Girdwood <lrg@slimlogic.co.uk>296Description:297 Some regulator directories will contain a field called298 suspend_disk_mode. This holds the regulator operating mode299 setting for this domain when the system is suspended to disk,300 for regulators implementing suspend mode configuration301 constraints.302 303What: /sys/class/regulator/.../suspend_standby_mode304Date: May 2008305KernelVersion: 2.6.26306Contact: Liam Girdwood <lrg@slimlogic.co.uk>307Description:308 Some regulator directories will contain a field called309 suspend_standby_mode. This holds the regulator operating mode310 setting for this domain when the system is suspended to311 standby, for regulators implementing suspend mode312 configuration constraints.313 314What: /sys/class/regulator/.../suspend_mem_state315Date: May 2008316KernelVersion: 2.6.26317Contact: Liam Girdwood <lrg@slimlogic.co.uk>318Description:319 Some regulator directories will contain a field called320 suspend_mem_state. This holds the regulator operating state321 when suspended to memory, for regulators implementing suspend322 configuration constraints.323 324 This will be one of the same strings reported by325 the "state" attribute.326 327What: /sys/class/regulator/.../suspend_disk_state328Date: May 2008329KernelVersion: 2.6.26330Contact: Liam Girdwood <lrg@slimlogic.co.uk>331Description:332 Some regulator directories will contain a field called333 suspend_disk_state. This holds the regulator operating state334 when suspended to disk, for regulators implementing335 suspend configuration constraints.336 337 This will be one of the same strings reported by338 the "state" attribute.339 340What: /sys/class/regulator/.../suspend_standby_state341Date: May 2008342KernelVersion: 2.6.26343Contact: Liam Girdwood <lrg@slimlogic.co.uk>344Description:345 Some regulator directories will contain a field called346 suspend_standby_state. This holds the regulator operating347 state when suspended to standby, for regulators implementing348 suspend configuration constraints.349 350 This will be one of the same strings reported by351 the "state" attribute.352 353What: /sys/class/regulator/.../bypass354Date: September 2012355KernelVersion: 3.7356Contact: Mark Brown <broonie@opensource.wolfsonmicro.com>357Description:358 Some regulator directories will contain a field called359 bypass. This indicates if the device is in bypass mode.360 361 This will be one of the following strings:362 363 - 'enabled'364 - 'disabled'365 - 'unknown'366 367 'enabled' means the regulator is in bypass mode.368 369 'disabled' means that the regulator is regulating.370 371 'unknown' means software cannot determine the state, or372 the reported state is invalid.373 374What: /sys/class/regulator/.../under_voltage375Date: April 2022376KernelVersion: 5.18377Contact: Zev Weiss <zev@bewilderbeest.net>378Description:379 Some regulator directories will contain a field called380 under_voltage. This indicates if the device reports an381 under-voltage fault (1) or not (0).382 383What: /sys/class/regulator/.../over_current384Date: April 2022385KernelVersion: 5.18386Contact: Zev Weiss <zev@bewilderbeest.net>387Description:388 Some regulator directories will contain a field called389 over_current. This indicates if the device reports an390 over-current fault (1) or not (0).391 392What: /sys/class/regulator/.../regulation_out393Date: April 2022394KernelVersion: 5.18395Contact: Zev Weiss <zev@bewilderbeest.net>396Description:397 Some regulator directories will contain a field called398 regulation_out. This indicates if the device reports an399 out-of-regulation fault (1) or not (0).400 401What: /sys/class/regulator/.../fail402Date: April 2022403KernelVersion: 5.18404Contact: Zev Weiss <zev@bewilderbeest.net>405Description:406 Some regulator directories will contain a field called407 fail. This indicates if the device reports an output failure408 (1) or not (0).409 410What: /sys/class/regulator/.../over_temp411Date: April 2022412KernelVersion: 5.18413Contact: Zev Weiss <zev@bewilderbeest.net>414Description:415 Some regulator directories will contain a field called416 over_temp. This indicates if the device reports an417 over-temperature fault (1) or not (0).418 419What: /sys/class/regulator/.../under_voltage_warn420Date: April 2022421KernelVersion: 5.18422Contact: Zev Weiss <zev@bewilderbeest.net>423Description:424 Some regulator directories will contain a field called425 under_voltage_warn. This indicates if the device reports an426 under-voltage warning (1) or not (0).427 428What: /sys/class/regulator/.../over_current_warn429Date: April 2022430KernelVersion: 5.18431Contact: Zev Weiss <zev@bewilderbeest.net>432Description:433 Some regulator directories will contain a field called434 over_current_warn. This indicates if the device reports an435 over-current warning (1) or not (0).436 437What: /sys/class/regulator/.../over_voltage_warn438Date: April 2022439KernelVersion: 5.18440Contact: Zev Weiss <zev@bewilderbeest.net>441Description:442 Some regulator directories will contain a field called443 over_voltage_warn. This indicates if the device reports an444 over-voltage warning (1) or not (0).445 446What: /sys/class/regulator/.../over_temp_warn447Date: April 2022448KernelVersion: 5.18449Contact: Zev Weiss <zev@bewilderbeest.net>450Description:451 Some regulator directories will contain a field called452 over_temp_warn. This indicates if the device reports an453 over-temperature warning (1) or not (0).454