BPF List
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH] Suppress bogus F13 trigger on Sirius keyboard full fan shortcut
Date: Fri, 10 Jan 2025 17:57:45 +0100	[thread overview]
Message-ID: <864114f2-e2b2-410c-98bd-d9e18da74aec@tuxedocomputers.com> (raw)
In-Reply-To: <20250109183723.190507-1-wse@tuxedocomputers.com>

Am 09.01.25 um 19:37 schrieb Werner Sembach:
> The TUXEDO Sirius 15 Gen1 and the TUXEDO Sirius 15 Gen2 Notebooks have an
> additional "fan" key next to F12.
>
> Pressing it alone sends a F14 key press which can be bound by user space.
>
> Pressing it while holding the FN key triggers two things:
> - The EC firmware locks the fan speed of the internal fans at 100%
> - F13 key press is registered which by default is already bound in xkb and
>    desktop environments (e.g. in KDE Plasma it launches system settings)
>
> To avoid this unexpected double duty of the FN shortcut, this bpf program
> suppresses the F13 key press.
>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
This patch is also discussed (and more up to date) here: 
https://gitlab.freedesktop.org/libevdev/udev-hid-bpf/-/merge_requests/166

      reply	other threads:[~2025-01-10 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 18:37 [PATCH] Suppress bogus F13 trigger on Sirius keyboard full fan shortcut Werner Sembach
2025-01-10 16:57 ` Werner Sembach [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=864114f2-e2b2-410c-98bd-d9e18da74aec@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=bentiss@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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