mirror of
https://github.com/torvalds/linux.git
synced 2026-03-08 04:24:31 +01:00
2d53dfacf0
It turns out that both sysfs attributes actually directly control
the FN lock status/super key enable status, rather than the
triggering of the associated events. This behavior was first observed
on a Tuxedo notebook and was belived to be a hardware quirk.
However, it seems that i simply misunderstood the manual of the
OEM software for Intel NUC devices. The correct behavior is:
- fn_lock_toggle_enable enables/disables FN lock mode
- super_key_toggle_enable enables/disables the super key
Rename both sysfs attributes to avoid confusing users.
Fixes:
|
||
|---|---|---|
| .. | ||
| alienware-wmi.rst | ||
| asus-laptop.rst | ||
| disk-shock-protection.rst | ||
| index.rst | ||
| lg-laptop.rst | ||
| samsung-galaxybook.rst | ||
| sony-laptop.rst | ||
| sonypi.rst | ||
| thinkpad-acpi.rst | ||
| toshiba_haps.rst | ||
| uniwill-laptop.rst | ||