Devicetree
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 5/6] arm64: dts: qcom: Add device tree for Nord Ride board
Date: Mon, 20 Jul 2026 22:00:39 +0800	[thread overview]
Message-ID: <al4qB8gIyLSjPBGS@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <d5240c7c-6450-489a-97a3-c774deb129b5@oss.qualcomm.com>

On Mon, Jul 20, 2026 at 10:40:09AM +0200, Konrad Dybcio wrote:
> On 7/20/26 6:20 AM, Shawn Guo wrote:
> > On Thu, Jul 16, 2026 at 07:14:56PM +0200, Konrad Dybcio wrote:
> >> On 7/16/26 4:26 PM, Shawn Guo wrote:
> >>> From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> >>>
> >>> Add initial device tree for the Qualcomm SA8797P Ride reference board,
> >>> which is built on Nord GearVM variant.
> 
> [...]
> 
> >>> +&scmi15 {
> >>> +	status = "okay";
> >>> +};
> >>> +
> >>> +&scmi23 {
> >>> +	status = "okay";
> >>> +};
> >>
> >> Why only these ones? Can all of the SCMI servers be enabled?
> > 
> > These are the ones that have actual/enabled client/consumer devices,
> > e.g. scmi3 for ufs, scmi11 for uart, scmi23 for thermal sensors.
> 
> We normally refrain from enabling resources in the DT only because the
> OS (really just Linux) doesn't have the necessary support to cope with
> the ""complete"" system description. In this case, there's a firmware
> layer drives everything and handles on/off requests gracefully
> (hopefully).
> 
> > We can enable all the SCMI servers, but I'm afraid that cause kernel
> > to map shared memory and issue SMC calls to discover protocols (like
> > power domains, DVFS, resets) that have no consumers, which might waste
> > a small amount of memory and boot time.
> 
> Please give it a shot and see if there's any immediate
> problems.

Sorry! I have to take "We can enable all the SCMI servers" back. I just
tested. It seems that NHLOS ABL doesn't like the idea, and it
fails/refuses to boot Linux Kernel when we enable all SCMI instances in
DT.

I can try to figure out the cause by working with Auto/firmware team
internally, but that likely takes some time. Can we address this later
as a separate topic, so that the whole series doesn't get blocked
for v7.3 merge window?

Shawn

  reply	other threads:[~2026-07-20 14:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 14:25 [PATCH v6 0/6] Add initial device trees for Nord platform Shawn Guo
2026-07-16 14:25 ` [PATCH v6 1/6] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-07-16 14:44   ` sashiko-bot
2026-07-16 14:25 ` [PATCH v6 2/6] arm64: dts: qcom: Add device tree for Nord GearVM variant Shawn Guo
2026-07-16 17:01   ` Konrad Dybcio
2026-07-20  3:11     ` Shawn Guo
2026-07-16 14:25 ` [PATCH v6 3/6] arm64: dts: qcom: Add device tree for Nord Embedded variant Shawn Guo
2026-07-16 14:43   ` sashiko-bot
2026-07-16 17:01   ` Konrad Dybcio
2026-07-20  3:50   ` Shawn Guo
2026-07-16 14:25 ` [PATCH v6 4/6] dt-bindings: arm: qcom: Document Nord reference boards Shawn Guo
2026-07-16 14:49   ` Bartosz Golaszewski
2026-07-16 14:26 ` [PATCH v6 5/6] arm64: dts: qcom: Add device tree for Nord Ride board Shawn Guo
2026-07-16 14:56   ` sashiko-bot
2026-07-16 17:14   ` Konrad Dybcio
2026-07-20  4:20     ` Shawn Guo
2026-07-20  8:40       ` Konrad Dybcio
2026-07-20 14:00         ` Shawn Guo [this message]
2026-07-20 14:02           ` Konrad Dybcio
2026-07-16 14:26 ` [PATCH v6 6/6] arm64: dts: qcom: Add device tree for Nord RRD board Shawn Guo
2026-07-16 17:17   ` Konrad Dybcio
2026-07-17 13:58     ` Bartosz Golaszewski
2026-07-20 13:02     ` Shawn Guo

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=al4qB8gIyLSjPBGS@QCOM-aGQu4IUr3Y \
    --to=shengchao.guo@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=deepti.jaggi@oss.qualcomm.com \
    --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