2011-04-18 20:53:54 +04:00
|
|
|
Kernel driver max16064
|
|
|
|
======================
|
|
|
|
|
|
|
|
Supported chips:
|
2019-04-17 12:46:26 +03:00
|
|
|
|
2011-04-18 20:53:54 +04:00
|
|
|
* Maxim MAX16064
|
2019-04-17 12:46:26 +03:00
|
|
|
|
2011-04-18 20:53:54 +04:00
|
|
|
Prefix: 'max16064'
|
2019-04-17 12:46:26 +03:00
|
|
|
|
2011-04-18 20:53:54 +04:00
|
|
|
Addresses scanned: -
|
2019-04-17 12:46:26 +03:00
|
|
|
|
2011-04-18 20:53:54 +04:00
|
|
|
Datasheet: http://datasheets.maxim-ic.com/en/ds/MAX16064.pdf
|
|
|
|
|
2013-02-21 08:58:42 +04:00
|
|
|
Author: Guenter Roeck <linux@roeck-us.net>
|
2011-04-18 20:53:54 +04:00
|
|
|
|
|
|
|
|
|
|
|
Description
|
|
|
|
-----------
|
|
|
|
|
2016-02-28 06:57:57 +03:00
|
|
|
This driver supports hardware monitoring for Maxim MAX16064 Quad Power-Supply
|
2011-04-18 20:53:54 +04:00
|
|
|
Controller with Active-Voltage Output Control and PMBus Interface.
|
|
|
|
|
|
|
|
The driver is a client driver to the core PMBus driver.
|
2019-04-17 12:46:29 +03:00
|
|
|
Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
|
2011-04-18 20:53:54 +04:00
|
|
|
|
|
|
|
|
|
|
|
Usage Notes
|
|
|
|
-----------
|
|
|
|
|
|
|
|
This driver does not auto-detect devices. You will have to instantiate the
|
2019-07-26 15:51:16 +03:00
|
|
|
devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
|
2011-04-18 20:53:54 +04:00
|
|
|
details.
|
|
|
|
|
|
|
|
|
|
|
|
Platform data support
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
The driver supports standard PMBus driver platform data.
|
|
|
|
|
|
|
|
|
|
|
|
Sysfs entries
|
|
|
|
-------------
|
|
|
|
|
|
|
|
The following attributes are supported. Limits are read-write; all other
|
|
|
|
attributes are read-only.
|
|
|
|
|
2019-04-17 12:46:26 +03:00
|
|
|
======================= ========================================================
|
2011-04-18 20:53:54 +04:00
|
|
|
in[1-4]_label "vout[1-4]"
|
|
|
|
in[1-4]_input Measured voltage. From READ_VOUT register.
|
2012-03-04 18:16:11 +04:00
|
|
|
in[1-4]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
|
2011-04-18 20:53:54 +04:00
|
|
|
in[1-4]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
|
2012-03-04 18:16:11 +04:00
|
|
|
in[1-4]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
|
2019-04-17 12:46:26 +03:00
|
|
|
in[1-4]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT
|
|
|
|
register.
|
2011-04-18 20:53:54 +04:00
|
|
|
in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
|
|
|
|
in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
|
2019-04-17 12:46:26 +03:00
|
|
|
in[1-4]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
|
|
|
|
status.
|
|
|
|
in[1-4]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
|
|
|
|
status.
|
2011-07-10 00:10:19 +04:00
|
|
|
in[1-4]_highest Historical maximum voltage.
|
|
|
|
in[1-4]_reset_history Write any value to reset history.
|
2011-04-18 20:53:54 +04:00
|
|
|
|
|
|
|
temp1_input Measured temperature. From READ_TEMPERATURE_1 register.
|
|
|
|
temp1_max Maximum temperature. From OT_WARN_LIMIT register.
|
|
|
|
temp1_crit Critical high temperature. From OT_FAULT_LIMIT register.
|
|
|
|
temp1_max_alarm Chip temperature high alarm. Set by comparing
|
|
|
|
READ_TEMPERATURE_1 with OT_WARN_LIMIT if TEMP_OT_WARNING
|
|
|
|
status is set.
|
|
|
|
temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
|
|
|
|
READ_TEMPERATURE_1 with OT_FAULT_LIMIT if TEMP_OT_FAULT
|
|
|
|
status is set.
|
2011-07-10 00:10:19 +04:00
|
|
|
temp1_highest Historical maximum temperature.
|
|
|
|
temp1_reset_history Write any value to reset history.
|
2019-04-17 12:46:26 +03:00
|
|
|
======================= ========================================================
|