From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mario.Limonciello@dell.com
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: dell-laptop and separate AC timeouts on some Dell systems
Date: Fri, 7 Apr 2017 23:55:20 +0200 [thread overview]
Message-ID: <201704072355.20831@pali> (raw)
In-Reply-To: <ac73b849a1de43b28ea87f92f4f95c1c@ausx13mpc120.AMER.DELL.COM>
[-- Attachment #1: Type: Text/Plain, Size: 2184 bytes --]
Hi!
On Friday 07 April 2017 21:33:53 Mario.Limonciello@dell.com wrote:
> Pali,
>
> For some time there have been folks reporting some issues where
> keyboard backlight setting is failing on various Dell systems
> (https://github.com/dell/libsmbios/issues/3). I've been circling
> around internally to find out what's going on. This affects a number
> of systems from the last year or so.
Great!
> What is happening is that some platforms support an alternate
> keyboard timeout while on AC. The old "timeout" value is treated as
> just a battery timeout and the separate value is the AC timeout.
> Unfortunately if the AC timeout is /not/ set in the timeout
> setting/update request, this will fail.
So in case notebook is running on AC and we want to change timeout for
keyboard backlight, we need to tell smbios two timeouts, one for battery
and one for AC?
> As a result I prototyped a few changes for this at the libsmbios
> branch here:
> https://github.com/dell/libsmbios/commits/fix-g8-keyboard-backlight
Can you update also documentation which is at the end of file? It would
help for kernel implementation.
> It's not yet requested for merging because I still don't know why
> the request to supported features returns "Always On" still (that
> shouldn't be supported).
It looks like that "Always On" mode is reported by smbios by supported,
but setting it will cause failure. Any idea where is a problem? Probably
Dell firmware bug? Or needs to be that mode handled specially?
> As far as I can tell this doesn't really map well to how the keyboard
> backlight driver in the kernel works today, so I wanted to raise
> this to you to discuss what the best way to handle it is. One of
> these systems can be detected by the presence of the token 0x451.
> When that is found, the additional timeout unit and value should be
> sent with the requests.
>
> Can you let me know your thoughts?
I think that extending struct kbd_state should work.
There are already functions dell_send_intensity() and
dell_get_intensity() which handle state based on battery/AC mode.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2017-04-07 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 19:33 dell-laptop and separate AC timeouts on some Dell systems Mario.Limonciello
2017-04-07 21:55 ` Pali Rohár [this message]
2017-04-07 22:56 ` Mario.Limonciello
2017-04-07 23:22 ` Pali Rohár
2017-04-08 2:09 ` Mario.Limonciello
2017-04-08 7:19 ` 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=201704072355.20831@pali \
--to=pali.rohar@gmail.com \
--cc=Mario.Limonciello@dell.com \
--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.