From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Trilok Soni <quic_tsoni@quicinc.com>,
Nikunj Kela <quic_nkela@quicinc.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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>
Subject: Re: DT Query on "New Compatible vs New Property"
Date: Tue, 12 Mar 2024 17:21:52 +0000 [thread overview]
Message-ID: <bd2dde74-e4b9-4cf8-b1f1-9bc52f3b83da@linaro.org> (raw)
In-Reply-To: <3aad2e6b-88fd-06ab-95c5-d07f012e8306@quicinc.com>
On 12/03/2024 16:58, Trilok Soni wrote:
> On 3/12/2024 9:52 AM, Nikunj Kela wrote:
>>> One is with old firmware interface and -scmi is with SCMI. No new top
>>> level compatible change is needed. I understand it was switch from one
>>> interface to the another and not like Qcom platforms which is moving
>>> from in-kernel solution to firmware solution. But the general rule applies
>>> here as well unless there are specific reasons for needing that exception.
>>> I am not against it or ruling that out, just curious to understand them.
>>>
>>> --
>>> Regards,
>>> Sudeep
>>
>> Hi All,
>>
>> Thank you all for all your inputs on this. I discussed this with Srini and he suggested that we could use a new optional DT property like "qcom, fw-managed" to ascertain if we are running on firmware managed variant. Thus each device node in the dts can add this. I did ask him if, instead of putting it to each device node, we can use it at the board level however he thinks that it would not be easy to update yaml documentation on DT nodes with board level property. So if everyone here agrees with this approach, I would like to close this thread.
>>
>> Thank you!
>
> Is "fw-managed" name restricted to SCMI based approaches? Why it needs to be per
> driver device-tree node?
This makes it much more explicit in device bindings on the resource
dependencies.
What happens when I attach the same SOC-IP
> along w/ the RISC-V Application core and use the RPMI?
>
> Should not have fw-managed defined at the devicetree spec? This is not a
> ARM specific problem since the drivers which are going to use this flag/property
> are generic shouldn't care about SCMI/RPMI.
>
> Basically, I would prefer better than "qcom, fw-managed" since this is not
> a qcom specific problem.
We already have something like this in mainline where the BAM DMA
controller is remotely powered.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/dma/qcom,bam-dma.yaml?h=v6.8
--srini
>
next prev parent reply other threads:[~2024-03-12 17:21 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
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 [this message]
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=bd2dde74-e4b9-4cf8-b1f1-9bc52f3b83da@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_nkela@quicinc.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=robh+dt@kernel.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).