X86 platform drivers
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@just42.net>
To: Micha?? K??pie?? <kernel@kempniu.pl>
Cc: Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>, Harvey <harv@gmx.de>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: fujitsu-laptop: Fix radio LED detection
Date: Wed, 25 Oct 2017 17:03:56 +1030	[thread overview]
Message-ID: <20171025063356.GE1090@marvin.atrad.com.au> (raw)
In-Reply-To: <20171025042946.13225-1-kernel@kempniu.pl>

On Wed, Oct 25, 2017 at 06:29:46AM +0200, Micha?? K??pie?? wrote:
> Radio LED detection method implemented in commit 4f62568c1fcf
> ("fujitsu-laptop: Support radio LED") turned out to be incorrect as it
> causes a radio LED to be erroneously detected on a Fujitsu Lifebook E751
> which has a slide switch (and thus no radio LED).  Use bit 17 of
> flags_supported (the value returned by method S000 of ACPI device
> FUJ02E3) to determine whether a radio LED is present as it seems to be a
> more reliable indicator, based on comparing DSDT tables of four Fujitsu
> Lifebook models (E744, E751, S7110, S8420).
> 
> Reported-by: Heinrich Siebmanns <harv@gmx.de>
> Signed-off-by: Micha?? K??pie?? <kernel@kempniu.pl>

This seems to be a reasonable approach given the most recent set of
observations.  Assuming it tests ok on the E751:

  Reviewed-by: Jonathan Woithe <jwoithe@just42.net>

Regards
  jonathan

> ---
> I do not have a Fujitsu laptop with a radio LED for testing, so I was
> only able to check that this patch still does not cause a radio LED to
> be detected on a Lifebook S7020.
> 
> Harvey, could you please try this patch on your Lifebook E751 and see
> whether the log messages you reported disappear?  I will be happy to
> assist you off-list in case you need help with it.
> 
>  drivers/platform/x86/fujitsu-laptop.c | 14 +++++++++-----
>  1 file changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/platform/x86/fujitsu-laptop.c b/drivers/platform/x86/fujitsu-laptop.c
> index 56a8195096a2..2cfbd3fa5136 100644
> --- a/drivers/platform/x86/fujitsu-laptop.c
> +++ b/drivers/platform/x86/fujitsu-laptop.c
> @@ -691,6 +691,7 @@ static enum led_brightness eco_led_get(struct led_classdev *cdev)
>  
>  static int acpi_fujitsu_laptop_leds_register(struct acpi_device *device)
>  {
> +	struct fujitsu_laptop *priv = acpi_driver_data(device);
>  	struct led_classdev *led;
>  	int result;
>  
> @@ -724,12 +725,15 @@ static int acpi_fujitsu_laptop_leds_register(struct acpi_device *device)
>  	}
>  
>  	/*
> -	 * BTNI bit 24 seems to indicate the presence of a radio toggle
> -	 * button in place of a slide switch, and all such machines appear
> -	 * to also have an RF LED.  Therefore use bit 24 as an indicator
> -	 * that an RF LED is present.
> +	 * Some Fujitsu laptops have a radio toggle button in place of a slide
> +	 * switch and all such machines appear to also have an RF LED.  Based on
> +	 * comparing DSDT tables of four Fujitsu Lifebook models (E744, E751,
> +	 * S7110, S8420; the first one has a radio toggle button, the other
> +	 * three have slide switches), bit 17 of flags_supported (the value
> +	 * returned by method S000 of ACPI device FUJ02E3) seems to indicate
> +	 * whether given model has a radio toggle button.
>  	 */
> -	if (call_fext_func(device, FUNC_BUTTONS, 0x0, 0x0, 0x0) & BIT(24)) {
> +	if (priv->flags_supported & BIT(17)) {
>  		led = devm_kzalloc(&device->dev, sizeof(*led), GFP_KERNEL);
>  		if (!led)
>  			return -ENOMEM;
> -- 
> 2.14.2

  reply	other threads:[~2017-10-25  6:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  4:29 [PATCH] platform/x86: fujitsu-laptop: Fix radio LED detection Michał Kępień
2017-10-25  6:33 ` Jonathan Woithe [this message]
2017-10-25 13:11   ` Harvey
2017-10-27 16:49 ` Andy Shevchenko
2017-10-29 21:28   ` Michał Kępień
2017-10-30 11:21     ` Andy Shevchenko
2017-10-30 12:12       ` Jonathan Woithe
2017-10-30 14:13         ` Andy Shevchenko
2017-10-31  4:20         ` Michał Kępień
2017-10-31 10:54           ` Harvey

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=20171025063356.GE1090@marvin.atrad.com.au \
    --to=jwoithe@just42.net \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=harv@gmx.de \
    --cc=kernel@kempniu.pl \
    --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