linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: input question: ambient light sensor button
Date: Tue, 19 Nov 2013 13:27:36 -0800	[thread overview]
Message-ID: <20131119212736.GA25784@core.coreip.homeip.net> (raw)
In-Reply-To: <201311141302.33384@pali>

On Thu, Nov 14, 2013 at 01:02:31PM +0100, Pali Rohár wrote:
> On Wednesday 13 November 2013 17:28:40 Dmitry Torokhov wrote:
> > On Wed, Nov 13, 2013 at 11:47:18AM +0100, Jiri Kosina wrote:
> > > On Sun, 15 Sep 2013, Pali Rohár wrote:
> > > > I do not know where to ask this question, but I think that
> > > > kernel developers could help me.
> > > > 
> > > > I have notebook with one special button on keyboard which
> > > > is designed for turning ambient light sensor on and off.
> > > > By default pressing button do nothing (I can turn ambient
> > > > light sensor on/off via sysfs platform wmi module).
> > > > Button press is reported by kernel input device AT
> > > > Translated Set 2 keyboard and reports it as button
> > > > "touchpad off".
> > > > 
> > > > Of course "touchpad off" is incorrect and I'd like to ask
> > > > which kernel key or button from
> > > > /usr/include/linux/input.h should be mapped for my
> > > > ambient light sensor button? Is there already some? And
> > > > what is strategy for allocating KEY_* and BTN_* numbers?
> > > 
> > > This is maintained by Dmitry, so he's the one to answer
> > > this. I am adding him to CC.
> > 
> > I guess we need patch adding
> > 
> > 	#define KEY_ALS_TOGGLE	0x230
> > 
> > Thanks.
> 
> So there is no good key for als yet?

No, but if you send me a patch adding it I will gladly apply it.

Thanks.

-- 
Dmitry

  reply	other threads:[~2013-11-19 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-15 13:53 input question: ambient light sensor button Pali Rohár
2013-11-13 10:47 ` Jiri Kosina
2013-11-13 16:28   ` Dmitry Torokhov
2013-11-14 12:02     ` Pali Rohár
2013-11-19 21:27       ` Dmitry Torokhov [this message]
2013-11-20 14:50         ` Pali Rohár
2013-11-20 15:59           ` Benjamin Tissoires
2013-11-22 11:13             ` Pali Rohár
2013-11-26 19:19               ` Dmitry Torokhov

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=20131119212736.GA25784@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).