From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andy@infradead.org>
Subject: Re: [PATCH] Input: soc_button_array - Add support for INT33D3 tablet-mode switch devices
Date: Thu, 14 May 2020 22:52:38 +0200 [thread overview]
Message-ID: <6e67205a-abfa-141c-ed74-d0359e5be0d8@redhat.com> (raw)
In-Reply-To: <20200514205134.136782-1-hdegoede@redhat.com>
Hi,
This should have been 2/2 of a set of 2, let me resend, sorry.
Regards,
Hans
On 5/14/20 10:51 PM, Hans de Goede wrote:
> According to the Microsoft documentation for Windows 8 convertible
> devices, these devices should implement a PNP0C60 "laptop/slate mode state
> indicator" ACPI device.
>
> This device can work in 2 ways, if there is a GPIO which directly
> indicates the device is in tablet-mode or not then the direct-gpio mode
> should be used. If there is no such GPIO, but instead the events are
> coming from e.g. the embedded-controller, then there should still be
> a PNP0C60 ACPI device and event-injection should be used to send the
> events. The drivers/platform/x86/intel-vbtn.c code is an example from
> a standardized manner of doing the latter.
>
> On various 2-in-1s with either a detachable keyboard, or with 360°
> hinges, the direct GPIO mode is indicated by an ACPI device with a
> HID of INT33D3, which contains a single GpioInt in its ACPI resource
> table, which directly indicates if the device is in tablet-mode or not.
>
> This commit adds support for this to the soc_button_array code, as
> well as for the alternative ID9001 HID which some devices use
> instead of the INT33D3 HID.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/input/misc/soc_button_array.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/input/misc/soc_button_array.c b/drivers/input/misc/soc_button_array.c
> index e3a22a61f5d9..837c787e9c4b 100644
> --- a/drivers/input/misc/soc_button_array.c
> +++ b/drivers/input/misc/soc_button_array.c
> @@ -397,6 +397,15 @@ static const struct soc_device_data soc_device_PNP0C40 = {
> .button_info = soc_button_PNP0C40,
> };
>
> +static const struct soc_button_info soc_button_INT33D3[] = {
> + { "tablet_mode", 0, EV_SW, SW_TABLET_MODE, false, false, false },
> + { }
> +};
> +
> +static const struct soc_device_data soc_device_INT33D3 = {
> + .button_info = soc_button_INT33D3,
> +};
> +
> /*
> * Special device check for Surface Book 2 and Surface Pro (2017).
> * Both, the Surface Pro 4 (surfacepro3_button.c) and the above mentioned
> @@ -459,6 +468,8 @@ static const struct soc_device_data soc_device_MSHW0040 = {
>
> static const struct acpi_device_id soc_button_acpi_match[] = {
> { "PNP0C40", (unsigned long)&soc_device_PNP0C40 },
> + { "INT33D3", (unsigned long)&soc_device_INT33D3 },
> + { "ID9001", (unsigned long)&soc_device_INT33D3 },
> { "ACPI0011", 0 },
>
> /* Microsoft Surface Devices (5th and 6th generation) */
>
prev parent reply other threads:[~2020-05-14 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 20:51 [PATCH] Input: soc_button_array - Add support for INT33D3 tablet-mode switch devices Hans de Goede
2020-05-14 20:52 ` Hans de Goede [this message]
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=6e67205a-abfa-141c-ed74-d0359e5be0d8@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).