mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: "Rong Zhang" <i@rong.moe>, "Ike Panhc" <ikepanhc@gmail.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Gergo Koteles" <soyer@irl.hu>,
	"Barnabás Pőcze" <pobrn@protonmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: ideapad-laptop: Fix FnLock not remembered among boots
Date: Mon, 7 Jul 2025 19:23:55 +0200	[thread overview]
Message-ID: <7a1addd2-9f82-4e48-9f17-7ebc991f984a@kernel.org> (raw)
In-Reply-To: <20250707163808.155876-2-i@rong.moe>

Hi,

On 7-Jul-25 6:38 PM, Rong Zhang wrote:
> On devices supported by ideapad-laptop, the HW/FW can remember the
> FnLock state among boots. However, since the introduction of the FnLock
> LED class device, it is turned off while shutting down, as a side effect
> of the LED class device unregistering sequence.
> 
> Many users always turn on FnLock because they use function keys much
> more frequently than multimedia keys. The behavior change is
> inconvenient for them. Thus, set LED_RETAIN_AT_SHUTDOWN on the LED class
> device so that the FnLock state gets remembered, which also aligns with
> the behavior of manufacturer utilities on Windows.
> 
> Fixes: 07f48f668fac ("platform/x86: ideapad-laptop: add FnLock LED class device")
> Cc: stable@vger.kernel.org
> Signed-off-by: Rong Zhang <i@rong.moe>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hansg@kernel.org>

Regards,

Hans




> ---
>  drivers/platform/x86/ideapad-laptop.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
> index b5e4da6a6779..62a72b09fc3a 100644
> --- a/drivers/platform/x86/ideapad-laptop.c
> +++ b/drivers/platform/x86/ideapad-laptop.c
> @@ -1728,7 +1728,7 @@ static int ideapad_fn_lock_led_init(struct ideapad_private *priv)
>  	priv->fn_lock.led.name                    = "platform::" LED_FUNCTION_FNLOCK;
>  	priv->fn_lock.led.brightness_get          = ideapad_fn_lock_led_cdev_get;
>  	priv->fn_lock.led.brightness_set_blocking = ideapad_fn_lock_led_cdev_set;
> -	priv->fn_lock.led.flags                   = LED_BRIGHT_HW_CHANGED;
> +	priv->fn_lock.led.flags                   = LED_BRIGHT_HW_CHANGED | LED_RETAIN_AT_SHUTDOWN;
>  
>  	err = led_classdev_register(&priv->platform_device->dev, &priv->fn_lock.led);
>  	if (err)


  reply	other threads:[~2025-07-07 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 16:38 [PATCH 0/2] platform/x86: ideapad-laptop: Fix FnLock & kbd backlight " Rong Zhang
2025-07-07 16:38 ` [PATCH 1/2] platform/x86: ideapad-laptop: Fix FnLock " Rong Zhang
2025-07-07 17:23   ` Hans de Goede [this message]
2025-07-07 16:38 ` [PATCH 2/2] platform/x86: ideapad-laptop: Fix kbd backlight " Rong Zhang
2025-07-07 17:24   ` Hans de Goede
2025-07-08 10:24 ` [PATCH 0/2] platform/x86: ideapad-laptop: Fix FnLock & " 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=7a1addd2-9f82-4e48-9f17-7ebc991f984a@kernel.org \
    --to=hansg@kernel.org \
    --cc=i@rong.moe \
    --cc=ikepanhc@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.com \
    --cc=soyer@irl.hu \
    --cc=stable@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®