From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Brian Masney <masneyb@onstation.org>
Cc: andy.gross@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, jonathan@marek.ca
Subject: Re: [PATCH v4 3/3] ARM: dts: qcom: msm8974-hammerhead: add device tree bindings for vibrator
Date: Wed, 6 Feb 2019 10:18:22 -0800 [thread overview]
Message-ID: <20190206181822.GB174258@dtor-ws> (raw)
In-Reply-To: <20190206013329.18195-4-masneyb@onstation.org>
On Tue, Feb 05, 2019 at 08:33:29PM -0500, Brian Masney wrote:
> This patch adds device device tree bindings for the vibrator found on
> the LG Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney <masneyb@onstation.org>
This should go through Qualcomm tree with the other bindings?
> ---
> Changes since v3:
> - None
>
> .../qcom-msm8974-lge-nexus5-hammerhead.dts | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts b/arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts
> index b3b04736a159..1fd9f429f34a 100644
> --- a/arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts
> +++ b/arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts
> @@ -5,6 +5,7 @@
> #include <dt-bindings/gpio/gpio.h>
> #include <dt-bindings/input/input.h>
> #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
> +#include <dt-bindings/clock/qcom,mmcc-msm8974.h>
>
> / {
> model = "LGE MSM 8974 HAMMERHEAD";
> @@ -306,6 +307,36 @@
> input-enable;
> };
> };
> +
> + vibrator_pin: vibrator {
> + pwm {
> + pins = "gpio27";
> + function = "gp1_clk";
> +
> + drive-strength = <6>;
> + bias-disable;
> + };
> +
> + enable {
> + pins = "gpio60";
> + function = "gpio";
> + };
> + };
> + };
> +
> + vibrator@fd8c3450 {
> + compatible = "qcom,msm8974-vibrator";
> + reg = <0xfd8c3450 0x400>;
> +
> + vcc-supply = <&pm8941_l19>;
> +
> + clocks = <&mmcc CAMSS_GP1_CLK>;
> + clock-names = "pwm";
> +
> + enable-gpios = <&msmgpio 60 GPIO_ACTIVE_HIGH>;
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&vibrator_pin>;
> };
>
> sdhci@f9824900 {
> --
> 2.17.2
>
--
Dmitry
next prev parent reply other threads:[~2019-02-06 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 1:33 [PATCH v4 0/3] ARM: qcom: add vibrator support for various MSM SOCs Brian Masney
2019-02-06 1:33 ` [PATCH v4 1/3] dt-bindings: Input: new bindings for MSM vibrator Brian Masney
2019-02-06 1:33 ` [PATCH v4 2/3] Input: add new vibrator driver for various MSM SOCs Brian Masney
2019-02-06 18:16 ` Dmitry Torokhov
2019-02-06 1:33 ` [PATCH v4 3/3] ARM: dts: qcom: msm8974-hammerhead: add device tree bindings for vibrator Brian Masney
2019-02-06 18:18 ` Dmitry Torokhov [this message]
2019-02-06 18:51 ` 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=20190206181822.GB174258@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masneyb@onstation.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).