| Message ID | 20170908043919.6924-2-andrew@aj.id.au |
|---|---|
| State | Changes Requested, archived |
| Headers | show |
| Series | pmbus: Expand fan support and add MAX31785 driver | expand |
On Fri, Sep 08, 2017 at 02:39:17PM +1000, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > --- > .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 +++++++++++++++++++++ I think this needs to be located by what it does (fan control), not what interface it has (pmbus). I'm not all that happy with hwmon either because things here seem to just be based on being Linux hwmon devices which is sometimes arbitrary. > 1 file changed, 158 insertions(+) > create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > new file mode 100644 > index 000000000000..af9578e7742c > --- /dev/null > +++ b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > @@ -0,0 +1,158 @@ > +Bindings for the Maxim MAX31785 Intelligent Fan Controller > +========================================================== > + > +Reference: > + > +https://datasheets.maximintegrated.com/en/ds/MAX31785.pdf > + > +Required properties: > +- compatible : One of "maxim,max31785" or "maxim,max31785a" > +- reg : I2C address, one of 0x52, 0x53, 0x54, 0x55. > +- #address-cells : Must be 1 > +- #size-cells : Must be 0 > +- #thermal-sensor-cells : Should be 1. The device supports: > + - One internal sensor > + - Four external I2C digital sensors > + - Six external thermal diodes You should define the IDs here, not just how many of each type. > + > +Optional properties: > +- use-stored-presence : Do not treat the devicetree description as canon for > + fan presence (the 'installed' bit of FAN_CONFIG_*). > + Instead, rely on the on the default value store of > + the device to populate it. Boolean? Please be explicit. Needs a vendor prefix. > + > +Capabilities are configured through subnodes of the controller's node. > + > +Fans > +---- > + > +Only fans with subnodes present will be considered as installed. If > +use-stored-presence is present in the parent node, then only fans that are both > +defined in the devicetree and have their installed bit set are considered > +installed. > + > +Required subnode properties: > +- compatible : Must be "pmbus-fan" "pmbus" is a property of the controller, not the fan, right? We should have compatibles along the lines of the type of fan like 4-wire, 3-wire, etc. > +- reg : The PMBus page the properties apply to. > +- #cooling-cells : Should be 2. See the thermal bindings at [1]. > +- maxim,fan-rotor-input : The type of rotor measurement provided to the > + controller. Must be either "tach" for tachometer > + pulses or "lock" for a locked-rotor signal. > +- maxim,fan-lock-polarity: Required iff maxim,fan-rotor-input is "lock". Valid > + values are "low" for active low, "high" for active > + high. > + > +Optional subnode properties: > +- fan-mode : "rpm" or "pwm". Default value is "pwm". > +- tach-pulses : Tachometer pulses per revolution. Valid values are > + 1, 2, 3 or 4. The default is 1. > +- cooling-min-level : Smallest cooling state accepted. See [1]. > +- cooling-max-level : Largest cooling state accepted. See [1]. > +- maxim,fan-no-fault-ramp: Do not ramp the fan to 100% PWM duty on detecting a > + fan fault > +- maxim,fan-startup : The number of rotations required before taking > + emergency action for an unresponsive fan and driving > + it with 100% or 0% PWM duty, depending on the state > + of maxim,fan-no-fault-ramp. Valid values are 0 > + (automatic spin-up disabled), 2, 4, or 8. Default > + value is 0. > +- maxim,fan-health : Enable automated fan health check > +- maxim,fan-ramp : Configures how fast the device ramps the PWM duty > + cycle from one value to another. Valid values are 0 > + to 7 inclusive, with values 0 - 2 configuring a > + 1000ms update rate and 1 - 3% duty respective duty > + increase, and 3 - 7 a 200ms update rate with a 1 - > + 5% respective duty increase. Default value is 0. > +- maxim,fan-no-watchdog : Do not ramp fan to 100% PWM duty on failure to > + update desired fan rate inside 10s. This implies > + maxim,tmp-no-fault-ramp > +- maxim,tmp-no-fault-ramp: Do not ramp fan to 100% PWM duty on temperature > + sensor fault detection. This implies > + maxim,fan-no-watchdog > +- maxim,tmp-hysteresis : The temperature hysteresis used to determine > + transitions to lower fan speed bands in the > + temperature/fan rate lookup table. Valid values are > + 2, 4, 6 or 8 (degrees celcius). Default value is 2. > +- maxim,fan-dual-tach : Enable dual tachometer functionality > +- maxim,fan-pwm-freq : The PWM frequency. Valid values are 30, 50, 100, 150 > + and 25000 (Hz). Default value is 30Hz. > +- maxim,fan-lookup-table : A 16-element cell array of alternating temperature > + and rate values representing the look up table. The > + rate units are set through the fan-mode property. > +- maxim,fan-fault-pin-mon: Ramp fans to 100% PWM duty when the FAULT pin is > + asserted In general, I think a good portion of these should be either implied by a fan compatible string or be part of a common fan binding. > + > +Temperature > +----------- > + > +Required subnode properties: > +- compatible : Must be "pmbus-temperature" > +- reg : The PMBus page the properties apply to. > + > +Optional subnode properties: > +- maxim,tmp-offset : Valid values are 0 - 30 (degrees celcius) inclusive. > + Default value is 0. > +- maxim,tmp-fans : An array of phandles to fans controlled by the > + current temperature sensor. Is this a feature of the Maxim chip or just a mapping of temperature sensors to fans. The latter should be a common property. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Sep 18, 2017 at 02:26:38PM -0500, Rob Herring wrote: > On Fri, Sep 08, 2017 at 02:39:17PM +1000, Andrew Jeffery wrote: > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > > --- > > .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 +++++++++++++++++++++ > > I think this needs to be located by what it does (fan control), not what > interface it has (pmbus). > > I'm not all that happy with hwmon either because things here seem to > just be based on being Linux hwmon devices which is sometimes arbitrary. > The chip also measures temperatures. Other PMBus chips may do fan control, measure temperatures, measure and/or control voltages, current, power ... Strictly speaking pretty much all PMBus chips are multi-function devices. I personally don't really care if the documentation is spread across several directories, but even here this is already challenging. Only solution I can think of would be to create separate documents for each functionality, ie here one for the device itself, one for fan control, and one for temperature control (if that needs separate bindings). That would be similar to mfd. But then we would still have to sort out where to store the various bindings. Like iio, in subdirectories ? Like mfd, in the matching subsystems ? If so, what to do if there is no matching subsystem ? Lots of questions. I'll be happy to spend some time sorting it out, but I would need some directions. Thanks, Guenter > > 1 file changed, 158 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > > > diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > new file mode 100644 > > index 000000000000..af9578e7742c > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > @@ -0,0 +1,158 @@ > > +Bindings for the Maxim MAX31785 Intelligent Fan Controller > > +========================================================== > > + > > +Reference: > > + > > +https://datasheets.maximintegrated.com/en/ds/MAX31785.pdf > > + > > +Required properties: > > +- compatible : One of "maxim,max31785" or "maxim,max31785a" > > +- reg : I2C address, one of 0x52, 0x53, 0x54, 0x55. > > +- #address-cells : Must be 1 > > +- #size-cells : Must be 0 > > +- #thermal-sensor-cells : Should be 1. The device supports: > > + - One internal sensor > > + - Four external I2C digital sensors > > + - Six external thermal diodes > > You should define the IDs here, not just how many of each type. > > > + > > +Optional properties: > > +- use-stored-presence : Do not treat the devicetree description as canon for > > + fan presence (the 'installed' bit of FAN_CONFIG_*). > > + Instead, rely on the on the default value store of > > + the device to populate it. > > Boolean? Please be explicit. > > Needs a vendor prefix. > > > + > > +Capabilities are configured through subnodes of the controller's node. > > + > > +Fans > > +---- > > + > > +Only fans with subnodes present will be considered as installed. If > > +use-stored-presence is present in the parent node, then only fans that are both > > +defined in the devicetree and have their installed bit set are considered > > +installed. > > + > > +Required subnode properties: > > +- compatible : Must be "pmbus-fan" > > "pmbus" is a property of the controller, not the fan, right? We should > have compatibles along the lines of the type of fan like 4-wire, 3-wire, > etc. > > > +- reg : The PMBus page the properties apply to. > > +- #cooling-cells : Should be 2. See the thermal bindings at [1]. > > +- maxim,fan-rotor-input : The type of rotor measurement provided to the > > + controller. Must be either "tach" for tachometer > > + pulses or "lock" for a locked-rotor signal. > > +- maxim,fan-lock-polarity: Required iff maxim,fan-rotor-input is "lock". Valid > > + values are "low" for active low, "high" for active > > + high. > > + > > +Optional subnode properties: > > +- fan-mode : "rpm" or "pwm". Default value is "pwm". > > +- tach-pulses : Tachometer pulses per revolution. Valid values are > > + 1, 2, 3 or 4. The default is 1. > > +- cooling-min-level : Smallest cooling state accepted. See [1]. > > +- cooling-max-level : Largest cooling state accepted. See [1]. > > +- maxim,fan-no-fault-ramp: Do not ramp the fan to 100% PWM duty on detecting a > > + fan fault > > +- maxim,fan-startup : The number of rotations required before taking > > + emergency action for an unresponsive fan and driving > > + it with 100% or 0% PWM duty, depending on the state > > + of maxim,fan-no-fault-ramp. Valid values are 0 > > + (automatic spin-up disabled), 2, 4, or 8. Default > > + value is 0. > > +- maxim,fan-health : Enable automated fan health check > > +- maxim,fan-ramp : Configures how fast the device ramps the PWM duty > > + cycle from one value to another. Valid values are 0 > > + to 7 inclusive, with values 0 - 2 configuring a > > + 1000ms update rate and 1 - 3% duty respective duty > > + increase, and 3 - 7 a 200ms update rate with a 1 - > > + 5% respective duty increase. Default value is 0. > > +- maxim,fan-no-watchdog : Do not ramp fan to 100% PWM duty on failure to > > + update desired fan rate inside 10s. This implies > > + maxim,tmp-no-fault-ramp > > +- maxim,tmp-no-fault-ramp: Do not ramp fan to 100% PWM duty on temperature > > + sensor fault detection. This implies > > + maxim,fan-no-watchdog > > +- maxim,tmp-hysteresis : The temperature hysteresis used to determine > > + transitions to lower fan speed bands in the > > + temperature/fan rate lookup table. Valid values are > > + 2, 4, 6 or 8 (degrees celcius). Default value is 2. > > +- maxim,fan-dual-tach : Enable dual tachometer functionality > > +- maxim,fan-pwm-freq : The PWM frequency. Valid values are 30, 50, 100, 150 > > + and 25000 (Hz). Default value is 30Hz. > > +- maxim,fan-lookup-table : A 16-element cell array of alternating temperature > > + and rate values representing the look up table. The > > + rate units are set through the fan-mode property. > > +- maxim,fan-fault-pin-mon: Ramp fans to 100% PWM duty when the FAULT pin is > > + asserted > > In general, I think a good portion of these should be either implied by > a fan compatible string or be part of a common fan binding. > > > + > > +Temperature > > +----------- > > + > > +Required subnode properties: > > +- compatible : Must be "pmbus-temperature" > > +- reg : The PMBus page the properties apply to. > > + > > +Optional subnode properties: > > +- maxim,tmp-offset : Valid values are 0 - 30 (degrees celcius) inclusive. > > + Default value is 0. > > +- maxim,tmp-fans : An array of phandles to fans controlled by the > > + current temperature sensor. > > Is this a feature of the Maxim chip or just a mapping of temperature > sensors to fans. The latter should be a common property. > > Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2017-09-18 at 14:26 -0500, Rob Herring wrote: > On Fri, Sep 08, 2017 at 02:39:17PM +1000, Andrew Jeffery wrote: > > > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > > --- > > .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 +++++++++++++++++++++ > > I think this needs to be located by what it does (fan control), not what > interface it has (pmbus). > > I'm not all that happy with hwmon either because things here seem to > just be based on being Linux hwmon devices which is sometimes arbitrary. I'll follow-up on this on Guenter's reply if necessary. > > > > 1 file changed, 158 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > > > diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > new file mode 100644 > > index 000000000000..af9578e7742c > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt > > @@ -0,0 +1,158 @@ > > +Bindings for the Maxim MAX31785 Intelligent Fan Controller > > +========================================================== > > + > > +Reference: > > + > > +https://datasheets.maximintegrated.com/en/ds/MAX31785.pdf > > + > > +Required properties: > > +- compatible : One of "maxim,max31785" or "maxim,max31785a" > > +- reg : I2C address, one of 0x52, 0x53, 0x54, 0x55. > > +- #address-cells : Must be 1 > > +- #size-cells : Must be 0 > > +- #thermal-sensor-cells : Should be 1. The device supports: > > + - One internal sensor > > + - Four external I2C digital sensors > > + - Six external thermal diodes > > You should define the IDs here, not just how many of each type. Okay. > > > + > > +Optional properties: > > +- use-stored-presence : Do not treat the devicetree description as canon for > > + fan presence (the 'installed' bit of FAN_CONFIG_*). > > + Instead, rely on the on the default value store of > > + the device to populate it. > > Boolean? Please be explicit. Okay. > > Needs a vendor prefix. We've discussed this previously. It's describing how to interpret part of the PMBus spec, not something Maxim have done, so I don't think it should have a vendor prefix. But maybe I'm representing it wrong? > > > + > > +Capabilities are configured through subnodes of the controller's node. > > + > > +Fans > > +---- > > + > > +Only fans with subnodes present will be considered as installed. If > > +use-stored-presence is present in the parent node, then only fans that are both > > +defined in the devicetree and have their installed bit set are considered > > +installed. > > + > > +Required subnode properties: > > +- compatible : Must be "pmbus-fan" > > "pmbus" is a property of the controller, not the fan, right? We should > have compatibles along the lines of the type of fan like 4-wire, 3-wire, > etc. Yes, PMBus is a property of the controller. But a controller that implements PMBus fan control and monitoring abstracts away most of the details of the fan hardware, so I don't see it fit to describe e.g. 4- wire or 3-wire properties here. Perhaps this is resolved by having a "pmbus-fan-control" compatible node, and nesting a fan node under that? My concern would be that the only element of the fan subnode would be the "tach-pulses" property (though maybe also dual-tach if we generalise the maxim,fan-dual-tach property below). Regardless, what I'm trying to describe here with the non-vendor- prefixed properties are configurable elements of the PMBus interface for fan control. Adherence to PMBus by a device dictates the command interface, and is therefore a property of the controller hardware at the end of the day. In this instance (PMBus) I don't see how we can draw the distinction between "what it does" and "what interface it has" - adherence to relevant parts of the PMBus spec defines the minimum of what the controller does (PMBus allows for vendor extensions). Unfortunately the PMBus spec is fairly loose in terms of what it *requires* you to implement, but I don't think that's relevant here. > > > +- reg : The PMBus page the properties apply to. > > +- #cooling-cells : Should be 2. See the thermal bindings at [1]. > > +- maxim,fan-rotor-input : The type of rotor measurement provided to the > > + controller. Must be either "tach" for tachometer > > + pulses or "lock" for a locked-rotor signal. > > +- maxim,fan-lock-polarity: Required iff maxim,fan-rotor-input is "lock". Valid > > + values are "low" for active low, "high" for active > > + high. > > + > > +Optional subnode properties: > > +- fan-mode : "rpm" or "pwm". Default value is "pwm". > > +- tach-pulses : Tachometer pulses per revolution. Valid values are > > + 1, 2, 3 or 4. The default is 1. > > +- cooling-min-level : Smallest cooling state accepted. See [1]. > > +- cooling-max-level : Largest cooling state accepted. See [1]. > > +- maxim,fan-no-fault-ramp: Do not ramp the fan to 100% PWM duty on detecting a > > + fan fault > > +- maxim,fan-startup : The number of rotations required before taking > > + emergency action for an unresponsive fan and driving > > + it with 100% or 0% PWM duty, depending on the state > > + of maxim,fan-no-fault-ramp. Valid values are 0 > > + (automatic spin-up disabled), 2, 4, or 8. Default > > + value is 0. > > +- maxim,fan-health : Enable automated fan health check > > +- maxim,fan-ramp : Configures how fast the device ramps the PWM duty > > + cycle from one value to another. Valid values are 0 > > + to 7 inclusive, with values 0 - 2 configuring a > > + 1000ms update rate and 1 - 3% duty respective duty > > + increase, and 3 - 7 a 200ms update rate with a 1 - > > + 5% respective duty increase. Default value is 0. > > +- maxim,fan-no-watchdog : Do not ramp fan to 100% PWM duty on failure to > > + update desired fan rate inside 10s. This implies > > + maxim,tmp-no-fault-ramp > > +- maxim,tmp-no-fault-ramp: Do not ramp fan to 100% PWM duty on temperature > > + sensor fault detection. This implies > > + maxim,fan-no-watchdog > > +- maxim,tmp-hysteresis : The temperature hysteresis used to determine > > + transitions to lower fan speed bands in the > > + temperature/fan rate lookup table. Valid values are > > + 2, 4, 6 or 8 (degrees celcius). Default value is 2. > > +- maxim,fan-dual-tach : Enable dual tachometer functionality > > +- maxim,fan-pwm-freq : The PWM frequency. Valid values are 30, 50, 100, 150 > > + and 25000 (Hz). Default value is 30Hz. > > +- maxim,fan-lookup-table : A 16-element cell array of alternating temperature > > + and rate values representing the look up table. The > > + rate units are set through the fan-mode property. > > +- maxim,fan-fault-pin-mon: Ramp fans to 100% PWM duty when the FAULT pin is > > + asserted > > In general, I think a good portion of these should be either implied by > a fan compatible string or be part of a common fan binding. Above you made the distinction between fan and fan controller, but I feel like following your suggestion here is mixing things up in the opposite direction to what you desired above. In my mind most of these properties describe a fan controller's capability rather than a property of a fan, save say "tach-pulses", which is a property of the fan's tacho, and maybe "maxim,fan-dual-tach" which applies to any dual- rotor fan and should probably be generalised. > > > + > > +Temperature > > +----------- > > + > > +Required subnode properties: > > +- compatible : Must be "pmbus-temperature" > > +- reg : The PMBus page the properties apply to. > > + > > +Optional subnode properties: > > +- maxim,tmp-offset : Valid values are 0 - 30 (degrees celcius) inclusive. > > + Default value is 0. > > +- maxim,tmp-fans : An array of phandles to fans controlled by the > > + current temperature sensor. > > Is this a feature of the Maxim chip or just a mapping of temperature > sensors to fans. The latter should be a common property. It's a manufacturer-specific feature of the Maxim chip, which can do the full closed-loop fan control using a lookup table mapping temperatures to fan speeds. The lookup table can be described with the maxim,fan-lookup-table property specified above, and maxim,tmp-fans maps the temperature sensor to a set of fans to control using its temperature readings with respect to each fan's lookup table. Cheers, Andrew > > Rob
On Mon, 2017-09-18 at 13:15 -0700, Guenter Roeck wrote: > On Mon, Sep 18, 2017 at 02:26:38PM -0500, Rob Herring wrote: > > On Fri, Sep 08, 2017 at 02:39:17PM +1000, Andrew Jeffery wrote: > > > > > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> > > > --- > > > .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 +++++++++++++++++++++ > > > > I think this needs to be located by what it does (fan control), not what > > interface it has (pmbus). > > > > I'm not all that happy with hwmon either because things here seem to > > just be based on being Linux hwmon devices which is sometimes arbitrary. > > > > The chip also measures temperatures. Other PMBus chips may do fan control, > measure temperatures, measure and/or control voltages, current, power ... > Strictly speaking pretty much all PMBus chips are multi-function devices. > I personally don't really care if the documentation is spread across > several directories, but even here this is already challenging. > > Only solution I can think of would be to create separate documents for each > functionality, ie here one for the device itself, one for fan control, > and one for temperature control (if that needs separate bindings). That > would be similar to mfd. But then we would still have to sort out where > to store the various bindings. Like iio, in subdirectories ? Like mfd, > in the matching subsystems ? If so, what to do if there is no matching > subsystem ? > > Lots of questions. I'll be happy to spend some time sorting it out, > but I would need some directions. > Likewise - I'm keen to discuss and iterate on this so we get something satisfactory. At least I could split out the PMBus-specific bindings from the Maxim- specific bindings in the current document, but there's still the question of how to arrange it as Guenter has queried above, and also how much of PMBus to define bindings for. I'm hesitant to take a stab at describing bindings across the whole spec if I don't have useful driver implementations to test against. I know that the bindings describe the hardware and not the driver, but there are probably more or less clumsy ways to describe devices that could be ironed out with a corresponding implementation (e.g. the Aspeed PWM/Tacho...). Thoughts? Andrew
diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt new file mode 100644 index 000000000000..af9578e7742c --- /dev/null +++ b/Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt @@ -0,0 +1,158 @@ +Bindings for the Maxim MAX31785 Intelligent Fan Controller +========================================================== + +Reference: + +https://datasheets.maximintegrated.com/en/ds/MAX31785.pdf + +Required properties: +- compatible : One of "maxim,max31785" or "maxim,max31785a" +- reg : I2C address, one of 0x52, 0x53, 0x54, 0x55. +- #address-cells : Must be 1 +- #size-cells : Must be 0 +- #thermal-sensor-cells : Should be 1. The device supports: + - One internal sensor + - Four external I2C digital sensors + - Six external thermal diodes + +Optional properties: +- use-stored-presence : Do not treat the devicetree description as canon for + fan presence (the 'installed' bit of FAN_CONFIG_*). + Instead, rely on the on the default value store of + the device to populate it. + +Capabilities are configured through subnodes of the controller's node. + +Fans +---- + +Only fans with subnodes present will be considered as installed. If +use-stored-presence is present in the parent node, then only fans that are both +defined in the devicetree and have their installed bit set are considered +installed. + +Required subnode properties: +- compatible : Must be "pmbus-fan" +- reg : The PMBus page the properties apply to. +- #cooling-cells : Should be 2. See the thermal bindings at [1]. +- maxim,fan-rotor-input : The type of rotor measurement provided to the + controller. Must be either "tach" for tachometer + pulses or "lock" for a locked-rotor signal. +- maxim,fan-lock-polarity: Required iff maxim,fan-rotor-input is "lock". Valid + values are "low" for active low, "high" for active + high. + +Optional subnode properties: +- fan-mode : "rpm" or "pwm". Default value is "pwm". +- tach-pulses : Tachometer pulses per revolution. Valid values are + 1, 2, 3 or 4. The default is 1. +- cooling-min-level : Smallest cooling state accepted. See [1]. +- cooling-max-level : Largest cooling state accepted. See [1]. +- maxim,fan-no-fault-ramp: Do not ramp the fan to 100% PWM duty on detecting a + fan fault +- maxim,fan-startup : The number of rotations required before taking + emergency action for an unresponsive fan and driving + it with 100% or 0% PWM duty, depending on the state + of maxim,fan-no-fault-ramp. Valid values are 0 + (automatic spin-up disabled), 2, 4, or 8. Default + value is 0. +- maxim,fan-health : Enable automated fan health check +- maxim,fan-ramp : Configures how fast the device ramps the PWM duty + cycle from one value to another. Valid values are 0 + to 7 inclusive, with values 0 - 2 configuring a + 1000ms update rate and 1 - 3% duty respective duty + increase, and 3 - 7 a 200ms update rate with a 1 - + 5% respective duty increase. Default value is 0. +- maxim,fan-no-watchdog : Do not ramp fan to 100% PWM duty on failure to + update desired fan rate inside 10s. This implies + maxim,tmp-no-fault-ramp +- maxim,tmp-no-fault-ramp: Do not ramp fan to 100% PWM duty on temperature + sensor fault detection. This implies + maxim,fan-no-watchdog +- maxim,tmp-hysteresis : The temperature hysteresis used to determine + transitions to lower fan speed bands in the + temperature/fan rate lookup table. Valid values are + 2, 4, 6 or 8 (degrees celcius). Default value is 2. +- maxim,fan-dual-tach : Enable dual tachometer functionality +- maxim,fan-pwm-freq : The PWM frequency. Valid values are 30, 50, 100, 150 + and 25000 (Hz). Default value is 30Hz. +- maxim,fan-lookup-table : A 16-element cell array of alternating temperature + and rate values representing the look up table. The + rate units are set through the fan-mode property. +- maxim,fan-fault-pin-mon: Ramp fans to 100% PWM duty when the FAULT pin is + asserted + +Temperature +----------- + +Required subnode properties: +- compatible : Must be "pmbus-temperature" +- reg : The PMBus page the properties apply to. + +Optional subnode properties: +- maxim,tmp-offset : Valid values are 0 - 30 (degrees celcius) inclusive. + Default value is 0. +- maxim,tmp-fans : An array of phandles to fans controlled by the + current temperature sensor. + +[1] Documentation/devicetree/bindings/thermal/thermal.txt + +Example: + fan-max31785: max31785@52 { + reg = <0x52>; + compatible = "maxim,max31785"; + #address-cells = <1>; + #size-cells = <0>; + #thermal-sensor-cells = <1>; + + fan@0 { + compatible = "pmbus-fan"; + reg = <0>; + mode = "rpm"; + tach-pulses = <1>; + + #cooling-cells = <2>; + cooling-min-level = <0>; + cooling-max-level = <9>; + + maxim,fan-rotor-input = "tach"; + maxim,fan-dual-tach; + }; + + /* + * Hardware controlled fan: Fan speed is controlled by a + * temperature sensor feeding values into the lookup table. The + * fan association is done in the temperature sensor node. One + * sensor can drive multiple fans. + */ + cpu_fan: fan@1 { + compatible = "pmbus-fan"; + reg = <1>; + mode = "rpm"; + tach-pulses = <1>; + + #cooling-cells = <2>; + + maxim,fan-rotor-input = "tach"; + maxim,tmp-hysteresis = <2>; + maxim,fan-lookup-table = < + /* Temperature RPM */ + 0 1000 + 10 2000 + 20 3000 + 30 4000 + 40 5000 + 50 6000 + 60 7000 + 70 8000 + >; + }; + + cpu_temp: sensor@6 { + compatible = "pmbus-temperature"; + reg = <6>; + + maxim,tmp-offset = <0>; + maxim,tmp-fans = <&cpu_fan>; + }; + };
Signed-off-by: Andrew Jeffery <andrew@aj.id.au> --- .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 +++++++++++++++++++++ 1 file changed, 158 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt