From: Chunyan Zhang <zhang.lyra@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang7@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
Nemo Han <nemo.han@unisoc.com>
Subject: [PATCH v2 0/3] Add support for sc2730 and sc2721
Date: Tue, 17 Nov 2020 11:49:46 +0800 [thread overview]
Message-ID: <20201117034949.47877-1-zhang.lyra@gmail.com> (raw)
This patchset add new compatible strings and match data to support sc2730 and sc2721,
also convert the bindings to yaml schema.
Changes since v1:
* fixed the error when running dt_binding_check;
Chunyan Zhang (2):
dt-bindings: input: Convert sc27xx-vibra.txt to json-schema
dt-bindings: input: Add compatible string for SC2721 and SC2730
Nemo Han (1):
input: sc27xx: Add support for sc2730 and sc2721
.../bindings/input/sprd,sc27xx-vibra.txt | 23 -------
.../bindings/input/sprd,sc27xx-vibrator.yaml | 48 ++++++++++++++
drivers/input/misc/sc27xx-vibra.c | 64 ++++++++++++++++---
3 files changed, 102 insertions(+), 33 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/input/sprd,sc27xx-vibra.txt
create mode 100644 Documentation/devicetree/bindings/input/sprd,sc27xx-vibrator.yaml
--
2.25.1
next reply other threads:[~2020-11-17 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 3:49 Chunyan Zhang [this message]
2020-11-17 3:49 ` [PATCH v2 1/3] input: sc27xx: Add support for sc2730 and sc2721 Chunyan Zhang
2020-12-12 3:04 ` Dmitry Torokhov
2020-11-17 3:49 ` [PATCH v2 2/3] dt-bindings: input: Convert sc27xx-vibra.txt to json-schema Chunyan Zhang
2020-12-07 19:35 ` Rob Herring
2020-12-12 3:00 ` Dmitry Torokhov
2020-11-17 3:49 ` [PATCH v2 3/3] dt-bindings: input: Add compatible string for SC2721 and SC2730 Chunyan Zhang
2020-12-07 19:35 ` Rob Herring
2020-12-12 3:01 ` 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=20201117034949.47877-1-zhang.lyra@gmail.com \
--to=zhang.lyra@gmail.com \
--cc=baolin.wang7@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nemo.han@unisoc.com \
--cc=orsonzhai@gmail.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 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.