devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Andy Gross <agross@kernel.org>,
	Damien Riegel <damien.riegel@savoirfairelinux.com>,
	linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: pm8916: Add vibration motor node
Date: Wed, 11 Dec 2019 22:42:59 -0800	[thread overview]
Message-ID: <20191212064259.GJ3143381@builder> (raw)
In-Reply-To: <20191211192906.56638-1-stephan@gerhold.net>

On Wed 11 Dec 11:29 PST 2019, Stephan Gerhold wrote:

> PM8916 has one vibration motor driver that is already supported
> by the pm8xxx-vibrator driver.
> 
> Add a node describing it to pm8916.dtsi.
> Keep it disabled by default since not all devices make use of it.
> 
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>

Applied, please also send a defconfig patch that enables the associated
driver (=m)

Thanks,
Bjorn

> ---
>  arch/arm64/boot/dts/qcom/pm8916.dtsi | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/pm8916.dtsi b/arch/arm64/boot/dts/qcom/pm8916.dtsi
> index 9dd2df1cbf47..0bcdf0471107 100644
> --- a/arch/arm64/boot/dts/qcom/pm8916.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pm8916.dtsi
> @@ -111,6 +111,12 @@ pm8916_1: pm8916@1 {
>  		#address-cells = <1>;
>  		#size-cells = <0>;
>  
> +		pm8916_vib: vibrator@c000 {
> +			compatible = "qcom,pm8916-vib";
> +			reg = <0xc000>;
> +			status = "disabled";
> +		};
> +
>  		wcd_codec: codec@f000 {
>  			compatible = "qcom,pm8916-wcd-analog-codec";
>  			reg = <0xf000 0x200>;
> -- 
> 2.24.0
> 

      reply	other threads:[~2019-12-12  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 19:29 [PATCH] arm64: dts: qcom: pm8916: Add vibration motor node Stephan Gerhold
2019-12-12  6:42 ` Bjorn Andersson [this message]

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=20191212064259.GJ3143381@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=damien.riegel@savoirfairelinux.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stephan@gerhold.net \
    /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).