From: Brian Masney <masneyb@onstation.org>
To: sboyd@kernel.org, dmitry.torokhov@gmail.com, robh+dt@kernel.org
Cc: mark.rutland@arm.com, agross@kernel.org,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: [PATCH 0/7] qcom: add clk-vibrator driver
Date: Wed, 4 Dec 2019 19:24:56 -0500 [thread overview]
Message-ID: <20191205002503.13088-1-masneyb@onstation.org> (raw)
This patch series adds support for the vibrator that's found on the
Nexus 5 phone. I previously added a msm-vibrator driver to the input
subsystem, however that's not the correct approach since the direct
register writes should occur from within the clk subsystem based on the
conversation at
https://lore.kernel.org/lkml/20190516085018.2207-1-masneyb@onstation.org/
So this patch series:
- Adds support for setting the clock duty cycle to clk-rcg2.c
- Removes the msm-vibrator driver and adds a generic clk-vibrator
driver in its place. No one is using this driver at the moment so we
shouldn't get any complaints.
I also included the defconfig and dts changes. Once this whole series is
deemed to be ready, it can be merged in pieces through the different
subsystems. I included everything here as one patch series so everyone
can see the complete picture of what I'm doing.
Sorry it took me awhile to get back to correcting this; was working on
other tasks on this phone.
Brian Masney (7):
clk: qcom: add support for setting the duty cycle
dt-bindings: Input: drop msm-vibrator in favor of clk-vibrator
Input: drop msm-vibrator in favor of clk-vibrator driver
dt-bindings: Input: introduce new clock vibrator bindings
Input: introduce new clock vibrator driver
ARM: qcom_defconfig: drop msm-vibrator in favor of clk-vibrator driver
ARM: dts: qcom: msm8974-hammerhead: add support for vibrator
.../bindings/input/clk-vibrator.yaml | 60 ++++++++
.../bindings/input/msm-vibrator.txt | 36 -----
.../qcom-msm8974-lge-nexus5-hammerhead.dts | 30 ++++
arch/arm/configs/qcom_defconfig | 2 +-
drivers/clk/qcom/clk-rcg.h | 4 +
drivers/clk/qcom/clk-rcg2.c | 61 +++++++-
drivers/input/misc/Kconfig | 20 +--
drivers/input/misc/Makefile | 2 +-
.../misc/{msm-vibrator.c => clk-vibrator.c} | 138 +++++++-----------
9 files changed, 216 insertions(+), 137 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/clk-vibrator.yaml
delete mode 100644 Documentation/devicetree/bindings/input/msm-vibrator.txt
rename drivers/input/misc/{msm-vibrator.c => clk-vibrator.c} (51%)
--
2.21.0
next reply other threads:[~2019-12-05 0:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 0:24 Brian Masney [this message]
2019-12-05 0:24 ` [PATCH 1/7] clk: qcom: add support for setting the duty cycle Brian Masney
2019-12-10 4:47 ` Taniya Das
2020-02-12 23:23 ` Stephen Boyd
[not found] ` <0101016eee224b50-8a5545e2-837f-41c2-9574-b385e111a6b3-000000@us-west-2.amazonses.com>
2019-12-10 11:51 ` Brian Masney
2019-12-13 13:56 ` Linus Walleij
2019-12-05 0:24 ` [PATCH 2/7] dt-bindings: Input: drop msm-vibrator in favor of clk-vibrator Brian Masney
2019-12-17 14:11 ` Rob Herring
2019-12-05 0:24 ` [PATCH 3/7] Input: drop msm-vibrator in favor of clk-vibrator driver Brian Masney
2020-02-11 12:18 ` Brian Masney
2019-12-05 0:25 ` [PATCH 4/7] dt-bindings: Input: introduce new clock vibrator bindings Brian Masney
2019-12-05 13:56 ` Rob Herring
2019-12-09 0:54 ` Brian Masney
2019-12-09 16:16 ` Rob Herring
2019-12-09 16:55 ` Brian Masney
2020-01-05 8:35 ` Stephen Boyd
2020-01-07 12:03 ` Brian Masney
2020-01-07 17:52 ` Stephen Boyd
2020-01-07 23:18 ` Brian Masney
2019-12-05 0:25 ` [PATCH 5/7] Input: introduce new clock vibrator driver Brian Masney
2019-12-05 0:25 ` [PATCH 6/7] ARM: qcom_defconfig: drop msm-vibrator in favor of clk-vibrator driver Brian Masney
2019-12-05 0:25 ` [PATCH 7/7] ARM: dts: qcom: msm8974-hammerhead: add support for vibrator Brian Masney
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=20191205002503.13088-1-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).