From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: qcom: Add device tree for Nord SoC series
Date: Tue, 28 Apr 2026 21:09:25 +0800 [thread overview]
Message-ID: <afCxhUaxLEcbosvV@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <e1a84d37-04a1-4c36-b6c3-f8830df9a744@kernel.org>
On Tue, Apr 28, 2026 at 09:28:47AM +0200, Krzysztof Kozlowski wrote:
> On 28/04/2026 09:24, Krzysztof Kozlowski wrote:
> > On Mon, Apr 27, 2026 at 10:34:52AM +0800, Shawn Guo wrote:
...
> >> diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
> >> new file mode 100644
> >> index 000000000000..00d189cfed8c
> >> --- /dev/null
> >> +++ b/arch/arm64/boot/dts/qcom/nord.dtsi
> >> @@ -0,0 +1,4511 @@
> >> +// SPDX-License-Identifier: BSD-3-Clause
> >> +/*
> >> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> >> + */
> >> +
> >> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> >> +
> >> +/ {
> >> + interrupt-parent = <&intc>;
> >> + #address-cells = <2>;
> >> + #size-cells = <2>;
> >> +
> >> + cpus {
> >> + #address-cells = <2>;
> >> + #size-cells = <0>;
> >> +
> >> + cpu0: cpu@0 {
> >> + device_type = "cpu";
> >> + compatible = "qcom,oryon-1-5";
> >
> > I asked you to send this binding WITH the user, because they go via
> > the same tree. I see the user, but no binding for it in the patchset.
>
> And few others like SCM are also missing. I am talking about this many
> times already, to multiple vendors, and I am still surprised why people
> on purpose give more work to the maintainer. Well, not my tree, so not
> my work, but if you ever wonder why your patches are not applied for
> longer time, that could be one of the reasons.
Yes, I should have sent all those bindings targeting Bjorn as part of
this series to make it easier for Bjorn. But I'm not sure cpus.yaml
change is one of them, as I'm sending it to Rob.
Shawn
next prev parent reply other threads:[~2026-04-28 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 2:34 [PATCH 0/4] Add initial device trees for Nord SA8797P Shawn Guo
2026-04-27 2:34 ` [PATCH 1/4] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-04-28 7:24 ` Krzysztof Kozlowski
2026-04-28 7:28 ` Krzysztof Kozlowski
2026-04-28 13:09 ` Shawn Guo [this message]
2026-04-27 2:34 ` [PATCH 2/4] arm64: dts: qcom: Add device tree for Nord SA8797P SoC Shawn Guo
2026-04-27 2:34 ` [PATCH 3/4] dt-bindings: arm: qcom: Document SA8797P Ride board Shawn Guo
2026-04-28 7:23 ` Krzysztof Kozlowski
2026-04-28 13:03 ` Shawn Guo
2026-04-27 2:34 ` [PATCH 4/4] arm64: dts: qcom: Add device tree for " 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=afCxhUaxLEcbosvV@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@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=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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