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.com
Subject: [PATCH v2 0/7] Additional fixes for Azoteq IQS7222A/B/C
Date: Thu, 15 Sep 2022 23:29:11 -0500 [thread overview]
Message-ID: <YyP7l/ts6SFI9iM2@nixie71> (raw)
This series comprises a second round of fixes that result from
continued testing and updated guidance from the vendor.
Jeff LaBundy (7):
Input: iqs7222 - drop unused device node references
dt-bindings: input: iqs7222: Reduce 'linux,code' to optional
Input: iqs7222 - report malformed properties
dt-bindings: input: iqs7222: Correct minimum slider size
Input: iqs7222 - protect against undefined slider size
dt-bindings: input: iqs7222: Add support for IQS7222A v1.13+
Input: iqs7222 - add support for IQS7222A v1.13+
.../bindings/input/azoteq,iqs7222.yaml | 25 +-
drivers/input/misc/iqs7222.c | 489 +++++++++++-------
2 files changed, 313 insertions(+), 201 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-16 4:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:29 Jeff LaBundy [this message]
2022-09-16 4:30 ` [PATCH v2 1/7] Input: iqs7222 - drop unused device node references Jeff LaBundy
2022-10-07 13:12 ` Mattijs Korpershoek
2022-09-16 4:31 ` [PATCH v2 2/7] dt-bindings: input: iqs7222: Reduce 'linux,code' to optional Jeff LaBundy
2022-09-29 18:59 ` Rob Herring
2022-09-16 4:31 ` [PATCH v2 3/7] Input: iqs7222 - report malformed properties Jeff LaBundy
2022-10-07 13:12 ` Mattijs Korpershoek
2022-10-08 1:20 ` Jeff LaBundy
2022-09-16 4:31 ` [PATCH v2 4/7] dt-bindings: input: iqs7222: Correct minimum slider size Jeff LaBundy
2022-09-16 4:31 ` [PATCH v2 5/7] Input: iqs7222 - protect against undefined " Jeff LaBundy
2022-09-16 4:32 ` [PATCH v2 6/7] dt-bindings: input: iqs7222: Add support for IQS7222A v1.13+ Jeff LaBundy
2022-09-16 4:32 ` [PATCH v2 7/7] Input: iqs7222 - add " Jeff LaBundy
2022-10-07 13:16 ` Mattijs Korpershoek
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=YyP7l/ts6SFI9iM2@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).