Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
	Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 2/5] arm64: dts: qcom: Add device tree for Nord SoC series
Date: Thu, 9 Jul 2026 15:09:38 +0200	[thread overview]
Message-ID: <a56f13af-d506-479f-919b-8a4d2e09bd90@oss.qualcomm.com> (raw)
In-Reply-To: <akhcTp1MyjGnhXav@QCOM-aGQu4IUr3Y>

On 7/4/26 3:05 AM, Shawn Guo wrote:
> On Tue, Jun 16, 2026 at 12:57:42PM +0200, Konrad Dybcio wrote:
>> On 5/26/26 7:12 AM, Shawn Guo wrote:
>>> Add base device tree include (nord.dtsi) for the Nord SoC series
>>> describing the core hardware components:
>>>
>>>  - 18 Oryon (qcom,oryon-1-5) cores in three clusters, with PSCI-based
>>>    power management and CPU/cluster idle states
>>>  - ARM GICv3 interrupt controller with ITS
>>>  - TLMM GPIO/pinctrl controller
>>>  - 8 TSENS thermal sensors with thermal zones
>>>  - 3 APPS SMMU-500 instances
>>>  - 3 QUPv3 GENI SE QUP blocks
>>>  - PDP SCMI channel and mailbox
>>>  - Watchdog, TRNG and TCSR
>>>  - Reserved memory, CMD-DB and firmware SCM
>>>  - PSCI and architected timers
>>
>> [...]
>>
>>> +		dump_mem: mem-dump-region {
>>> +			alloc-ranges = <0x0 0x00000000 0x0 0xffffffff>;
>>
>> off-by-1?
> 
> Yes. We have the same thing in sdm845.dtsi and sm8750.dtsi. Unless you
> think that missing the last byte is functionally problematic, I would
> rather be consistent with the established pattern in the tree.

It's difficult to tell whether it's cargo cult or whether the hw
actually has an issue decoding 0xffff_ffff. I would skew towards
the former, but I have nothing to prove that

Konrad

  reply	other threads:[~2026-07-09 13:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  5:12 [PATCH v3 RESEND 0/5] Add initial device trees for Nord SA8797P Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 1/5] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 2/5] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-05-26  5:44   ` sashiko-bot
2026-06-16 10:57   ` Konrad Dybcio
2026-07-04  1:05     ` Shawn Guo
2026-07-09 13:09       ` Konrad Dybcio [this message]
2026-06-16 10:58   ` Konrad Dybcio
2026-07-04  1:06     ` Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 3/5] arm64: dts: qcom: Add device tree for Nord SA8797P SoC Shawn Guo
2026-05-26  6:01   ` sashiko-bot
2026-06-16 11:00   ` Konrad Dybcio
2026-07-04  1:32     ` Shawn Guo
2026-07-06 13:57   ` Pavan Kondeti
2026-07-07  2:15     ` Deepti Jaggi
2026-07-07  3:38       ` Pavan Kondeti
2026-07-09  3:19         ` Deepti Jaggi
2026-07-09  7:43           ` Dmitry Baryshkov
2026-07-07  8:48   ` Krzysztof Kozlowski
2026-05-26  5:12 ` [PATCH v3 RESEND 4/5] dt-bindings: arm: qcom: Document SA8797P Ride board Shawn Guo
2026-05-26  6:11   ` sashiko-bot
2026-05-26  5:13 ` [PATCH v3 RESEND 5/5] arm64: dts: qcom: Add device tree for " Shawn Guo
2026-05-26  6:29   ` sashiko-bot
2026-06-16 11:02   ` Konrad Dybcio
2026-07-04  3:03     ` 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=a56f13af-d506-479f-919b-8a4d2e09bd90@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=deepti.jaggi@oss.qualcomm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=harshal.dev@oss.qualcomm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=robh@kernel.org \
    --cc=shengchao.guo@oss.qualcomm.com \
    /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