From: Mark Pearson <markpearson@lenovo.com>
To: <markpearson@lenovo.com>
Cc: <njoshi1@lenovo.com>, <hdegoede@redhat.com>,
<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>
Subject: [PATCH 0/3] Lenovo lap and palm sensor support
Date: Thu, 15 Oct 2020 09:57:14 -0400 [thread overview]
Message-ID: <20201015135717.384610-1-markpearson@lenovo.com> (raw)
In-Reply-To: <markpearson@lenovo.com>
This patch series is to add support for the Lenovo lap and palm sensors.
The original lap sensor implementation used a sysfs API but after
consultation with the kernel maintainers we agreed on using the input
subsystem instead.
The first patch just adds the new defines needed.
The second patch adds the implementation needed for the palm sensor.
The third patch adds the implementation needed for the lap sensor.
This means currently thinkpad_acpi.c has both the sysfs and input dev
implementations. I will add a follow-on patch to remove the sysfs
interface once I've confirmed this is OK with the few people who are
using this in user space and given them some time to migrate to the
input dev implementation.
Mark Pearson (3):
Adding event codes for Lenovo lap and palm sensors
Add support for Lenovo palm sensor.
Add support for Lenovo lap sensor
drivers/platform/x86/thinkpad_acpi.c | 144 ++++++++++++++++++++++++-
include/linux/mod_devicetable.h | 2 +-
include/uapi/linux/input-event-codes.h | 4 +-
3 files changed, 145 insertions(+), 5 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-15 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:57 Mark Pearson [this message]
2020-10-15 13:57 ` [PATCH 1/3] Adding event codes for Lenovo lap and palm sensors Mark Pearson
2020-10-15 13:57 ` [PATCH 2/3] Add support for Lenovo palm sensor Mark Pearson
2020-10-15 13:57 ` [PATCH 3/3] Add support for Lenovo lap sensor Mark Pearson
2020-10-19 18:49 ` [PATCH 0/3] Lenovo lap and palm sensor support Hans de Goede
2020-10-20 0:15 ` [External] " Mark Pearson
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=20201015135717.384610-1-markpearson@lenovo.com \
--to=markpearson@lenovo.com \
--cc=anthony.wong@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jeff@labundy.com \
--cc=linux-input@vger.kernel.org \
--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).