https://bugzilla.novell.com/show_bug.cgi?id=308191#c1
Timo Hoenig
/usr/sbin/thinkpad-keys is always on of the top-3 causes to always keep my cpu hot (most times even in top-2), so my cpu is prevented to go to C4 state by thinkpad-keys only. thinkpad-keys rereads its whole dataset from nvram up to 25times per second (cpu/time expensive and in a maximum unoptimal way) just to show up OSD (on screen display) info.
Reduce the interval and you will see that it does not work very well.
Additionally this is needles to many points: 1. thinkpad_acpi (kernel module) can be told to issue acpi-events which then can be processed (no need for polling at all).
Please share which ACPI events are being generated for volume up/down and mute.
---but even without using acpi-events: 2. 5HZ would be enough (5 e.g. volume-changes per second should be enough - especially as this is expensive polling just for the OSD popup).
See above.
3. The expensive reading of nvram needs to be optimized to just read parts of interest (and not everything (with 25HZ), process all changes, then see if those found changes are of interest and so forth...)
I would very much prefer to use acpi-events from the thinkpad_acpi driver, as additionally thinkpad-keys messes with the hardware-volume mixer of thinkpads.
If we rely on ACPI events we'd still have to pass the events using uinput to keep the OSD working. We're still stuck with the double adjustment as we do not have a "handled in hardware" flag as for brightness keys.
But this is due to a wrong compile of the source (the source documents this, but we compile the part for soft-mixers (only found i extremly old/outdated thinkpads), but not the part for hardware-mixers found in todays thinkpads.
Hm? I don't understand what you're trying to say. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.