From: Josh Triplett <josh@joshtriplett.org>
To: linux-input@vger.kernel.org, Jamie Lentin <jm@lentin.co.uk>
Cc: 1006251@bugs.debian.org
Subject: USB Lenovo ThinkPad Compact Keyboard has fn_lock inverted
Date: Fri, 11 Nov 2022 09:06:57 -0800 [thread overview]
Message-ID: <Y26BMXn15Kbt6a2u@localhost> (raw)
I have an external ThinkPad USB keyboard:
$ lsusb | grep -i keyboard
Bus 003 Device 022: ID 17ef:6047 Lenovo ThinkPad Compact Keyboard with TrackPoint
The Linux kernel exposes a fn_lock attribute in sysfs for this keyboard:
$ cat
sys/devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.4/3-5.4.3/3-5.4.3:1.1/0003:17EF:6047.000F/fn_lock
1
However, this attribute appears inverted for this particular keyboard:
it seems to be 1 when FnLock is *disabled* and 0 when FnLock is
*enabled*. In order to enable FnLock, I have to write 0 to this file.
(Also, separately from that, it would be nice if the kernel could handle
fn_lock toggling *internally*, rather than expecting userspace to do it.
As far as I can tell, it does handle similar things for some keyboards,
but not this one.)
next reply other threads:[~2022-11-11 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:06 Josh Triplett [this message]
2022-11-12 15:23 ` USB Lenovo ThinkPad Compact Keyboard has fn_lock inverted Jamie Lentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y26BMXn15Kbt6a2u@localhost \
--to=josh@joshtriplett.org \
--cc=1006251@bugs.debian.org \
--cc=jm@lentin.co.uk \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).