Linux LED subsystem development
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>,
	ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
	chumuzero@gmail.com, corbet@lwn.net, cs@tuxedo.de,
	wse@tuxedocomputers.com, ggo@tuxedocomputers.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, rdunlap@infradead.org,
	linux-leds@vger.kernel.org, lee@kernel.org, pobrn@protonmail.com
Subject: Re: [External] : [PATCH 1/3] platform/x86: Add Uniwill WMI driver
Date: Wed, 16 Jul 2025 18:37:30 +0200	[thread overview]
Message-ID: <b0ac5ea8-e18c-4460-8366-efef4f6e9cc6@gmx.de> (raw)
In-Reply-To: <2cc8f650-e917-4bed-80f0-e74b37a426f5@oracle.com>

Am 12.07.25 um 13:46 schrieb ALOK TIWARI:

>
>> +    /* Reported when the user locks/unlocks the super key */
>> +    { KE_IGNORE,    UNIWILL_OSD_SUPER_KEY_LOCK_ENABLE,    { 
>> KEY_UNKNOWN }},
>> +    { KE_IGNORE,    UNIWILL_OSD_SUPER_KEY_LOCK_DISABLE,    { 
>> KEY_UNKNOWN }},
>> +
>> +    /* Reported in manual mode when toggling the airplane mode 
>> status */
>> +    { KE_KEY,    UNIWILL_OSD_RFKILL,            { KEY_RFKILL }},
>> +
>> +    /* Reported when user wants to cycle the platform profile */
>> +    { KE_IGNORE,    UNIWILL_OSD_PERFORMANCE_MODE_TOGGLE,    { 
>> KEY_UNKNOWN }},
>> +
>> +    /* Reported when the user wants to adjust the brightness of the 
>> keyboard  */
>
> remove extra " " after keyboard

Will do.

Thanks,
Armin Wolf

>
>> +    { KE_KEY, UNIWILL_OSD_KBDILLUMDOWN,        { KEY_KBDILLUMDOWN }},
>> +    { KE_KEY,    UNIWILL_OSD_KBDILLUMUP,            { KEY_KBDILLUMUP 
>> }},
>> +
>> +    /* Reported when the user wants to toggle the microphone mute 
>> status */
>> +    { KE_KEY,    UNIWILL_OSD_MIC_MUTE,            { KEY_MICMUTE }},
>> +
>> +    /* Reported when the user locks/unlocks the Fn key */
>> +    { KE_IGNORE,    UNIWILL_OSD_FN_LOCK,            { KEY_FN_ESC }},
>> +
>> +    /* Reported when the user wants to toggle the brightness of the 
>> keyboard */
>
>
> Thanks,
> Alok
>

  reply	other threads:[~2025-07-16 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-12 11:23 [PATCH 0/3] platform/x86: Add support for Uniwill laptop features Armin Wolf
2025-07-12 11:23 ` [PATCH 1/3] platform/x86: Add Uniwill WMI driver Armin Wolf
2025-07-12 11:46   ` [External] : " ALOK TIWARI
2025-07-16 16:37     ` Armin Wolf [this message]
2025-07-12 11:23 ` [PATCH 2/3] platform/x86: Add Uniwill laptop driver Armin Wolf
2025-07-12 12:31   ` [External] : " ALOK TIWARI
2025-07-16 16:47     ` Armin Wolf
2025-07-13  2:56   ` kernel test robot
2025-07-12 11:23 ` [PATCH 3/3] Documentation: laptops: Add documentation for uniwill laptops Armin Wolf
2025-07-12 12:54   ` [External] : " ALOK TIWARI
2025-07-16 16:51     ` 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=b0ac5ea8-e18c-4460-8366-efef4f6e9cc6@gmx.de \
    --to=w_armin@gmx.de \
    --cc=alok.a.tiwari@oracle.com \
    --cc=chumuzero@gmail.com \
    --cc=corbet@lwn.net \
    --cc=cs@tuxedo.de \
    --cc=ggo@tuxedocomputers.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.com \
    --cc=rdunlap@infradead.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