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
Subject: Re: [PATCH v2 0/2] Add support for Azoteq IQS7210A/7211A/E
Date: Wed, 12 Jul 2023 16:26:58 -0500 [thread overview]
Message-ID: <ZK8aoiVOoZgWSCDc@nixie71> (raw)
In-Reply-To: <ZHVD/9OgRTAwBhqx@nixie71>
Hi Dmitry,
On Mon, May 29, 2023 at 07:31:59PM -0500, Jeff LaBundy wrote:
> This series introduces support for the Azoteq IQS7210A, IQS7211A and
> IQS7211E trackpad/touchscreen controllers. Optimized for wearable
> applications, these devices track up to two contacts and are capable
> of reporting an array of gestures.
>
> The IQS7210A includes an additional channel to support an inductive
> or capacitive button, while the IQS7211E adds an advanced assortment
> of gestures. All three devices are demonstrated in [1].
>
> These devices can be configured during production using OTP memory,
> or over I2C using the device tree. For the latter case, the binding
> covers all major parameters called out by the vendor in [2].
>
> [1] https://youtu.be/RjB8rNkzQJQ
> [2] https://www.azoteq.com/images/stories/pdf/azd123_iqs721xy_trackpad_userguide.pdf
>
> Jeff LaBundy (2):
> dt-bindings: input: Add bindings for Azoteq IQS7210A/7211A/E
> Input: add support for Azoteq IQS7210A/7211A/E
>
> .../input/touchscreen/azoteq,iqs7211.yaml | 769 +++++
> drivers/input/touchscreen/Kconfig | 10 +
> drivers/input/touchscreen/Makefile | 1 +
> drivers/input/touchscreen/iqs7211.c | 2569 +++++++++++++++++
> 4 files changed, 3349 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/touchscreen/azoteq,iqs7211.yaml
> create mode 100644 drivers/input/touchscreen/iqs7211.c
>
> --
> 2.34.1
>
Just bumping this one; any interest in taking it?
Kind regards,
Jeff LaBundy
next prev parent reply other threads:[~2023-07-12 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 0:31 [PATCH v2 0/2] Add support for Azoteq IQS7210A/7211A/E Jeff LaBundy
2023-05-30 0:33 ` [PATCH v2 1/2] dt-bindings: input: Add bindings " Jeff LaBundy
2023-06-09 14:25 ` Rob Herring
2023-06-12 1:06 ` Jeff LaBundy
2023-06-12 15:29 ` Rob Herring
2023-06-13 0:58 ` Jeff LaBundy
2023-06-14 18:51 ` Rob Herring
2023-06-14 18:52 ` Rob Herring
2023-05-30 0:34 ` [PATCH v2 2/2] Input: add support " Jeff LaBundy
2023-07-12 21:26 ` Jeff LaBundy [this message]
2023-07-12 21:34 ` [PATCH v2 0/2] Add " Dmitry Torokhov
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=ZK8aoiVOoZgWSCDc@nixie71 \
--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).