From: Hans de Goede <hdegoede@redhat.com>
To: Meng Dong <whenov@gmail.com>, Ike Panhc <ike.pan@canonical.com>,
Mark Gross <mgross@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] ideapad-laptop: Fix Legion 5 Fn lock LED
Date: Wed, 18 Aug 2021 09:44:57 +0200 [thread overview]
Message-ID: <b5905cfc-db0e-72ff-745a-3439333f35b0@redhat.com> (raw)
In-Reply-To: <20210817171203.12855-1-whenov@gmail.com>
Hi,
On 8/17/21 7:12 PM, Meng Dong wrote:
> This patch fixes the bug 212671.
> Althrough the Fn lock (Fn + Esc) works on Legion 5 (R7000P), its LED
> light does not change with the state. This modification sets the Fn lock
> state to its current value on receiving the wmi event
> 8FC0DE0C-B4E4-43FD-B0F3-8871711C1294 to update the LED state.
>
> Signed-off-by: Meng Dong <whenov@gmail.com>
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> ---
> Another possible approach is to call `ideapad_input_report(priv, value)`
> to send a keycode and let the user handle the LED by echoing the current
> value of /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/fn_lock back
> into itself. But the problem with this approach is Fn+F9 and Fn+Esc
> trigger the same WMI GUID and event value and I have no idea how to
> distinguish them.
>
> drivers/platform/x86/ideapad-laptop.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
> index 784326bd72f0..48561b666547 100644
> --- a/drivers/platform/x86/ideapad-laptop.c
> +++ b/drivers/platform/x86/ideapad-laptop.c
> @@ -41,6 +41,7 @@
> static const char *const ideapad_wmi_fnesc_events[] = {
> "26CAB2E5-5CF1-46AE-AAC3-4A12B6BA50E6", /* Yoga 3 */
> "56322276-8493-4CE8-A783-98C991274F5E", /* Yoga 700 */
> + "8FC0DE0C-B4E4-43FD-B0F3-8871711C1294", /* Legion 5 */
> };
> #endif
>
> @@ -1464,6 +1465,15 @@ static void ideapad_wmi_notify(u32 value, void *context)
> case 128:
> ideapad_input_report(priv, value);
> break;
> + case 208:
> + unsigned long result;
> +
> + if (!eval_hals(priv->adev->handle, &result)) {
> + bool state = test_bit(HALS_FNLOCK_STATE_BIT, &result);
> +
> + exec_sals(priv->adev->handle, state ? SALS_FNLOCK_ON : SALS_FNLOCK_OFF);
> + }
> + break;
> default:
> dev_info(&priv->platform_device->dev,
> "Unknown WMI event: %u\n", value);
>
prev parent reply other threads:[~2021-08-18 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 17:12 [PATCH] ideapad-laptop: Fix Legion 5 Fn lock LED Meng Dong
2021-08-18 7:44 ` Hans de Goede [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=b5905cfc-db0e-72ff-745a-3439333f35b0@redhat.com \
--to=hdegoede@redhat.com \
--cc=ike.pan@canonical.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=whenov@gmail.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;
as well as URLs for NNTP newsgroup(s).