From: Hijae Song <hijae99@gmail.com>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: ayaneo-flip-kb: Add driver for keyboard backlight
Date: Sun, 8 Nov 2026 22:55:05 +0900 [thread overview]
Message-ID: <20261108135505.67330-1-hijae99@gmail.com> (raw)
In-Reply-To: <CAGwozwEKXJGBY5oZtdrrzfK-aOyYu5GaiOqkejSqbCPdeq0UJg@mail.gmail.com>
Hi Antheas,
Thanks for the feedback.
> If this is an actual keyboard product on the market and Ayaneo is
> sourcing the part for their device, look-up similar devices and kernel
> drivers.
I checked. hid-sigmamicro only fixes the 0x0059 report descriptor, and
I found no SiGma Micro backlight driver on lore.
> The name of the driver cannot be -flip-kb. You need to make sure it is
> generic enough to match most Ayaneo devices.
1c4f:007c also appears on the AYANEO Slide in hhd-dev/hwinfo, with the
same vendor interface (report ID 0x41, 7-byte feature report). I only
have a Flip KB, so I can only test the byte layout there.
Matias's hid-ayaneo already claims 1c4f:0002 behind a DMI check for
AYANEO 3. Would you prefer that I add 007c backlight support to
hid-ayaneo once it is merged, or keep a separate driver named after
the chip? I lean towards hid-ayaneo, since the Slide may work the same
way, but I would like your view first.
I will also fix the two sashiko comments in v2.
Thanks,
Hijae
next prev parent reply other threads:[~2026-11-08 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 11:07 [PATCH] HID: ayaneo-flip-kb: Add driver for keyboard backlight Hijae Song
2026-11-08 11:24 ` sashiko-bot
2026-11-08 12:19 ` Antheas Kapenekakis
2026-11-08 13:55 ` Hijae Song [this message]
2026-11-08 14:26 ` Antheas Kapenekakis
2026-11-08 14:28 ` Antheas Kapenekakis
2026-11-08 14:30 ` Antheas Kapenekakis
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=20261108135505.67330-1-hijae99@gmail.com \
--to=hijae99@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.