On 2022/11/3, 12:30 PM, "Guenter Roeck" <groeck7@xxxxxxxxx on behalf of linux@xxxxxxxxxxxx> wrote:
On Thu, Nov 03, 2022 at 03:52:59AM +0000, Billy Tsai wrote:
> >
> > Can't I use a min/max RPM to let the driver know a reasonable timeout/polling period when
> > the driver is trying to get RPM?
> > Beacause that our tach controller have the falg to indicates the hardware detected the change
> > in the input signal. I need the proper timout to rule out slow RPMs.
> If the chip measures the fan speed continuously, why would that ever be a
> problem, and why wait in the first place instead of just taking the most
> recent result ?
> Pretty much every other driver is doing that, so I really don't understand
> why that would not work here.
When the fan speed drop from a very fast RPM to a very slow RPM. Especially when it is close to stopping.
The most recent result will be no meaningful value. The slower RPM needs more time to sample it. E.g., If
we want to measure the fan with 600 RPM, the controller needs at least 100ms. During this time period, we
will always get the wrong value. So, our tach controller have the flag to avoid this problem:
TACH_ASPEED_VALUE_UPDATE: tach value updated since last read
This flag will be set when the controller detected the change of the signal and clear by read it.
In order to use this flag, the controller needs the proper timeout based on minimum RPM to avoid waiting forever.
Best Regards,
Billy Tsai
