public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Bastien Nocera <hadess@hadess.net>
Cc: Darren Hart <dvhart@infradead.org>,
	ibm-acpi-devel@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 5/6] input: Add keycodes used by Lenovo Carbon X1 2014
Date: Mon, 23 Feb 2015 07:49:51 -0300	[thread overview]
Message-ID: <1424688591.3045289.231119453.42C70082@webmail.messagingengine.com> (raw)
In-Reply-To: <1424686542.28361.10.camel@hadess.net>

On Mon, Feb 23, 2015, at 07:15, Bastien Nocera wrote:
> On Wed, 2015-02-18 at 21:34 -0200, Henrique de Moraes Holschuh wrote:
> > On Wed, 18 Feb 2015, Bastien Nocera wrote:
> > > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > 
> > This one requires an ACK from the input maintainers, or no go...
> 
> Any comments about the other patches?

The series looks mostly good, but the new keymap and attributes need to
go
in the driver documentation (Documentation/laptops/thinkpad-acpi.txt),
and some
of the commit decriptions could use an update.

You could opt to change some of those keypresses dinamically into
driver-specific
ACPI events, by setting the keymap entry to KEY_RESERVED.  The driver
will
issue HKEY events in that case. That will be an viable alternative for
some of the new
keys.

The beauty of it is that keymaps are configurable in run-time, so
userspace can
just set any key entries it wants to change to something else, and ACPI
events will be
suppressed if the entry is not set to KEY_RESERVED anymore.

We need to be careful with tpacpi_input_send_key_masked(). If any of the
codepaths
could call it from the adaptative keyboard handling code, it needs to be
updated (just
assume anything above 32 is enabled, as the firmware does not have an
event mask
for the new keycodes).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2015-02-23 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 20:53 [PATCH 5/6] input: Add keycodes used by Lenovo Carbon X1 2014 Bastien Nocera
2015-02-18 23:34 ` Henrique de Moraes Holschuh
2015-02-23 10:15   ` Bastien Nocera
2015-02-23 10:49     ` Henrique de Moraes Holschuh [this message]
2015-02-23 11:41       ` Bastien Nocera
2015-02-23 14:10         ` Henrique de Moraes Holschuh

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=1424688591.3045289.231119453.42C70082@webmail.messagingengine.com \
    --to=hmh@hmh.eng.br \
    --cc=dvhart@infradead.org \
    --cc=hadess@hadess.net \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox