From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Nikunj Kela <quic_nkela@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
krzysztof.kozlowski+dt@linaro.org,
Vincent Guittot <vincent.guittot@linaro.org>,
robh+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org,
"Prasad Sodagudi (QUIC)" <quic_psodagud@quicinc.com>,
srinivas.kandagatla@linaro.org
Subject: Re: DT Query on "New Compatible vs New Property"
Date: Wed, 28 Feb 2024 15:20:44 +0100 [thread overview]
Message-ID: <799268ac-7ffb-4b99-b037-d5bb93d37f13@linaro.org> (raw)
In-Reply-To: <20240228140239.gkzcytw6cmb4opja@bogus>
On 28/02/2024 15:02, Sudeep Holla wrote:
> On Wed, Feb 28, 2024 at 02:27:30PM +0100, Ulf Hansson wrote:
>> On Mon, 26 Feb 2024 at 15:24, Nikunj Kela <quic_nkela@quicinc.com> wrote:
>>>
>>> Hi Sudeep,
>>>
>>> I would like to conclude on this thread. I was discussing this with Ulf.
>>> He thinks that using the domain names to identify if platform is
>>> abstracting clocks etc. are not scalable and sufficient. Instead he
>>> thinks that the change in the interface to OS(and FW) is a good
>>> candidate for a new compatible(even though HW is same). Even for SCMI,
>>> we do change phandle in DT to SCMI protocol phandle so that is like a
>>> different platform altogether. Could you please let me know if you still
>>> think that using a different compatible in this case is not warranted.
>>
>> My apologies for joining this discussion at this late state. Yet, I
>> just wanted to confirm what Nikunj said above.
>>
>> In the end we are indeed talking about adding a new platform, as
>> changing the FW interface from a QCOM proprietary one into SCMI,
>> simply requires updates to a DTS file(s) that is platform specific.
>>
>
> The way I read this sounds like all this are platform specific and need
> new compatible.
>
>> That said, it also seems reasonable to me to use a compatible string,
>> to allow us to describe the update of HW for various affected devices.
>>
>
> While I agree with the above statement, it depends on what you refer as
> update of HW above. It is all Qcom specific and there is so much turn
> between SoCs that this shouldn't matter but I would like to take example
> and describe what I initially mentioned/argued against.
>
> Lets us assume 2 SoCs: A and B. A is old and didn't use SCMI while B is
> new and migrated to use SCMI. Now let us assume both A and B SoCs have
> exact same version/revision of an IP: X. Now just because B uses SCMI,
> should X have one compatible to be used in A and another in B. That
> doesn't sound right IMO.
That's trivial to answer, because these are different SoCs. Compatibles
are SoC specific and every SoC-IP-block needs its compatible. Rob was
repeating this many times that versioned compatibles are discouraged.
>
> If X on A has to manage clocks and voltage separately while the same X
> on B uses SCMI to manage them together as performance domain, then the
> presence(or absence) of those properties must indicate the difference and
> not a change in compaible for the IP X. But it is upto Qcom platform
> maintainer, IP driver maintainer and DT maintainers to decide, I will
> leave that them. I just wanted to express my opinion on the matter.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-28 14:20 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:45 DT Query on "New Compatible vs New Property" Nikunj Kela
2023-12-12 19:01 ` Krzysztof Kozlowski
2023-12-12 19:06 ` Nikunj Kela
2023-12-14 6:17 ` Manivannan Sadhasivam
2023-12-14 7:49 ` Krzysztof Kozlowski
2023-12-14 15:18 ` Nikunj Kela
2024-01-23 16:12 ` Manivannan Sadhasivam
2024-01-24 8:02 ` Krzysztof Kozlowski
2024-01-24 8:39 ` Manivannan Sadhasivam
2024-01-24 8:45 ` Krzysztof Kozlowski
2024-01-24 8:53 ` Manivannan Sadhasivam
2024-01-24 9:01 ` Krzysztof Kozlowski
2024-01-24 9:27 ` Manivannan Sadhasivam
2024-01-24 9:40 ` Krzysztof Kozlowski
2024-01-24 10:36 ` Manivannan Sadhasivam
2024-01-24 10:23 ` Sudeep Holla
2024-01-24 10:45 ` Manivannan Sadhasivam
2024-01-24 11:02 ` Sudeep Holla
2024-01-24 12:27 ` Nikunj Kela
2024-01-24 12:48 ` Sudeep Holla
2024-01-24 13:17 ` Nikunj Kela
2024-01-24 13:38 ` Vincent Guittot
2024-01-24 14:04 ` Sudeep Holla
2024-01-24 14:28 ` Nikunj Kela
2024-01-24 17:24 ` Sudeep Holla
2024-01-24 17:33 ` Nikunj Kela
2024-02-26 14:22 ` Nikunj Kela
2024-02-28 13:27 ` Ulf Hansson
2024-02-28 14:02 ` Sudeep Holla
2024-02-28 14:20 ` Krzysztof Kozlowski [this message]
2024-02-28 16:09 ` Sudeep Holla
2024-02-28 16:22 ` Ulf Hansson
2024-02-28 17:11 ` Srinivas Kandagatla
2024-03-01 11:53 ` Ulf Hansson
2024-03-04 11:01 ` Sudeep Holla
2024-03-12 16:52 ` Nikunj Kela
2024-03-12 16:58 ` Trilok Soni
2024-03-12 17:08 ` Nikunj Kela
2024-03-12 17:21 ` Srinivas Kandagatla
2024-03-12 17:25 ` Trilok Soni
2024-03-13 9:19 ` Ulf Hansson
2024-03-13 9:31 ` Nikunj Kela
2024-03-13 11:21 ` Srinivas Kandagatla
2024-03-13 11:49 ` Srinivas Kandagatla
2024-03-13 22:40 ` Trilok Soni
2024-04-10 16:53 ` Nikunj Kela
2024-04-11 9:29 ` Sudeep Holla
2024-03-13 11:04 ` Sudeep Holla
2024-03-13 13:04 ` Srinivas Kandagatla
2024-03-14 10:55 ` Sudeep Holla
2024-03-14 12:35 ` Nikunj Kela
2024-03-14 15:38 ` Sudeep Holla
2024-03-16 19:30 ` Trilok Soni
2024-03-19 10:17 ` Srinivas Kandagatla
2024-03-19 12:00 ` Sudeep Holla
2024-03-19 14:40 ` Srinivas Kandagatla
2024-03-19 15:17 ` Sudeep Holla
2024-03-19 15:41 ` Srinivas Kandagatla
2024-03-19 16:13 ` Sudeep Holla
2024-04-10 16:55 ` Nikunj Kela
2024-04-10 17:13 ` Krzysztof Kozlowski
2024-04-10 17:24 ` Nikunj Kela
2024-04-11 15:44 ` Conor Dooley
2024-04-11 15:55 ` Nikunj Kela
2024-04-11 19:29 ` Krzysztof Kozlowski
2024-04-12 10:16 ` Sudeep Holla
2024-04-11 9:23 ` Sudeep Holla
2024-04-11 15:59 ` Nikunj Kela
2024-04-12 10:12 ` Sudeep Holla
2024-01-24 14:01 ` Sudeep Holla
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=799268ac-7ffb-4b99-b037-d5bb93d37f13@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_nkela@quicinc.com \
--cc=quic_psodagud@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).