Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

3 Commits   0 Branches   0 Tags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) Kernel driver max16064
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) ======================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) Supported chips:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6)   * Maxim MAX16064
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8)     Prefix: 'max16064'
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10)     Addresses scanned: -
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12)     Datasheet: http://datasheets.maxim-ic.com/en/ds/MAX16064.pdf
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) Author: Guenter Roeck <linux@roeck-us.net>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) Description
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) -----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) This driver supports hardware monitoring for Maxim MAX16064 Quad Power-Supply
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) Controller with Active-Voltage Output Control and PMBus Interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) The driver is a client driver to the core PMBus driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) Usage Notes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) -----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) This driver does not auto-detect devices. You will have to instantiate the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) Platform data support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) The driver supports standard PMBus driver platform data.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) Sysfs entries
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) -------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) The following attributes are supported. Limits are read-write; all other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) attributes are read-only.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) ======================= ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) in[1-4]_label		"vout[1-4]"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) in[1-4]_input		Measured voltage. From READ_VOUT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) in[1-4]_min		Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) in[1-4]_max		Maximum voltage. From VOUT_OV_WARN_LIMIT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) in[1-4]_lcrit		Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) in[1-4]_crit		Critical maximum voltage. From VOUT_OV_FAULT_LIMIT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) 			register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) in[1-4]_min_alarm	Voltage low alarm. From VOLTAGE_UV_WARNING status.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) in[1-4]_max_alarm	Voltage high alarm. From VOLTAGE_OV_WARNING status.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) in[1-4]_lcrit_alarm	Voltage critical low alarm. From VOLTAGE_UV_FAULT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) 			status.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) in[1-4]_crit_alarm	Voltage critical high alarm. From VOLTAGE_OV_FAULT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) 			status.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) in[1-4]_highest		Historical maximum voltage.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) in[1-4]_reset_history	Write any value to reset history.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) temp1_input		Measured temperature. From READ_TEMPERATURE_1 register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) temp1_max		Maximum temperature. From OT_WARN_LIMIT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) temp1_crit		Critical high temperature. From OT_FAULT_LIMIT register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) temp1_max_alarm		Chip temperature high alarm. Set by comparing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) 			READ_TEMPERATURE_1 with OT_WARN_LIMIT if TEMP_OT_WARNING
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) 			status is set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) temp1_crit_alarm	Chip temperature critical high alarm. Set by comparing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) 			READ_TEMPERATURE_1 with OT_FAULT_LIMIT if TEMP_OT_FAULT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) 			status is set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) temp1_highest		Historical maximum temperature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) temp1_reset_history	Write any value to reset history.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) ======================= ========================================================