From: Jackie Dong <xy-jackie@139.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: hansg@kernel.org, platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
dongeg1@lenovo.com
Subject: Re: [PATCH v3] lenovo-wmi-hotkey: Fixed a kernel error report forsome Lenovo non-ThinkPad devices
Date: Wed, 9 Jul 2025 11:56:29 +0800 [thread overview]
Message-ID: <d43f274b-33fd-4fba-94a1-ba1ca20a9edb@139.com> (raw)
In-Reply-To: <e45af10b-fa26-d7e4-8051-093a6f9ce552@linux.intel.com>
On 7/8/25 18:07, Ilpo Järvinen wrote:
> On Tue, 8 Jul 2025, Jackie Dong wrote:
>
>> Not all of Lenovo non-ThinkPad devices support both mic mute LED (on F4)
>> and audio mute LED (on F1). Some of them only support one mute LED, some
>> of them don't have any mute LED. Add a decision to judge this device
>> support mute LED or not. Without this decision, not support both of mic
>> mute LED and audio mute LED Lenovo non-ThinkPad brand devices (including
>> Ideapad/Yoga/Xiaoxin/Gaming/ThinkBook, etc.) will report a failed message
>> with error -5.
>>
>> Signed-off-by: Jackie Dong <xy-jackie@139.com>
>> Suggested-by: Hans de Goede <hansg@kernel.org>
>> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>
> Hi Jackie,
>
> Please don't add Reviewed-by nor Tested-by tags unless they were
> explicitly given to you.
>
Hi Ilpo,
I have deleted the Reviewed-by tag in next version patch.
>> ---
>> Changes in v3:
>> - Reverse orignal logic (obj && obj->type == ACPI_TYPE_INTEGER)
>> and add new decision for led_version == 0.
>> - Optimize the descriptions based on reviewer comments.
>>
>> Changes in v2:
>> - Add warning message and then return 0 if the device support mute LED
>> abnormaly, based on Hans suggestion and Armin previous patch.
>>
>>
>> .../x86/lenovo-wmi-hotkey-utilities.c | 24 ++++++++++++++-----
>> 1 file changed, 18 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/platform/x86/lenovo-wmi-hotkey-utilities.c b/drivers/platform/x86/lenovo-wmi-hotkey-utilities.c
>> index 89153afd7015..1850992f2ea8 100644
>> --- a/drivers/platform/x86/lenovo-wmi-hotkey-utilities.c
>> +++ b/drivers/platform/x86/lenovo-wmi-hotkey-utilities.c
>> @@ -127,21 +127,30 @@ static int lenovo_super_hotkey_wmi_led_init(enum mute_led_type led_type, struct
>> else
>> return -EIO;
>
> The logic was not reversed as requested. Please change this code to:
>
> union acpi_object *obj __free(kfree) = output.pointer;
> if (!obj || obj->type != ACPI_TYPE_INTEGER)
> return -EIO;
>
> led_version = obj->integer.value;
>
It's good suggestion, I'll update it.
>> - wpriv->cdev[led_type].max_brightness = LED_ON;
>> - wpriv->cdev[led_type].flags = LED_CORE_SUSPENDRESUME;
>> + /*
>> + * Output parameters define: 0 means mute LED is not supported, Non-zero means
>> + * mute LED can be supported.
>> + */
>> + if (led_version == 0)
>> + return 0;
>> +
>>
>> switch (led_type) {
>> case MIC_MUTE:
>> - if (led_version != WMI_LUD_SUPPORT_MICMUTE_LED_VER)
>> - return -EIO;
>> + if (led_version != WMI_LUD_SUPPORT_MICMUTE_LED_VER) {
>> + pr_warn("The MIC_MUTE LED of this device isn't supported now.\n");
>
> Drop "now" (or change it to more precise explanation why).
>
I have deleted the "now" in next version patch.
>> + return 0;
>> + }
>>
>> wpriv->cdev[led_type].name = "platform::micmute";
>> wpriv->cdev[led_type].brightness_set_blocking = &lsh_wmi_micmute_led_set;
>> wpriv->cdev[led_type].default_trigger = "audio-micmute";
>> break;
>> case AUDIO_MUTE:
>> - if (led_version != WMI_LUD_SUPPORT_AUDIOMUTE_LED_VER)
>> - return -EIO;
>> + if (led_version != WMI_LUD_SUPPORT_AUDIOMUTE_LED_VER) {
>> + pr_warn("The AUDIO_MUTE LED of this device isn't supported now.\n");
>
> Ditto.
>
I have deleted the "now" in next version patch.
>> + return 0;
>> + }
>>
>> wpriv->cdev[led_type].name = "platform::mute";
>> wpriv->cdev[led_type].brightness_set_blocking = &lsh_wmi_audiomute_led_set;
>> @@ -152,6 +161,9 @@ static int lenovo_super_hotkey_wmi_led_init(enum mute_led_type led_type, struct
>> return -EINVAL;
>> }
>>
>> + wpriv->cdev[led_type].max_brightness = LED_ON;
>> + wpriv->cdev[led_type].flags = LED_CORE_SUSPENDRESUME;
>> +
>> err = devm_led_classdev_register(dev, &wpriv->cdev[led_type]);
>> if (err < 0) {
>> dev_err(dev, "Could not register mute LED %d : %d\n", led_type, err);
>>
>
Thanks a lot,
Jackie
prev parent reply other threads:[~2025-07-09 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 9:43 [PATCH v3] lenovo-wmi-hotkey: Fixed a kernel error report for some " Jackie Dong
2025-07-08 10:07 ` Ilpo Järvinen
2025-07-08 10:12 ` Ilpo Järvinen
2025-07-09 3:56 ` Jackie Dong [this message]
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=d43f274b-33fd-4fba-94a1-ba1ca20a9edb@139.com \
--to=xy-jackie@139.com \
--cc=dongeg1@lenovo.com \
--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®