Questions

[glpnk]

AI allowed, but do minimal research yourself.
Please add links to make question more exact

[mohammad-abbas-mehdi]

Clarifying intent on issues #739, #740, #741

Thanks for the responses and for creating this space. A few corrections and clarifications:

On the use case: the goal is read-only monitoring — making fan RPM visible to sensors, desktop extensions like Vitals, and node_exporter. Not fan control; not touching the EC's closed-loop logic. Our implementation registers only fan1_input / fan2_input with no write path.

On tachometer registers (#740): the registers exist on WMI1 hardware — they appear in your own WMI1 EC register map (TDCD/TDCB in the AP block), and PR #475 (@Jiogo18) reads from these same addresses using ec_read_seq. We have confirmed them empirically on the GV62 7RD as well. We also noted in issue #164 that you had planned "SYS-FS API for fan tuning and RPM readout" — we are proposing to deliver that via the hwmon interface rather than a new platform sysfs path.

On EC temperatures (#739): your point is taken — EC temps are secondary and real temperature data comes from coretemp/amdgpu. We'll close that issue. The hwmon device registration will be bundled with the fan RPM PR directly, so closing #739 leaves no gap in the plan.

On WMI2 coexistence (#741): glad to hear the WMI2 migration direction is confirmed. The is_wmi2 flag was specifically to avoid duplicating hwmon channels during that transition — still needed until the migration is complete.

One question to unblock: is read-only fan RPM monitoring on WMI1 via EC tachometer registers a direction you'd accept a PR for?

[mohammad-abbas-mehdi]

Just a gentle follow-up — happy to wait, but wanted to bump visibility of the key question from my earlier comment:

Is read-only fan RPM monitoring on WMI1 via EC tachometer registers a direction you’d accept a PR for?

No rush — just want to know whether to proceed or park it.