From: Jamie Lentin <jm@lentin.co.uk>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-input@vger.kernel.org, 1006251@bugs.debian.org
Subject: Re: USB Lenovo ThinkPad Compact Keyboard has fn_lock inverted
Date: Sat, 12 Nov 2022 15:23:11 +0000 [thread overview]
Message-ID: <a031b2a5ed783b1558bceedd3041bf6a@lentin.co.uk> (raw)
In-Reply-To: <Y26BMXn15Kbt6a2u@localhost>
On 2022-11-11 17:06, Josh Triplett wrote:
> 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.
Under Windows the default actions of the Function keys are the media
keys, i.e. pressing F1 is Mute. Fn-"Mute" is F1, or enabling Fn-Lock &
"Mute". That's why when /fn_lock is 1, the Mute key is F1.
With keyboards built into Thinkpads there's a BIOS setting to invert the
behaviour of Fn-Lock (and thus have Fn keys by default), as well as
swapping Fn<->Ctrl, but there's no equivalent option for the external
keyboards.
What's the wrong way around here is hid-lenovo assumes that you want
Fn-Lock on when connecting to the keyboard, not off. My assumption at
the time was that whilst it's different to how the keyboard behaves
under Windows, it'd be a more useful default.
> (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.)
Agreed. This was something I looked into when I was adding support for
the keyboards. For yours it's a pretty trivial addition, but for the USB
variant you can't send the command in the middle of the USB interrupt
receiving the keypress, solving this seemed to require quite a lot of
boilerplate for what would have been pretty trivial in userland.
Of course, It's very easily possible that I missed something, or there's
a helper to do this sort of thing that now exists.
Cheers,
prev parent reply other threads:[~2022-11-12 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:06 USB Lenovo ThinkPad Compact Keyboard has fn_lock inverted Josh Triplett
2022-11-12 15:23 ` Jamie Lentin [this message]
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=a031b2a5ed783b1558bceedd3041bf6a@lentin.co.uk \
--to=jm@lentin.co.uk \
--cc=1006251@bugs.debian.org \
--cc=josh@joshtriplett.org \
--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