From: Hans de Goede <hdegoede@redhat.com>
To: Mark Pearson <markpearson@lenovo.com>
Cc: dmitry.torokhov@gmail.com, platform-driver-x86@vger.kernel.org,
linux-input@vger.kernel.org, jeff@labundy.com,
anthony.wong@canonical.com, hadess@hadess.net,
Nitin Joshi <njoshi1@lenovo.com>
Subject: Re: [PATCH v3 1/3] Input: add event codes for lap and palmreset proximity switches
Date: Mon, 26 Oct 2020 15:57:53 +0100 [thread overview]
Message-ID: <bc1f2cde-c50e-8704-2fa7-bb7f1b5d6405@redhat.com> (raw)
In-Reply-To: <20201026144512.621479-1-markpearson@lenovo.com>
Hi,
On 10/26/20 3:45 PM, Mark Pearson wrote:
> Add infrastructure needed to support lap and palmrest proximity sensors.
>
> These sensors are used for identifying thermal mode changes and modifying
> WWAN transmitter power.
>
> Reviewed-by: Nitin Joshi <njoshi1@lenovo.com>
> Signed-off-by: Mark Pearson <markpearson@lenovo.com>
The entire series looks good to me and is:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Dmitry: FYI I have take over drivers/platform/x86
maintainership from Andy.
Dmitry, since the first patch adds new evdev switch event-codes,
it is probably best if you merge this entire series through
the input tree. You hereby have my ack (as the new pdx86 maintainer)
for doing this.
Regards,
Hans
> ---
> Changes in v2:
> - Update Input message
> Changes in v3:
> - Added missing patch history notes
>
> include/linux/mod_devicetable.h | 2 +-
> include/uapi/linux/input-event-codes.h | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
> index 5b08a473cdba..897f5a3e7721 100644
> --- a/include/linux/mod_devicetable.h
> +++ b/include/linux/mod_devicetable.h
> @@ -320,7 +320,7 @@ struct pcmcia_device_id {
> #define INPUT_DEVICE_ID_LED_MAX 0x0f
> #define INPUT_DEVICE_ID_SND_MAX 0x07
> #define INPUT_DEVICE_ID_FF_MAX 0x7f
> -#define INPUT_DEVICE_ID_SW_MAX 0x10
> +#define INPUT_DEVICE_ID_SW_MAX 0x12
> #define INPUT_DEVICE_ID_PROP_MAX 0x1f
>
> #define INPUT_DEVICE_ID_MATCH_BUS 1
> diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> index 0c2e27d28e0a..26f71a9a6936 100644
> --- a/include/uapi/linux/input-event-codes.h
> +++ b/include/uapi/linux/input-event-codes.h
> @@ -889,7 +889,9 @@
> #define SW_MUTE_DEVICE 0x0e /* set = device disabled */
> #define SW_PEN_INSERTED 0x0f /* set = pen inserted */
> #define SW_MACHINE_COVER 0x10 /* set = cover closed */
> -#define SW_MAX 0x10
> +#define SW_LAP_PROXIMITY 0x11 /* set = lap proximity sensor active */
> +#define SW_PALMREST_PROXIMITY 0x12 /* set = palmrest proximity sensor active */
> +#define SW_MAX 0x12
> #define SW_CNT (SW_MAX+1)
>
> /*
>
prev parent reply other threads:[~2020-10-26 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 14:45 [PATCH v3 1/3] Input: add event codes for lap and palmreset proximity switches Mark Pearson
2020-10-26 14:45 ` [PATCH v3 2/3] platform/x86: thinkpad_acpi: Add support for palm sensor Mark Pearson
2020-10-26 14:45 ` [PATCH v3 3/3] platform/x86: thinkpad_acpi: Add support for lap sensor Mark Pearson
2020-10-26 14:57 ` 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=bc1f2cde-c50e-8704-2fa7-bb7f1b5d6405@redhat.com \
--to=hdegoede@redhat.com \
--cc=anthony.wong@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=jeff@labundy.com \
--cc=linux-input@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=njoshi1@lenovo.com \
--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).