mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: W_Armin@gmx.de, Hans de Goede <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] platform/x86/uniwill: Handle more WMI events required for TUXEDO devices
Date: Thu, 20 Nov 2025 12:03:02 +0100	[thread overview]
Message-ID: <ed4d19d3-a438-4e0a-9feb-1c62edef46d1@tuxedocomputers.com> (raw)
In-Reply-To: <ecc8e175-af33-4607-a720-5c380f7b5622@tuxedocomputers.com>


Am 20.11.25 um 11:59 schrieb Werner Sembach:
> Hi Ilpo,
>
> Am 20.11.25 um 11:44 schrieb Ilpo Järvinen:
>> On Wed, 19 Nov 2025, Werner Sembach wrote:
>>
>>> Am 18.11.25 um 16:02 schrieb Werner Sembach:
>>>> Handle some more WMI events that are triggered on TUXEDO devices.
>> To avoid another round-trip and a version, please write a bit more what
>> this is about than extremely vague "some".
>>
> ofc:
>
> I tested 3 more devices (InfinityBook 15 Gen9 Intel, Stellaris 16 Gen5 AMD and 
> Intel) and found that these send additional WMI events that the devices Armin 
> tested didn't.
>
> These are: UNIWILL_OSD_MUTE, UNIWILL_OSD_WEBCAM_TOGGLE, and 
> UNIWILL_OSD_DC_ADAPTER_CHANGED
>
> I also went through our out-of-tree driver where additional WMI events are 
> bound: UNIWILL_OSD_RADIOON, UNIWILL_OSD_RADIOOFF, and UNIWILL_OSD_KB_LED_LEVEL*
>
> While I don't know which devices exactly use them, at least one device does, 
> otherwise we wouldn't have them there. Also I don't see any harm in binding 
> them, so I did.
Forgot the most important part: Why i bound them even when some are just 
ignored: This avoids warning spam in dmesg about unbound events.
>
> Best Regards,
>
> Werner

  reply	other threads:[~2025-11-20 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 15:02 [PATCH v2 0/2] Start of upstream support for TUXEDO NB02 devices Werner Sembach
2025-11-18 15:02 ` [PATCH v2 1/2] platform/x86/uniwill: Handle more WMI events required for TUXEDO devices Werner Sembach
2025-11-19 20:27   ` Werner Sembach
2025-11-20 10:44     ` Ilpo Järvinen
2025-11-20 10:59       ` Werner Sembach
2025-11-20 11:03         ` Werner Sembach [this message]
2025-11-20 16:31           ` Ilpo Järvinen
2025-11-20 20:52             ` Werner Sembach
2025-11-18 15:02 ` [PATCH v2 2/2] platform/x86/uniwill: Add " Werner Sembach
2025-11-20 10:46   ` Ilpo Järvinen

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=ed4d19d3-a438-4e0a-9feb-1c62edef46d1@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

all inboxes | Powered by JetHome®