linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sibi Sankar <quic_sibis@quicinc.com>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 05/11] arm64: dts: qcom: x1e80100: Add TCSR node
Date: Fri, 26 Jan 2024 10:18:41 +0200	[thread overview]
Message-ID: <ZbNq4b813348ZiV8@linaro.org> (raw)
In-Reply-To: <b0f4236a-c87e-4d50-b1a0-42ed5b015b86@linaro.org>

On 24-01-23 19:09:37, Konrad Dybcio wrote:
> 
> 
> On 1/23/24 12:01, Abel Vesa wrote:
> > Add the TCSR clock controller and halt register space node.
> > 
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> 
> The former - yes, the latter - ?

Hm, so halt register space is at 0x1f60000. That would be in the mutex
region. But the mutex region is 0x20000 short, even on SM8650 and
SM8550. Need to see why is that, historically.

Either way, the tcsr node region still contains the regs needed by the
SCM driver to enable download mode. So I will rephrase this accordingly.

> 
> Konrad
> >   arch/arm64/boot/dts/qcom/x1e80100.dtsi | 8 ++++++++
> >   1 file changed, 8 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/qcom/x1e80100.dtsi b/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> > index be69e71b7f53..2b6c55a486b2 100644
> > --- a/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> > @@ -2606,6 +2606,14 @@ tcsr_mutex: hwlock@1f40000 {
> >   			#hwlock-cells = <1>;
> >   		};
> > +		tcsr: clock-controller@1fc0000 {
> > +			compatible = "qcom,x1e80100-tcsr", "syscon";
> > +			reg = <0 0x01fc0000 0 0x30000>;
> > +			clocks = <&rpmhcc RPMH_CXO_CLK>;
> > +			#clock-cells = <1>;
> > +			#reset-cells = <1>;
> > +		};
> > +
> >   		gem_noc: interconnect@26400000 {
> >   			compatible = "qcom,x1e80100-gem-noc";
> >   			reg = <0 0x26400000 0 0x311200>;
> > 

  reply	other threads:[~2024-01-26  8:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 11:01 [PATCH v4 00/11] arm64: dts: qcom: Add more support to X1E80100 base dtsi, CRD and QCP boards Abel Vesa
2024-01-23 11:01 ` [PATCH v4 01/11] arm64: dts: qcom: x1e80100: Add IPCC node Abel Vesa
2024-01-23 18:07   ` Konrad Dybcio
2024-01-23 11:01 ` [PATCH v4 02/11] arm64: dts: qcom: x1e80100: Add SMP2P nodes Abel Vesa
2024-01-23 18:30   ` Konrad Dybcio
2024-01-23 11:01 ` [PATCH v4 03/11] arm64: dts: qcom: x1e80100: Add QMP AOSS node Abel Vesa
2024-01-23 18:08   ` Konrad Dybcio
2024-01-23 11:01 ` [PATCH v4 04/11] arm64: dts: qcom: x1e80100: Add ADSP/CDSP remoteproc nodes Abel Vesa
2024-01-23 18:22   ` Konrad Dybcio
2024-01-24 12:37     ` Abel Vesa
2024-01-24 12:40       ` Konrad Dybcio
2024-01-23 11:01 ` [PATCH v4 05/11] arm64: dts: qcom: x1e80100: Add TCSR node Abel Vesa
2024-01-23 18:09   ` Konrad Dybcio
2024-01-26  8:18     ` Abel Vesa [this message]
2024-01-23 11:01 ` [PATCH v4 06/11] arm64: dts: qcom: x1e80100: Add USB nodes Abel Vesa
2024-01-23 18:17   ` Konrad Dybcio
2024-01-26  9:38     ` Abel Vesa
2024-01-23 11:01 ` [PATCH v4 07/11] arm64: dts: qcom: x1e80100: Add PCIe nodes Abel Vesa
2024-01-23 18:20   ` Konrad Dybcio
2024-01-25  8:02     ` Abel Vesa
2024-01-23 11:01 ` [PATCH v4 08/11] arm64: dts: qcom: x1e80100: Add display nodes Abel Vesa
2024-01-23 18:36   ` Konrad Dybcio
2024-01-25  8:01     ` Abel Vesa
2024-01-23 11:01 ` [PATCH v4 09/11] arm64: dts: qcom: x1e80100-crd: Enable more support Abel Vesa
2024-01-23 11:01 ` [PATCH v4 10/11] arm64: dts: qcom: x1e80100-qcp: " Abel Vesa
2024-01-23 11:01 ` [PATCH v4 11/11] arm64: dts: qcom: x1e80100-qcp: Fix supplies for LDOs 3E and 2J Abel Vesa
2024-01-23 18:21   ` Konrad Dybcio

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=ZbNq4b813348ZiV8@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=quic_sibis@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 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).