From: Bastien Nocera <hadess@hadess.net>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Stefan Brüns" <stefan.bruens@rwth-aachen.de>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
Andy Shevchenko <andy@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
AceLan Kao <acelan.kao@canonical.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>
Subject: Re: [PATCH 0/4] platform/x86: intel-vbtn: Add support for several more switches/buttons
Date: Mon, 06 Nov 2017 13:54:25 +0100 [thread overview]
Message-ID: <1509972865.2869.112.camel@hadess.net> (raw)
In-Reply-To: <CAHp75VfxpUJRdp9hKnPnJ7-7Kfo=DnTm-NRvE-KCQ2ZJ6eehNA@mail.gmail.com>
On Sun, 2017-11-05 at 14:31 +0200, Andy Shevchenko wrote:
> On Fri, Nov 3, 2017 at 9:03 PM, Stefan Brüns
> <stefan.bruens@rwth-aachen.de> wrote:
> > Currently, intel-vbtn only supports the most relevant buttons,
> > although
> > there are several more events, mostly in use by convertibles.
> >
> > This series adds support for three more events. One of these events
> > is a switch (SW_*) event, which is currently not working when using
> > sparse keymaps. The first patch fixes this combination.
> >
> > The second patch adds support for the SW_TABLET_MODE switch, which
> > is used by current convertibles.
> >
> > The third patch adds support for the KEY_ROTATE_DISPLAY. On the
> > Dell
> > XPS 12 (9Q33), rotation lock is implemented as a button to toggle
> > between locked and unlocked state. In locked state, the
> > accelerometer
> > should be ignored, while in unlocked the screen contents should
> > autorotate based on the tablet orientation. The same functionality
> > is likely implemented as a switch (SW_ROTATE_LOCK event) on
> > different
> > hardware.
> >
> > The fourth patch adds support for the "Windows logo" button/key
> > found on
> > the XPS 12 display (i.e. in tablet mode, it is the only key
> > reachable).
> > The Lenovo Helix 2 has an equivalent touch button. The event
> > currently
> > uses KEY_MENU, although a distinct key code may be a better choice.
> >
>
> All, except first, are applied to my review and testing queue,
> thanks!
>
> >
> > Stefan Brüns (4):
> > Input: sparse-keymap - send sync event for KE_SW/KW_VSW
> > platform/x86: intel-vbtn: support SW_TABLET_MODE
> > platform/x86: intel-vbtn: support KEY_ROTATE_DISPLAY
> > platform/x86: intel-vbtn: support panel front button
KEY_MENU is the key for the contextual menu. You need to use
KEY_LEFTMETA. See 791738be57473fddaf393dcedcef31b577231aaa which does
this for soc_button_array.
Cheers
next prev parent reply other threads:[~2017-11-06 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 19:03 [PATCH 0/4] platform/x86: intel-vbtn: Add support for several more switches/buttons Stefan Brüns
2017-11-05 12:31 ` Andy Shevchenko
2017-11-06 12:41 ` Bastien Nocera
2017-11-17 11:31 ` Andy Shevchenko
2017-11-06 12:54 ` Bastien Nocera [this message]
2017-11-06 15:25 ` Brüns, Stefan
2017-11-06 15:36 ` Bastien Nocera
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=1509972865.2869.112.camel@hadess.net \
--to=hadess@hadess.net \
--cc=acelan.kao@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stefan.bruens@rwth-aachen.de \
/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