From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Mylène Josserand" <mylene.josserand@collabora.com>,
"Rob Herring" <robh+dt@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [PATCHv2 0/4] Rotary Encoder Push Button Support
Date: Mon, 7 Sep 2020 22:40:41 +0200 [thread overview]
Message-ID: <20200907204045.95530-1-sebastian.reichel@collabora.com> (raw)
Hi,
The aim of this series is to add support for reporting push
events from rotary encoders with integrated push button
functionality (which are quite common).
I added a few more additional cleanup patches, since I worked
on the driver anyways.
Changes since PATCHv1 [0]:
* Added patch converting the binding to YAML
* Added patch fixing the steps default value
* Added patch introducing dev_err_probe usage
* Updated gpio push button patch from Mylène
- use linux,push-code to be clear this is about the push button
- add linux,push-type to support switches in addition to buttons
- cleanup code a bit
o 100 character line length
o use dev_err_probe()
- use EV_KEY and KEY_ENTER as default and make properties optional
- use push-gpios instead of push-gpio in binding
[0] https://lore.kernel.org/linux-input/20190614133651.28396-1-mylene.josserand@bootlin.com/
-- Sebastian
Mylène Josserand (1):
Input: rotary-encoder - Add gpio as push button
Sebastian Reichel (3):
dt-bindings: input: Convert rotary-encoder bindings to schema
Input: rotary-encoder - Fix steps property reading
Input: rotary-encoder - Use dev_err_probe
.../bindings/input/rotary-encoder.txt | 50 --------
.../bindings/input/rotary-encoder.yaml | 121 ++++++++++++++++++
drivers/input/misc/rotary_encoder.c | 56 +++++++-
3 files changed, 171 insertions(+), 56 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/input/rotary-encoder.txt
create mode 100644 Documentation/devicetree/bindings/input/rotary-encoder.yaml
--
2.28.0
next reply other threads:[~2020-09-07 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 20:40 Sebastian Reichel [this message]
2020-09-07 20:40 ` [PATCHv2 1/4] dt-bindings: input: Convert rotary-encoder bindings to schema Sebastian Reichel
2020-09-15 16:22 ` Rob Herring
2020-09-07 20:40 ` [PATCHv2 2/4] Input: rotary-encoder - Fix steps property reading Sebastian Reichel
2020-09-07 20:40 ` [PATCHv2 3/4] Input: rotary-encoder - Use dev_err_probe Sebastian Reichel
2020-09-09 19:48 ` Rob Herring
2020-09-10 20:58 ` Sebastian Reichel
2020-09-07 20:40 ` [PATCHv2 4/4] Input: rotary-encoder - Add gpio as push button Sebastian Reichel
2020-09-15 16:33 ` Rob Herring
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=20200907204045.95530-1-sebastian.reichel@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mylene.josserand@collabora.com \
--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).