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 0/7] Miscellaneous fixes for Azoteq IQS7222A/B/C
Date: Wed, 22 Jun 2022 22:53:02 -0500 [thread overview]
Message-ID: <20220623035309.39528-1-jeff@labundy.com> (raw)
This series comprises a handful of minor fixes that result from
continued testing and updated guidance from the vendor.
Jeff LaBundy (7):
Input: iqs7222 - fortify slider event reporting
Input: iqs7222 - protect volatile registers
Input: iqs7222 - acknowledge reset before writing registers
Input: iqs7222 - handle reset during ATI
Input: iqs7222 - remove support for RF filter
dt-bindings: input: iqs7222: Remove support for RF filter
dt-bindings: input: iqs7222: Correct bottom speed step size
.../bindings/input/azoteq,iqs7222.yaml | 7 +-
drivers/input/misc/iqs7222.c | 132 ++++++++++++------
2 files changed, 90 insertions(+), 49 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-23 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 3:53 Jeff LaBundy [this message]
2022-06-23 3:53 ` [PATCH 1/7] Input: iqs7222 - fortify slider event reporting Jeff LaBundy
2022-06-23 3:53 ` [PATCH 2/7] Input: iqs7222 - protect volatile registers Jeff LaBundy
2022-06-23 3:53 ` [PATCH 3/7] Input: iqs7222 - acknowledge reset before writing registers Jeff LaBundy
2022-06-23 3:53 ` [PATCH 4/7] Input: iqs7222 - handle reset during ATI Jeff LaBundy
2022-06-23 3:53 ` [PATCH 5/7] Input: iqs7222 - remove support for RF filter Jeff LaBundy
2022-06-24 1:05 ` Dmitry Torokhov
2022-06-24 1:13 ` Jeff LaBundy
2022-06-23 3:53 ` [PATCH 6/7] dt-bindings: input: iqs7222: Remove " Jeff LaBundy
2022-06-23 3:53 ` [PATCH 7/7] dt-bindings: input: iqs7222: Correct bottom speed step size 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=20220623035309.39528-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.