From: "Pali Rohár" <pali.rohar@gmail.com>
To: Henk <henk.vergonet@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH]: dell-wmi: Found location of 'auto brightness' key in dmi table
Date: Wed, 18 Jan 2017 20:15:55 +0100 [thread overview]
Message-ID: <201701182015.55214@pali> (raw)
In-Reply-To: <CAMFK4TO=Nt56Ygs0gKWbj+JoEfx7gG=Ug_3Cid-g3Y5uSNtuzw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2049 bytes --]
On Wednesday 18 January 2017 20:06:11 Henk wrote:
> No need for user space application, this is handled by dell-wmi.c
> itself and the key is translated into a regular linux key-code like
> the keys for brightness up/down.
>
> For the latter these are already translated to:
> #define KEY_BRIGHTNESSDOWN 224
> #define KEY_BRIGHTNESSUP 225
>
> Now with this patch adds support for:
> #define KEY_BRIGHTNESS_AUTO 244
>
> See the enclosed picture for actual key
So... this key enable/disable automatic display brightness based on
integrated ALS sensors. From your description "Found location of 'auto
brightness'" I did not understand what exactly you mean... As I know
these Dell keyboards, picture helped me :-) I would suggest to describe
your change more preciously but patch is OK for me.
> 2017-01-18 19:33 GMT+01:00 Pali Rohár <pali.rohar@gmail.com>:
> > On Wednesday 18 January 2017 19:27:00 you wrote:
> > > Tested on Dell Lattitude E6500.
> > >
> > > Signed-off-by: Henk Vergonet <henk.vergonet@gmail.com>
> > >
> > > diff --git a/drivers/platform/x86/dell-wmi.c
> > > b/drivers/platform/x86/dell-wmi.c
> > > index 75e6370..2949aee 100644
> > > --- a/drivers/platform/x86/dell-wmi.c
> > > +++ b/drivers/platform/x86/dell-wmi.c
> > > @@ -229,7 +229,7 @@ static const u16 bios_to_linux_keycode[256]
> > > __initconst = {
> > >
> > > [18] = KEY_PROG1,
> > > [19] = KEY_BRIGHTNESSDOWN,
> > > [20] = KEY_BRIGHTNESSUP,
> > >
> > > - [21] = KEY_UNKNOWN,
> > > + [21] = KEY_BRIGHTNESS_AUTO,
> > >
> > > [22] = KEY_KBDILLUMTOGGLE,
> > > [23] = KEY_UNKNOWN,
> > > [24] = KEY_SWITCHVIDEOMODE,
> >
> > Hi! Can you describe more details? Is that key handled by
> > notebook's firmware itself or do you need some userspace
> > application for handling?
> >
> > And what should that key suppose to do on your notebook?
> >
> > --
> > Pali Rohár
> > pali.rohar@gmail.com
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
parent reply other threads:[~2017-01-18 19:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMFK4TO=Nt56Ygs0gKWbj+JoEfx7gG=Ug_3Cid-g3Y5uSNtuzw@mail.gmail.com>]
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=201701182015.55214@pali \
--to=pali.rohar@gmail.com \
--cc=henk.vergonet@gmail.com \
--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.