From: "Aiqun(Maria) Yu" <aiqun.yu@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
tingwei.zhang@oss.qualcomm.com, trilok.soni@oss.qualcomm.com,
yijie.yang@oss.qualcomm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: cpus: Add Qualcomm Oryon compatibles
Date: Thu, 20 Nov 2025 16:50:20 +0800 [thread overview]
Message-ID: <77bcb402-dc38-4f04-95e4-ff4fd5812ac1@oss.qualcomm.com> (raw)
In-Reply-To: <20251120-tacky-perfect-barnacle-0fb27d@kuoka>
On 11/20/2025 4:24 PM, Krzysztof Kozlowski wrote:
> On Wed, Nov 19, 2025 at 09:50:53PM -0800, Jingyi Wang wrote:
>> Previous "qcom,oryon" is too generic, add specific cpu bindings:
>
> Why is too generic? Why gen1/2/3 is not generic? Both sound exactly the
> same for me - arbitrary number incremented from 1 does not make it less
> generic.
This is align the qualcomm announced cpu information, there is no other
more information revealed publicly. The reference is from [1].
For me, it is likely the generation numbers information is having more
information compare to "qcom,oryon". And the current patch is to be
address the comments like [2]. What's your specific suggestion on this pls?
[1]
https://www.qualcomm.com/smartphones/products/8-series/snapdragon-8-elite-gen-5
[2]
https://lore.kernel.org/all/2960a6fc-106b-4280-b4d4-9c1a3a449454@oss.qualcomm.com/
>
>> qcom,oryon-gen1 for X1E80100, qcom,oryon-gen2 for SM8750, qcom,oryon-gen3
>> for Kaanapali.
>>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>
> Best regards,
> Krzysztof
>
--
Thx and BRs,
Aiqun(Maria) Yu
next prev parent reply other threads:[~2025-11-20 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 5:50 Jingyi Wang
2025-11-20 8:24 ` Krzysztof Kozlowski
2025-11-20 8:50 ` Aiqun(Maria) Yu [this message]
2025-11-20 9:00 ` Krzysztof Kozlowski
2025-11-20 11:21 ` Krzysztof Kozlowski
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=77bcb402-dc38-4f04-95e4-ff4fd5812ac1@oss.qualcomm.com \
--to=aiqun.yu@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@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
all inboxes | Powered by JetHome®