From: Aditya Garg <aditya.garg@linux.dev>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
Linux Input Mailing List <linux-input@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andre Eikmeyer <dev@deq.rocks>
Subject: Re: [PATCH v4] HID: appletb-kbd: support layer switching on Fn double press
Date: Sat, 12 Sep 2026 01:34:03 +0530 [thread overview]
Message-ID: <78a34a46-85c1-4428-8e85-2186ae434512@linux.dev> (raw)
In-Reply-To: <4s5p7s1n-87n6-2833-s73r-s82s45862srs@xreary.bet>
On 11/09/26 10:15 pm, Jiri Kosina wrote:
> On Sat, 5 Sep 2026, Aditya Garg wrote:
>
>>> Holding Fn temporarily switches the Touch Bar between media controls and
>>> function keys. Users who want to keep the alternate layer currently need
>>> to change the mode through sysfs.
>>>
>>> An optional double_press_switch_time module parameter makes a double press
>>> persistently switch the default layer. Its value specifies the double-press
>>> interval in milliseconds, while zero leaves the behavior disabled.
>>>
>>> Signed-off-by: Aditya Garg <aditya.garg@linux.dev>
>>> Signed-off-by: Andre Eikmeyer <dev@deq.rocks>
>>> ---
>>> Changes in v2:
>>> - Added a check to ensure negative fn switch times are ignored.
>>>
>>> Changes in v3:
>>> - Renamed the backing variable to match the module parameter.
>>> - Fixed the reported code style issues.
>>>
>>> Changes in v4:
>>> - Added missing "break;" in case statements.
>>> - Change author's email to aditya.garg@linux.dev
>>
>> Now that I see it, the case statements were ending in return. break was
>> not needed. Sorry for the brainfart.
>
> Please send v5 and I will apply it.
Sent here:
https://lore.kernel.org/linux-input/20260911200019.17028-1-aditya.garg@linux.dev/T/#u
prev parent reply other threads:[~2026-09-11 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 14:37 Aditya Garg
2026-09-05 14:49 ` Aditya Garg
2026-09-11 16:45 ` Jiri Kosina
2026-09-11 20:04 ` Aditya Garg [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=78a34a46-85c1-4428-8e85-2186ae434512@linux.dev \
--to=aditya.garg@linux.dev \
--cc=bentiss@kernel.org \
--cc=dev@deq.rocks \
--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
all inboxes | Powered by JetHome®