The pwm-fan driver uses full PWM (255) duty cycle at startup, which may not always be desirable because of noise or power consumption peaks, so add an optional "default-pwm" property that can be used to specify a custom default PWM duty cycle (0..255). This is somewhat similar to target-rpm from fan-common.yaml, but that cannot be used here as target-rpm specifies the target fan speed, whereas this is the default pwm to set when the device is instantiated - And the resulting fan RPM resulting from a given PWM duty cycle is fan dependent. Signed-off-by: Peter Korsgaard <peter@xxxxxxxxxxxxx> --- Changes since v3: - Fix example syntax - Extend description of why target-rpm cannot be used Changes since v2: - Recreated/resent Changes since v1: - Rename to default-pwm Documentation/devicetree/bindings/hwmon/pwm-fan.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/hwmon/pwm-fan.yaml b/Documentation/devicetree/bindings/hwmon/pwm-fan.yaml index 8b4ed5ee962f..873c4c32e608 100644 --- a/Documentation/devicetree/bindings/hwmon/pwm-fan.yaml +++ b/Documentation/devicetree/bindings/hwmon/pwm-fan.yaml @@ -20,6 +20,13 @@ properties: items: maximum: 255 + default-pwm: + description: Default PWM duty cycle value to use at startup + $ref: /schemas/types.yaml#/definitions/uint32 + minimum: 0 + maximum: 255 + default: 255 + fan-supply: description: Phandle to the regulator that provides power to the fan. @@ -100,6 +107,7 @@ examples: pwm-fan { compatible = "pwm-fan"; pwms = <&pwm 0 40000 0>; + default-pwm = <75>; fan-supply = <®_fan>; interrupt-parent = <&gpio5>; interrupts = <1 IRQ_TYPE_EDGE_FALLING>; -- 2.39.5