The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	wse@tuxedocomputers.com
Subject: Re: [PATCH 0/7] platform/x86: uniwill-laptop: Support additional features
Date: Thu, 11 Jun 2026 17:00:54 +0200	[thread overview]
Message-ID: <5e7fd549-eb73-45d2-a40e-4c8b21bb28bb@gmx.de> (raw)
In-Reply-To: <8395fcb7-4de7-85ff-d2ae-a7eefd2dc87c@linux.intel.com>

Am 11.06.26 um 15:21 schrieb Ilpo Järvinen:
> On Wed, 10 Jun 2026, Armin Wolf wrote:
> 
>> Am 10.06.26 um 12:50 schrieb Ilpo Järvinen:
>>> On Sat, 30 May 2026, Armin Wolf wrote:
>>>
>>>> This patch series adds support for various new features to the
>>>> uniwill-laptop driver. The first patch adds support for the keyboard
>>>> backlight available on some models, while the next three patches
>>>> add support for additional WMI events, USB powershare and AC auto
>>>> boot. The last four patches finally add support for additional devices.
>>>>
>>>> The patch series depends on commit b1a9b7a904af ("leds: Introduce the
>>>> multi_max_intensity sysfs attribute")
>>>> currently sitting inside the for-leds-next branch of the LED subsystem
>>>> tree. Without said commit the first patch will apply but not build.
>>>>
>>>> All patches have been tested on my Tuxedo InfinityBook Pro 15 Gen 10
>>>> AMD and most work flawlessly, only the AC auto boot feature seems to
>>>> be broken on my device. I decided to still include the patch because
>>>> it works on other devices.
>>>>
>>>> Armin Wolf (7):
>>>>     platform/x86: uniwill-laptop: Add keyboard backlight support
>>>>     platform/x86: uniwill-laptop: Handle screen-related events
>>>>     platform/x86: uniwill-laptop: Add AC auto boot support
>>>>     platform/x86: uniwill-laptop: Add support for USB powershare
>>>>     platform/x86: uniwill-laptop: Add support for the MACHENIKE L16 Pro
>>>>     platform/x86: uniwill-laptop: Add support for the AiStone X4SP4NAL
>>>>     platform/x86: uniwill-laptop: Add lightbar support for LAPQC71A/B
>>>>
>>>>    .../ABI/testing/sysfs-driver-uniwill-laptop   |  25 +
>>>>    .../admin-guide/laptops/uniwill-laptop.rst    |  27 +
>>>>    drivers/platform/x86/uniwill/uniwill-acpi.c   | 609 +++++++++++++++++-
>>>>    drivers/platform/x86/uniwill/uniwill-wmi.h    |   2 +
>>>>    4 files changed, 650 insertions(+), 13 deletions(-)
>>>
>>> Unfortunately, I got this error after applying this series on top of
>>> review-ilpo-next:
>>>
>>> drivers/platform/x86/uniwill/uniwill-acpi.c: In function
>>> ‘uniwill_kbd_led_init’:
>>> drivers/platform/x86/uniwill/uniwill-acpi.c:1827:49: error: ‘struct
>>> mc_subled’ has no member named ‘max_intensity’; did you mean ‘intensity’?
>>>    1827 |                 data->kbd_led_mc_subled_info[i].max_intensity =
>>> KBD_LED_MAX_INTENSITY;
>>>
>>>
>> The patch series depends on commit b1a9b7a904af ("leds: Introduce the
>> multi_max_intensity sysfs attribute")
>> currently sitting inside the for-leds-next branch of the LED subsystem
>> tree.
> 
> Ah, I missed that note.
> 
> This will have to wait to the next version then. I've summoned the series
> back to patchwork queue so I won't forget it.
> 

That is totally fine. Since you are ready to merge this series as-is, i 
will start developing patches based on this series that will be send 
after the development for 7.2 has started.

Thanks,
Armin Wolf

  reply	other threads:[~2026-06-11 15:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 17:08 [PATCH 0/7] platform/x86: uniwill-laptop: Support additional features Armin Wolf
2026-05-30 17:08 ` [PATCH 1/7] platform/x86: uniwill-laptop: Add keyboard backlight support Armin Wolf
2026-07-08 19:11   ` Werner Sembach
2026-07-08 20:08     ` Armin Wolf
2026-07-08 20:15       ` Werner Sembach
2026-07-09  5:49         ` Armin Wolf
2026-07-09 13:23           ` Werner Sembach
2026-07-09 20:23             ` Armin Wolf
2026-05-30 17:08 ` [PATCH 2/7] platform/x86: uniwill-laptop: Handle screen-related events Armin Wolf
2026-05-30 17:08 ` [PATCH 3/7] platform/x86: uniwill-laptop: Add AC auto boot support Armin Wolf
2026-05-30 17:08 ` [PATCH 4/7] platform/x86: uniwill-laptop: Add support for USB powershare Armin Wolf
2026-05-30 17:08 ` [PATCH 5/7] platform/x86: uniwill-laptop: Add support for the MACHENIKE L16 Pro Armin Wolf
2026-05-30 17:08 ` [PATCH 6/7] platform/x86: uniwill-laptop: Add support for the AiStone X4SP4NAL Armin Wolf
2026-05-30 17:08 ` [PATCH 7/7] platform/x86: uniwill-laptop: Add lightbar support for LAPQC71A/B Armin Wolf
2026-07-08 20:08   ` Werner Sembach
2026-07-09  8:57     ` Ilpo Järvinen
2026-07-09 13:13       ` Werner Sembach
2026-07-09 13:45         ` Ilpo Järvinen
2026-07-09 14:06           ` Werner Sembach
2026-06-10 10:50 ` [PATCH 0/7] platform/x86: uniwill-laptop: Support additional features Ilpo Järvinen
2026-06-10 16:36   ` Armin Wolf
2026-06-11 13:21     ` Ilpo Järvinen
2026-06-11 15:00       ` Armin Wolf [this message]
2026-07-01 11:30 ` Ilpo Järvinen
2026-07-02 17:21   ` 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=5e7fd549-eb73-45d2-a40e-4c8b21bb28bb@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