From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8750: Enable download mode register write
Date: Tue, 13 Jan 2026 18:34:28 +0530 [thread overview]
Message-ID: <20260113130428.n2kuo2d2tkoosws2@hu-mojha-hyd.qualcomm.com> (raw)
In-Reply-To: <cca646c3-5e74-47cf-9dfa-49a888db0414@oss.qualcomm.com>
On Tue, Jan 13, 2026 at 10:20:58AM +0100, Konrad Dybcio wrote:
> On 1/13/26 10:16 AM, Konrad Dybcio wrote:
> > On 1/12/26 4:17 PM, Mukesh Ojha wrote:
> >> Enable download mode setting for sm8750 which can help collect
> >> ramdump for this SoC.
> >>
> >> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> >> ---
> >
> > Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Actually no, we have a mess to undo..
>
> There's already this node:
>
> tcsrcc: clock-controller@f204008 {
> compatible = "qcom,sm8750-tcsr", "syscon";
> reg = <0x0 0x0f204008 0x0 0x3004>;
>
> clocks = <&rpmhcc RPMH_CXO_CLK>;
>
> #clock-cells = <1>;
> #reset-cells = <1>;
> };
>
> That's located at the rear end of TLMM (someone had a funny idea to
> move registers around when designing this specific SoC)
>
> Problem is, those registers aren't actually "TCSRCC", not even "TCSR"
> Physically, they belong to the TLMM register window (which starts at
> the base it promises under the TLMM node today and is 0xf0_0000-long.
>
> What we should have done for a fairer representation is make TLMM a
> clock provider on this specific platform
>
> qcom,sm8750-tcsr binds the tcsrcc driver, so we can't describe the
> actual TCSR (as in this patch).. we'll have to break something..
>
+ syscon: syscon@1fc0000 {
+ compatible = "syscon";
+ reg = <0 0x01fc0000 0 0x30000>;
+ };
What about above ?
> Konrad
--
-Mukesh Ojha
next prev parent reply other threads:[~2026-01-13 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 15:17 Mukesh Ojha
2026-01-12 16:42 ` Rob Herring
2026-01-13 9:16 ` Konrad Dybcio
2026-01-13 9:20 ` Konrad Dybcio
2026-01-13 13:04 ` Mukesh Ojha [this message]
2026-01-13 14:06 ` Rob Herring
2026-01-13 17:54 ` Dmitry Baryshkov
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=20260113130428.n2kuo2d2tkoosws2@hu-mojha-hyd.qualcomm.com \
--to=mukesh.ojha@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®