From: Werner Sembach <wse@tuxedocomputers.com>
To: Armin Wolf <W_Armin@gmx.de>,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] platform/x86: uniwill-laptop: Remove single color keyboard detection
Date: Wed, 15 Jul 2026 17:16:33 +0200 [thread overview]
Message-ID: <7efb476a-673e-46e3-9845-dcedca76c63a@tuxedocomputers.com> (raw)
In-Reply-To: <20260710223544.49602-3-W_Armin@gmx.de>
Am 11.07.26 um 00:35 schrieb Armin Wolf:
> It turns out that the code for detecting single color keyboards
> might not work correctly on future models. Remove it and use the
> device descriptor instead.
Technically: It already doesn't work reliable on old devices, that's why the
device list inside the init function was required. This patch is basically to
move this to the device_descriptor struct that is already present.
>
> Suggested-by: Werner Sembach <wse@tuxedocomputers.com>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
> drivers/platform/x86/uniwill/uniwill-acpi.c | 32 +++++++--------------
> 1 file changed, 11 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/platform/x86/uniwill/uniwill-acpi.c b/drivers/platform/x86/uniwill/uniwill-acpi.c
> index d27f316800f6..4591ee299a90 100644
> --- a/drivers/platform/x86/uniwill/uniwill-acpi.c
> +++ b/drivers/platform/x86/uniwill/uniwill-acpi.c
> @@ -255,6 +255,7 @@
> #define FAN_CURVE_LENGTH 5
>
> #define EC_ADDR_KBD_STATUS 0x078C
> +/* Unreliable */
> #define KBD_WHITE_ONLY BIT(0)
> #define KBD_POWER_OFF BIT(1)
> #define KBD_TURBO_LEVEL_MASK GENMASK(3, 2)
> @@ -400,7 +401,7 @@ struct uniwill_data {
> u8 lightbar_max_brightness;
> struct led_classdev_mc led_mc_cdev;
> struct mc_subled led_mc_subled_info[LED_CHANNELS];
> - bool single_color_kbd;
> + bool kbd_led_single_color;
> u8 kbd_led_max_brightness;
> unsigned int last_kbd_status;
> union {
> @@ -426,6 +427,7 @@ struct uniwill_battery_entry {
>
> struct uniwill_device_descriptor {
> unsigned int features;
> + bool kbd_led_single_color;
Why do this as a bool instead of a UNIWILL_FEATURE_* define? We already have
mutually exclusive UNIWILL_FEATURE_* defines for the charging modes.
Best regards
Werner
> u8 kbd_led_max_brightness;
> u8 lightbar_max_brightness;
> /* Executed during driver probing */
> @@ -1629,7 +1631,7 @@ static int uniwill_notify_kbd_led(struct uniwill_data *data, int brightness)
> struct led_classdev *led_cdev;
> int ret;
>
> - if (data->single_color_kbd)
> + if (data->kbd_led_single_color)
> led_cdev = &data->kbd_led_cdev;
> else
> led_cdev = &data->kbd_led_mc_cdev.led_cdev;
> @@ -1858,24 +1860,7 @@ static int uniwill_kbd_led_init(struct uniwill_data *data)
> if (ret < 0)
> return ret;
>
> - switch (data->project_id) {
> - case PROJECT_ID_PF:
> - case PROJECT_ID_PF4MU_PF4MN_PF5MU:
> - case PROJECT_ID_PH4TRX1:
> - case PROJECT_ID_PH4TUX1:
> - case PROJECT_ID_PH4TQX1:
> - case PROJECT_ID_PH6TRX1:
> - case PROJECT_ID_PH6TQXX:
> - case PROJECT_ID_PHXAXXX:
> - case PROJECT_ID_PHXPXXX:
> - data->single_color_kbd = true;
> - break;
> - default:
> - data->single_color_kbd = regval & KBD_WHITE_ONLY;
> - break;
> - }
> -
> - if (data->single_color_kbd)
> + if (data->kbd_led_single_color)
> return uniwill_white_kbd_led_init(data);
>
> return uniwill_rgb_kbd_led_init(data);
> @@ -2351,6 +2336,7 @@ static int uniwill_probe(struct platform_device *pdev)
> return ret;
>
> data->features = device_descriptor.features;
> + data->kbd_led_single_color = device_descriptor.kbd_led_single_color;
> data->kbd_led_max_brightness = device_descriptor.kbd_led_max_brightness;
> data->lightbar_max_brightness = device_descriptor.lightbar_max_brightness;
>
> @@ -2580,7 +2566,7 @@ static int uniwill_resume_kbd_led(struct uniwill_data *data)
> if (ret < 0)
> return ret;
>
> - if (data->single_color_kbd)
> + if (data->kbd_led_single_color)
> return 0;
>
> return regmap_write_bits(data->regmap, EC_ADDR_TRIGGER, RGB_APPLY_COLOR, RGB_APPLY_COLOR);
> @@ -2687,6 +2673,7 @@ static struct uniwill_device_descriptor machenike_l16p_descriptor __initdata = {
> UNIWILL_FEATURE_KEYBOARD_BACKLIGHT |
> UNIWILL_FEATURE_AC_AUTO_BOOT |
> UNIWILL_FEATURE_USB_POWERSHARE,
> + .kbd_led_single_color = false,
> .kbd_led_max_brightness = 4,
> };
>
> @@ -2869,6 +2856,7 @@ static struct uniwill_device_descriptor x4sp4nal_descriptor __initdata = {
> UNIWILL_FEATURE_KEYBOARD_BACKLIGHT |
> UNIWILL_FEATURE_AC_AUTO_BOOT |
> UNIWILL_FEATURE_USB_POWERSHARE,
> + .kbd_led_single_color = true,
> .kbd_led_max_brightness = 2,
> };
>
> @@ -3363,6 +3351,8 @@ static int __init uniwill_init(void)
> if (force) {
> /* Assume that the device supports all features except the charge limit */
> device_descriptor.features = UINT_MAX & ~UNIWILL_FEATURE_BATTERY_CHARGE_LIMIT;
> + /* Some models only have a (white) single color keyboard backlight */
> + device_descriptor.kbd_led_single_color = false;
> /* Some models only support 3 brightness levels */
> device_descriptor.kbd_led_max_brightness = 4;
> /* Some models only support 36 brightness levels per color component */
next prev parent reply other threads:[~2026-07-15 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 22:35 [PATCH v2 0/3] platform/x86: uniwill-laptop: Prepare for extending keyboard backlight support Armin Wolf
2026-07-10 22:35 ` [PATCH v2 1/3] platform/x86: uniwill-laptop: Split uniwill_kbd_led_init() Armin Wolf
2026-07-15 15:12 ` Werner Sembach
2026-07-15 23:56 ` Armin Wolf
2026-07-16 15:10 ` Werner Sembach
2026-07-10 22:35 ` [PATCH v2 2/3] platform/x86: uniwill-laptop: Remove single color keyboard detection Armin Wolf
2026-07-15 15:16 ` Werner Sembach [this message]
2026-07-15 23:59 ` Armin Wolf
2026-07-10 22:35 ` [PATCH v2 3/3] platform/x86: uniwill-laptop: Make KBD_LED_MAX_INTENSITY configurable Armin Wolf
2026-07-15 15:19 ` Werner Sembach
2026-07-16 15:12 ` Werner Sembach
2026-07-16 16:20 ` 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=7efb476a-673e-46e3-9845-dcedca76c63a@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=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 \
/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