From: Robert Marko <robimarko@gmail.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: agross@kernel.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: ipq8074: add SMEM support
Date: Mon, 20 Sep 2021 11:25:55 +0200 [thread overview]
Message-ID: <CAOX2RU5b46H7nqm6G4mHLSqEhGiWktwWjUKF5w10Ut+AdKea-A@mail.gmail.com> (raw)
In-Reply-To: <YUf3aKn78+41Cb/G@builder.lan>
On Mon, 20 Sept 2021 at 04:52, Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
>
> On Thu 02 Sep 16:47 CDT 2021, Robert Marko wrote:
>
> > IPQ8074 uses SMEM like other modern QCA SoC-s, so since its already
> > supported by the kernel add the required DT nodes.
> >
> > Signed-off-by: Robert Marko <robimarko@gmail.com>
>
> Thanks for your patch Robert.
>
> > ---
> > arch/arm64/boot/dts/qcom/ipq8074.dtsi | 28 +++++++++++++++++++++++++++
> > 1 file changed, 28 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> > index a620ac0d0b19..83e9243046aa 100644
> > --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> > @@ -82,6 +82,29 @@ scm {
> > };
> > };
> >
> > + reserved-memory {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > + ranges;
> > +
> > + smem_region: memory@4ab00000 {
> > + no-map;
> > + reg = <0x0 0x4ab00000 0x0 0x00100000>;
> > + };
> > + };
> > +
> > + tcsr_mutex: hwlock {
> > + compatible = "qcom,tcsr-mutex";
> > + syscon = <&tcsr_mutex_regs 0 0x80>;
>
> Since it's not okay to have a lone "syscon" and I didn't think it was
> worth coming up with a binding for the TCSR mutex "syscon" I rewrote the
> binding a while back. As such qcom,tcsr-mutex should now live in /soc
> directly.
>
> So can you please respin accordingly?
Sure, can you just confirm that the:
reg = <0x01905000 0x8000>;
Is the whole TCSR range as I don't have docs?
Regards,
Robert
>
> Thanks,
> Bjorn
>
> > + #hwlock-cells = <1>;
> > + };
> > +
> > + smem {
> > + compatible = "qcom,smem";
> > + memory-region = <&smem_region>;
> > + hwlocks = <&tcsr_mutex 0>;
> > + };
> > +
> > soc: soc {
> > #address-cells = <0x1>;
> > #size-cells = <0x1>;
> > @@ -293,6 +316,11 @@ gcc: gcc@1800000 {
> > #reset-cells = <0x1>;
> > };
> >
> > + tcsr_mutex_regs: syscon@1905000 {
> > + compatible = "syscon";
> > + reg = <0x01905000 0x8000>;
> > + };
> > +
> > sdhc_1: sdhci@7824900 {
> > compatible = "qcom,sdhci-msm-v4";
> > reg = <0x7824900 0x500>, <0x7824000 0x800>;
> > --
> > 2.31.1
> >
next prev parent reply other threads:[~2021-09-20 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 21:47 [PATCH] arm64: dts: qcom: ipq8074: add SMEM support Robert Marko
2021-09-20 2:52 ` Bjorn Andersson
2021-09-20 9:25 ` Robert Marko [this message]
2021-09-21 6:24 ` Kathiravan T
2021-09-22 20:23 ` Robert Marko
2021-09-22 22:18 ` Bjorn Andersson
2021-10-06 18:05 ` Robert Marko
2021-10-06 18:13 ` Robert Marko
2021-10-06 18:24 ` Manivannan Sadhasivam
2021-10-06 18:26 ` Robert Marko
2021-10-06 18:44 ` Manivannan Sadhasivam
2021-10-06 19:09 ` Robert Marko
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=CAOX2RU5b46H7nqm6G4mHLSqEhGiWktwWjUKF5w10Ut+AdKea-A@mail.gmail.com \
--to=robimarko@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).