public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Daniel Silverstone <dsilvers@simtec.co.uk>
Cc: Richard Hughes <hughsient@gmail.com>,
	linux-acpi@vger.kernel.org, toshiba_acpi@memebeam.org,
	linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: [PATCH] toshiba_acpi: Add full hotkey support
Date: Fri, 6 Mar 2009 10:09:51 +0000	[thread overview]
Message-ID: <20090306100951.GA6268@srcf.ucam.org> (raw)
In-Reply-To: <1236333861.19146.9.camel@petitemort>

On Fri, Mar 06, 2009 at 10:04:21AM +0000, Daniel Silverstone wrote:
> On Fri, 2009-03-06 at 09:56 +0000, Matthew Garrett wrote:
> > Yes, it'll be as functional as it was previously. They can be remapped 
> > on machines that have a different keymap.
> 
> Since I don't understand the input layer well enough yet, can you
> confirm if it is possible to add new mappings in without changing the
> source? I.E. if laptop <foo> has another hotkey not yet considered, is
> it just an FDI for hal, or is it a source change in the kernel?

Yes, the remapping can be done from userspace.

> > > How will it interact with software stacks like HAL when the lock button
> > > is pressed?
> > I don't really understand the question?
> 
> It was more: will events come out of both the notify method *and*
> the /proc/acpi/toshiba/keys stuff, or will they only come out of the
> notify method if it can be enabled? (I'm just trying to establish that
> things polling /proc/acpi/toshiba/keys won't end up causing duplicated
> events).

Either the kernel or userspace will get the event, but not both. There's 
an argument for disabling the input code if /proc/acpi/toshiba/keys is 
open in order to avoid breaking anything that expects to get the code 
itself.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-03-06 10:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  0:39 [PATCH] toshiba_acpi: Add full hotkey support Matthew Garrett
2009-03-06  0:52 ` Matthew Garrett
2009-03-06  9:08   ` Richard Hughes
2009-03-06  9:47     ` Daniel Silverstone
2009-03-06  9:56       ` Matthew Garrett
2009-03-06 10:04         ` Daniel Silverstone
2009-03-06 10:09           ` Matthew Garrett [this message]
2009-03-06 10:12             ` Daniel Silverstone
2009-03-06 10:15               ` Matthew Garrett
2009-03-06 10:21                 ` Daniel Silverstone
2009-03-06 18:49                   ` Andrey Borzenkov
2009-03-06 18:53                     ` Matthew Garrett
2009-03-06 18:37   ` Andrey Borzenkov
2009-03-06 18:44     ` Matthew Garrett
2009-03-06 18:57       ` Andrey Borzenkov
2009-03-07  7:27   ` Andrey Borzenkov
2009-03-07 15:06     ` Matthew Garrett
2009-03-07 15:38       ` Andrey Borzenkov
2009-03-07 15:44         ` Matthew Garrett
2009-03-07 20:19           ` Richard Hughes
2009-03-07 20:26             ` Matthew Garrett
2009-03-08  8:33               ` Richard Hughes
2009-03-08 14:29                 ` Andrey Borzenkov
2009-03-08 14:36                 ` Matthew Garrett
2009-03-09 17:11                 ` Len Brown

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=20090306100951.GA6268@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=dsilvers@simtec.co.uk \
    --cc=hughsient@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toshiba_acpi@memebeam.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