From: Jeff LaBundy <jeff@labundy.com>
To: dmitry.torokhov@gmail.com, robh+dt@kernel.org
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
Jeff LaBundy <jeff@labundy.com>
Subject: [PATCH v2 0/2] Add support for Azoteq IQS7222A/B/C
Date: Tue, 25 Jan 2022 21:07:21 -0600 [thread overview]
Message-ID: <20220126030723.223809-1-jeff@labundy.com> (raw)
This series introduces support for the Azoteq IQS7222A, IQS7222B and
IQS7222C capacitive touch controllers. This new family of devices is
similar to the IQS269A, a key difference being the delineation between
conversion cycles and sensing channels.
A cycle represents the charge transfer mechanism shared by up to two
channels. Channels may represent keys or switches and have two levels
of detection (proximity and touch).
Each device has its own unique features including channel count, slider
or wheel support, and Hall-effect sensing. The driver is demonstrated
with each device in the following videos:
IQS7222A: https://youtu.be/SyHhe9pSr8c
IQS7222B: https://youtu.be/R9Yd8yFPmN8
IQS7222C: https://youtu.be/-ahg52Co5zo
Like the IQS269A and its close cousin IQS626A, the IQS7222A/B/C are
highly configurable and follow the same general structure in terms of
how their bindings are represented.
Jeff LaBundy (2):
dt-bindings: input: Add bindings for Azoteq IQS7222A/B/C
Input: add support for Azoteq IQS7222A/B/C
.../bindings/input/azoteq,iqs7222.yaml | 960 +++++++
drivers/input/misc/Kconfig | 10 +
drivers/input/misc/Makefile | 1 +
drivers/input/misc/iqs7222.c | 2444 +++++++++++++++++
4 files changed, 3415 insertions(+)
create mode 100644 Documentation/devicetree/bindings/input/azoteq,iqs7222.yaml
create mode 100644 drivers/input/misc/iqs7222.c
--
2.25.1
next reply other threads:[~2022-01-26 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 3:07 Jeff LaBundy [this message]
2022-01-26 3:07 ` [PATCH v2 1/2] dt-bindings: input: Add bindings for Azoteq IQS7222A/B/C Jeff LaBundy
2022-02-07 23:33 ` Rob Herring
2022-01-26 3:07 ` [PATCH v2 2/2] Input: add support " Jeff LaBundy
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=20220126030723.223809-1-jeff@labundy.com \
--to=jeff@labundy.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=robh+dt@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).