On 1/3/25 20:58, Rob Herring wrote:
I still don't agree. Quoting Guenter:
The two values are also orthogonal. The fan rpm is fan dependent.
Each fan will require a different pwm value to reach the target speed.
Trying to use target-rpm to set a default pwm value would really
not make much if any sense.
But RPM is ultimately what you care about and is the fan parameter
that's universal yet independent of the underlying control. RPM is what
determines noise and power consumption.
There's 2 cases to consider: you have a tach signal and know the fan RPM
or you don't know the RPM. If you have a tach signal, we probably
wouldn't be discussing this because target-rpm would be enough. So I'm
assuming this is the case and you have no idea what RPM the fan runs at.
Correct, no tacho.
The fan-common.yaml binding is a bit incomplete for this. What you need
is some map of fan speed to PWM duty cycle as most likely it is not
linear response. I think there are 2 options here:
Use the 'cooling-levels' property. Fan "speed" is the index of the
array. So you just need a 'default-cooling-level' property that's the
default index.
I am not sure I what you mean with the RPM reference here? The
cooling-levels support in the fan-pwm.c driver is a mapping between
cooling levels and PWM values, NOT RPM value.
The other option is define an array of (fan RPM, PWM duty cycle) tuples.
Then target-rpm can be used to select the entry. We already have
something like this with 'gpio-fan,speed-map'.
Where should these "invented" RPM values come from when there is no
tacho signal? That sounds backwards / complicated for the very trivial
"what should the default PWM value be at driver probe time" use case.
There's also no definition of the minimum RPM or duty cycle in the
pwm-fan binding. We have min-rpm in fan-common, but that doesn't work
without a tach. A map would help here as well
The minimum PWM is presumably 0, E.G. signal always low?
This problem to me is similar to LEDs. Ultimately it's brightness that
you care about, not the current or PWM duty cycle to get there.
The use case (as described in the commit message) is to drive the fan
less hard to limit noise and/or power consumption. The input to the fan
drive control is a PWM setting, so it IMHO makes sense to specify that,
as that is the interface provided by the fan-pwm driver - E.G. you boot
up and tweak the pwm1 property in sysfs until you have a value that
suits the noise/power consumption requirements and stick that value in
the dts.
Finally, whatever we end up with, it should go in fan-common.yaml. That
supports PWMs too, so whatever we end up with is applicable to any PWM
controlled fan.
What makes this "default-pwm" (or whatever it will be called) more
generic than E.G. the recently added "fan-stop-to-start-percent" /
"fan-stop-to-start-usec" properties added to pwm-fan.yaml by commit
80bc64201e78 ("dt-bindings: hwmon: pwm-fan: Document start from stopped
state properties")?
--
Bye, Peter Korsgaard
