From: "Pali Rohár" <pali.rohar@gmail.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: andy@infradead.org, mjg59@srcf.ucam.org, dvhart@infradead.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: dell-laptop: Fix bogus keyboard backlight sysfs interface
Date: Mon, 19 Jun 2017 09:57:42 +0200 [thread overview]
Message-ID: <20170619075742.GA32387@pali> (raw)
In-Reply-To: <20170619073629.14239-1-kai.heng.feng@canonical.com>
On Monday 19 June 2017 15:36:29 Kai-Heng Feng wrote:
> Dell Latitude 3160 does not have keyboard backlight, but there is a
> sysfs interface for it, which does nothing at all.
>
> KBD_LED_ON_TOKEN is the only token can be found. Since it doesn't have
*ON* really?
> KBD_LED_OFF_TOKEN or KBD_LED_AUTO_*_TOKEN, it should be safe to assume it
> does not support keyboard backlight.
>
> Models which do not use SMBIOS to control keyboard backlight, also have
> this issue. Brightness level is 0 on these models. Verified on Dell
> Inspiron 3565.
>
> Reports keyboard backlight is supported only when tokens other than
> KBD_LED_ON_TOKEN can be found, or brightness level is not 0.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
>
> v2:
> The only token can be found is actually KBD_LED_ON_TOKEN, which is BIT(5),
> instead of KBD_LED_OFF_TOKEN. Change commit log accordingly.
>
> Use token bit to make the intention more clear.
> Also consider kbd_mode_levels_count and kbd_info.levels, suggested by
> Pali Rohár.
>
> Use XOR to simplify the bitmask comparison, suggested by
> Andy Shevchenko.
>
> drivers/platform/x86/dell-laptop.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/dell-laptop.c b/drivers/platform/x86/dell-laptop.c
> index ec202094bd50..4b21fc982cb0 100644
> --- a/drivers/platform/x86/dell-laptop.c
> +++ b/drivers/platform/x86/dell-laptop.c
> @@ -1148,6 +1148,15 @@ static const int kbd_tokens[] = {
> KBD_LED_ON_TOKEN,
> };
>
> +enum kbd_led_token_bit {
> + KBD_LED_TOKEN_BIT_OFF = 0,
> + KBD_LED_TOKEN_BIT_AUTO_25,
> + KBD_LED_TOKEN_BIT_AUTO_50,
> + KBD_LED_TOKEN_BIT_AUTO_75,
> + KBD_LED_TOKEN_BIT_AUTO_100,
> + KBD_LED_TOKEN_BIT_ON,
> +};
> +
> static u16 kbd_token_bits;
>
> static struct kbd_info kbd_info;
> @@ -1510,7 +1519,12 @@ static void kbd_init(void)
> ret = kbd_init_info();
> kbd_init_tokens();
>
> - if (kbd_token_bits != 0 || ret == 0)
> + /*
> + * If brightness level is 0, or KBD_LED_ON_TOKEN is the only token,
> + * consider there is no keyboard backlight.
> + */
> + if ((ret == 0 && (kbd_info.levels || kbd_mode_levels_count)) ||
> + kbd_token_bits ^ BIT(KBD_LED_TOKEN_BIT_ON))
So in case there would be only *OFF* token then interface is exported
too... This does not seems to be good idea.
If there is machine for which firmware provides only *ON* token, then I
think we should presence for at least two tokens.
And similarly kbd_mode_levels_count needs to be checked that is at least
two (as "off" is in count).
> kbd_led_present = true;
> }
>
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-06-19 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 7:36 [PATCH v2] platform/x86: dell-laptop: Fix bogus keyboard backlight sysfs interface Kai-Heng Feng
2017-06-19 7:57 ` Pali Rohár [this message]
2017-06-19 8:39 ` Kai-Heng Feng
2017-06-19 8:47 ` Pali Rohár
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=20170619075742.GA32387@pali \
--to=pali.rohar@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.