From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Aiqun(Maria) Yu" <aiqun.yu@oss.qualcomm.com>,
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 12:21:02 +0100 [thread overview]
Message-ID: <5c4864fa-bf73-4397-8098-2a28f31c81f5@kernel.org> (raw)
In-Reply-To: <44474c4c-fcc6-4508-b311-de5c4636c75b@kernel.org>
On 20/11/2025 10:00, Krzysztof Kozlowski wrote:
> On 20/11/2025 09:50, Aiqun(Maria) Yu wrote:
>> 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?
>
> There is no context in this commit msg and patch is sent completely
> without users, so how anyone can guess above?
>
> The original compatible was never acked by any DT maintainers. What's
> more Konrad raised objections to it at v1 (!!!) 2 years ago and provided
> the answer what is expected.
>
> It is not my task to dig old thread like that, because it is not me who
> proposes this patch.
>
> You are doing it for some reason, so you must come with the background
> and the rationale.
>
For the context here was Konrad's request:
https://lore.kernel.org/lkml/b165d2cd-e8da-4f6d-9ecf-14df2b803614@linaro.org/
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-20 11:21 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
2025-11-20 9:00 ` Krzysztof Kozlowski
2025-11-20 11:21 ` Krzysztof Kozlowski [this message]
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=5c4864fa-bf73-4397-8098-2a28f31c81f5@kernel.org \
--to=krzk@kernel.org \
--cc=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=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®