From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shawn Guo <shengchao.guo@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 <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5
Date: Mon, 13 Apr 2026 14:40:18 +0200 [thread overview]
Message-ID: <1c06bd0f-24ce-4ea2-a7a1-4c61827b4763@kernel.org> (raw)
In-Reply-To: <adzjYypJciYFLT6F@QCOM-aGQu4IUr3Y>
On 13/04/2026 14:36, Shawn Guo wrote:
> On Mon, Apr 13, 2026 at 12:02:48PM +0200, Krzysztof Kozlowski wrote:
>> On 13/04/2026 11:16, Shawn Guo wrote:
>>> Qualcomm Oryon 1-5 is found on Nord SoC. Add compatible for it.
>>>
>>> $ cat /proc/cpuinfo
>>> ...
>>> CPU implementer : 0x51
>>> CPU architecture: 8
>>> CPU variant : 0x5
>>> CPU part : 0x001
>>> CPU revision : 4
>>>
>>> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>
>> No. I said many times. Bindings come with the user. We don't care what
>> is in cpuinfo of some non-upstream board (and lack of user means it is
>> non-upstream currently).
>
> I was not aware of this requirement, and I see many bindings that
I am not saying anything new here.
> currently do not have any in-tree users, e.g. qcom,oryon-2-3 in cpus.yaml.
And what is the reason for having oryon-2-3 in the kernel? I treat
arguments "I found a code like this, so I can do the same" as proof of
lack of actual technical arguments.
>
>> Please organize your patchset correctly.
>
> Are you asking for a big series that consists of all the new bindings
> used by Nord DTS and DTS itself? Unless this big series gets applied as
> one-go, there are still chances that bindings get into a kernel release
> without any users, e.g. subsystem maintainers pick up bindgins being
> reviewed, but DTS requires more iterations and thus misses the release.
Please follow existing rules, communicated multiple times on the mailing
list. Qualcomm also has internal guideline clarifying this.
Below are some upstream discussion clarifying this:
https://lore.kernel.org/linux-samsung-soc/CADrjBPq_0nUYRABKpskRF_dhHu+4K=duPVZX==0pr+cjSL_caQ@mail.gmail.com/T/#m2d9130a1342ab201ab49670fa6c858ee3724c83c
https://lore.kernel.org/all/49258645-d4d8-44a5-a4fc-b403c926a5d1@kernel.org/
And how to do it:
https://lore.kernel.org/all/20231121-topic-sm8650-upstream-dt-v3-0-db9d0507ffd3@linaro.org/
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-13 12:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 9:16 [PATCH 0/2] dt-bindings: arm: cpus: Fix and extend Qualcomm Oryon compatibles Shawn Guo
2026-04-13 9:16 ` [PATCH 1/2] dt-bindings: arm: cpus: Restore qcom,oryon-1-4 compatible Shawn Guo
2026-04-13 9:57 ` Konrad Dybcio
2026-04-13 10:01 ` Krzysztof Kozlowski
2026-04-13 12:06 ` Shawn Guo
2026-04-13 9:16 ` [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5 Shawn Guo
2026-04-13 9:58 ` Konrad Dybcio
2026-04-13 10:02 ` Krzysztof Kozlowski
2026-04-13 12:36 ` Shawn Guo
2026-04-13 12:40 ` Krzysztof Kozlowski [this message]
2026-04-13 13:10 ` Shawn Guo
2026-04-13 13:30 ` Krzysztof Kozlowski
2026-04-13 14:34 ` Shawn Guo
2026-04-13 16:08 ` Krzysztof Kozlowski
2026-04-14 1:21 ` Shawn Guo
2026-04-14 6:23 ` Krzysztof Kozlowski
2026-04-14 6:59 ` Shawn Guo
2026-04-14 7:05 ` Krzysztof Kozlowski
2026-04-14 7:11 ` Krzysztof Kozlowski
2026-04-14 8:01 ` 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=1c06bd0f-24ce-4ea2-a7a1-4c61827b4763@kernel.org \
--to=krzk@kernel.org \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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