From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH resend 1/2] Input: soc_button_array - Add active_low setting to soc_button_info
Date: Sun, 13 Sep 2020 23:09:38 -0700 [thread overview]
Message-ID: <20200914060938.GL1665100@dtor-ws> (raw)
In-Reply-To: <20200826150601.12137-2-hdegoede@redhat.com>
On Wed, Aug 26, 2020 at 05:06:00PM +0200, Hans de Goede wrote:
> This is a preparation patch for adding support for Intel INT33D3
> ACPI devices. These INT33D3 devices follow yet another Intel defined
> (but not documented) ACPI GPIO button standard.
>
> Unlike the ACPI GPIO button devices supported so far, the GPIO used in
> the INT33D3 devices is active-high, rather then active-low.
>
> This commit makes setting the gpio_keys_button.active_low flag
> configurable through the soc_button_info struct and enables it for all
> currently supported devices.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2020-09-14 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 15:05 [PATCH resend 0/2] Input: soc_button_array - Add support for INT33D3 ACPI tablet-switch device Hans de Goede
2020-08-26 15:06 ` [PATCH resend 1/2] Input: soc_button_array - Add active_low setting to soc_button_info Hans de Goede
2020-09-14 6:09 ` Dmitry Torokhov [this message]
2020-08-26 15:06 ` [PATCH resend 2/2] Input: soc_button_array - Add support for INT33D3 tablet-mode switch devices Hans de Goede
2020-09-14 6:09 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2020-06-20 12:34 [PATCH resend 0/2] " Hans de Goede
2020-06-20 12:34 ` [PATCH resend 1/2] Input: soc_button_array - Add active_low setting to soc_button_info Hans de Goede
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=20200914060938.GL1665100@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@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).