From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Kaushal Kumar <quic_kaushalk@quicinc.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] ARM: dts: qcom: sdx65-mtp: Enable QPIC BAM support
Date: Mon, 2 May 2022 12:37:02 +0530 [thread overview]
Message-ID: <20220502070702.GD5053@thinkpad> (raw)
In-Reply-To: <1651332610-6334-4-git-send-email-quic_kaushalk@quicinc.com>
On Sat, Apr 30, 2022 at 08:30:09AM -0700, Kaushal Kumar wrote:
> Enable QPIC BAM devicetree node for Qualcomm SDX65-MTP board.
>
> Signed-off-by: Kaushal Kumar <quic_kaushalk@quicinc.com>
> ---
> arch/arm/boot/dts/qcom-sdx65-mtp.dts | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-sdx65-mtp.dts b/arch/arm/boot/dts/qcom-sdx65-mtp.dts
> index 6920524..5c5fcb0 100644
> --- a/arch/arm/boot/dts/qcom-sdx65-mtp.dts
> +++ b/arch/arm/boot/dts/qcom-sdx65-mtp.dts
> @@ -68,6 +68,10 @@
> status = "ok";
> };
>
> +&qpic_bam {
Nodes need to be sorted in alphabetical order.
Thanks,
Mani
> + status = "ok";
> +};
> +
> &apps_rsc {
> pmx65-rpmh-regulators {
> compatible = "qcom,pmx65-rpmh-regulators";
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-05-02 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 15:30 [PATCH 0/4] Add QPIC BAM and QPIC NAND devicetree support for SDX65 Kaushal Kumar
2022-04-30 15:30 ` [PATCH 1/4] ARM: dts: qcom: sdx65: Add QPIC BAM support Kaushal Kumar
2022-05-02 7:04 ` Manivannan Sadhasivam
2022-04-30 15:30 ` [PATCH 2/4] ARM: dts: qcom: sdx65: Add QPIC NAND support Kaushal Kumar
2022-05-02 7:05 ` Manivannan Sadhasivam
2022-04-30 15:30 ` [PATCH 3/4] ARM: dts: qcom: sdx65-mtp: Enable QPIC BAM support Kaushal Kumar
2022-05-02 7:07 ` Manivannan Sadhasivam [this message]
2022-04-30 15:30 ` [PATCH 4/4] ARM: dts: qcom: sdx65-mtp: Enable QPIC NAND support Kaushal Kumar
2022-05-02 7:07 ` Manivannan Sadhasivam
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=20220502070702.GD5053@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kaushalk@quicinc.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.