From: Armin Wolf <W_Armin@gmx.de>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com, wse@tuxedocomputers.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] platform/x86: uniwill-laptop: Prepare for extending keyboard backlight support
Date: Mon, 20 Jul 2026 15:26:09 +0200 [thread overview]
Message-ID: <20260720132611.374073-1-W_Armin@gmx.de> (raw)
This patch series contains a couple of changes suggested by
Werner Sembach from Tuxedo that are necessary for eventually
enabling keyboard backlight support for Tuxedo devices.
The first patch simply cleans up uniwill_kbd_led_init(), while
the remaining two patches make two key properties (single color
vs RGB, max intensity) configurable using the existing device
descriptor infrastructure.
Tested on a Tuxedo InfinityBook Pro 15 Gen 10 AMD.
Changes since v3:
- add Reviewed-by tag
- fix spelling issue
- reword comment in second patch
Changes since v2:
- drop 3rd patch
- add Reviewed-by tag
- reword commit description of 2nd patch
Changes since v1:
- add Suggested-by tags
Armin Wolf (2):
platform/x86: uniwill-laptop: Split uniwill_kbd_led_init()
platform/x86: uniwill-laptop: Remove single color keyboard detection
drivers/platform/x86/uniwill/uniwill-acpi.c | 119 +++++++++++---------
1 file changed, 63 insertions(+), 56 deletions(-)
--
2.39.5
next reply other threads:[~2026-07-20 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 13:26 Armin Wolf [this message]
2026-07-20 13:26 ` [PATCH v4 1/2] platform/x86: uniwill-laptop: Split uniwill_kbd_led_init() Armin Wolf
2026-07-20 13:26 ` [PATCH v4 2/2] platform/x86: uniwill-laptop: Remove single color keyboard detection Armin Wolf
2026-07-21 8:44 ` Ilpo Järvinen
2026-07-25 20:08 ` Armin Wolf
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=20260720132611.374073-1-W_Armin@gmx.de \
--to=w_armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/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®