From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Kalle Valo <kvalo@kernel.org>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<jassisinghbrar@gmail.com>, <mathieu.poirier@linaro.org>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<quic_eberman@quicinc.com>, <quic_mojha@quicinc.com>,
<loic.poulain@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_anusha@quicinc.com>,
<quic_poovendh@quicinc.com>, <quic_varada@quicinc.com>,
<quic_devipriy@quicinc.com>
Subject: Re: [PATCH V2 01/13] dt-bindings: remoteproc: qcom: Add support for multipd model
Date: Tue, 18 Jul 2023 17:40:59 +0530 [thread overview]
Message-ID: <0fbbb9c9-f215-cf41-ec34-8c726a167bbf@quicinc.com> (raw)
In-Reply-To: <2eace846-1feb-4299-4678-e1ff06179fdc@linaro.org>
On 7/1/2023 4:21 PM, Krzysztof Kozlowski wrote:
> On 30/06/2023 09:12, Manikanta Mylavarapu wrote:
>>
>>
>> On 6/24/2023 12:49 PM, Krzysztof Kozlowski wrote:
>>> On 21/06/2023 13:39, Manikanta Mylavarapu wrote:
>>>>>> on number of wcss radios connected on that board and only one instance
>>>>>> of 'qcom,ipq5018-q6-mpd'.
>>>>>>
>>>>>
>>>>> I don't understand why the user protection domains need a specific
>>>>> compatible. Why do they need compatible at all?
>>>>>
>>>>> Not mentioning that amount of your domains on Q6 is actually fixed per
>>>>> SoC and probably should not be in DT at all.
>>>>>
>>>> root domain is fixed per soc (One Q6 DSP, one per soc)
>>>> user domain(s) are variable (based on number of wcss radios attached)
>>>>
>>>> The sequence to initialize, bring up, tear down the Q6 and wcss radios
>>>> are completely different. So in order to differentiate them, we will
>>>> need different compatibles. So this is a new rproc driver/architecture
>>>> which has a parent/child topology (Q6 DSP -> Master/parent controls
>>>> the WCSS (child)).
>>>
>>> I understand you need different properties, but I don't see yet the
>>> benefit of creating here artificial compatibles. Look at your ipq9574
>>> DTSI change - it does not use even ipq9574 compatibles for 66% of its
>>> children.
>>>
>>> Maybe you should have there just property describing type of device or
>>> bringup?
>>>
>>
>> Yeah i got your point. Indeed the requirement here is to
>> have device specific compatibles, so will have just two
>> compatible one for Q6-MPD and another for WCSS-MPD device's
>>
>>
>> "qcom,q6-mpd" --> For Q6-MPD device
>> "qcom,wcss-mpd" --> For WCSS-MPD device
>>
>> Is this approach fine ?
>
> Can you fix your reply style, so it is like on every mailing list? Some
> weird indentation does no help to read it.
>
Sure, i will change my reply style and don't use any indentation.
Sorry for inconvenience.
> I was proposing to drop compatibles entirely. Making compatibles generic
> is not solving any of my concerns.
>
> I don't understand what do you want to achieve here and very limited
> description of the hardware in the binding does not help.
>
Sure, i remove user pd compatibles. In root pd probe itself, user pd
remoteproc's are taken care. Also I updated diagram in cover page, it
gives enough information.
>>
>>> Given SoC cannot come with different amount of children (PD) and
>>> different amount of radios. You even fix the firmware name, so
>>> boards/customers cannot use anything else. It's fixed and the only
>>> variable element here is disabling some of the blocks per board, if they
>>> do not have physical interface (e.g. radio).
>>>
>>> You even hard-code the number of PD by using "pd-[123]", without unit
>>> address, so you do not expect it will grow.
>>>
>>> Unless you want to say that these are devices? But your binding does not
>>> really suggest it...
>>>
>>>
>>> Yes, as i mentioned above the requirement is to have device
>
> What requirement? You did not describe anything. Binding describes
> hardware, not your requirements.
>
> Binding said nothing about devices.
>
Yeah got your point. So we removed userpd compatibles from dt-bindings.
>> specific bindings. We will remove "PD-X" from soc dtsi and
>> add it in board dts file.
>
> Why? How is it related to the bindings? What does it solve? Instead of
> doing some changes you should explain why.
>
>>
>> So soc dts would have "Q6-MPD" master node & board dts have
>> "WCSS-MPD" child nodes based on number of radio's connected
>> on board.
>>
>> Is this fine ?
>>
>
> Why?
>
"PD-X" controls user pd WCSS bring up. WCSS blocks may vary based on
number of radio's connected on board but QDSP6 is always present.
So i will keep Q6 node in soc dtsi file and move 'PD-X' node to board
dts file.
Thanks & Regards,
Manikanta.
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-07-18 12:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 22:28 [PATCH V2 00/13] Add multipd remoteproc support Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 01/13] dt-bindings: remoteproc: qcom: Add support for multipd model Manikanta Mylavarapu
2023-05-30 10:46 ` Krzysztof Kozlowski
2023-06-05 5:58 ` Manikanta Mylavarapu
2023-05-30 10:58 ` Krzysztof Kozlowski
2023-06-05 8:03 ` Manikanta Mylavarapu
2023-06-05 12:02 ` Manikanta Mylavarapu
2023-06-06 6:14 ` Krzysztof Kozlowski
2023-06-06 12:11 ` Manikanta Mylavarapu
2023-06-06 13:49 ` Kalle Valo
2023-06-07 8:10 ` Manikanta Mylavarapu
2023-06-07 8:27 ` Krzysztof Kozlowski
2023-06-14 11:43 ` Manikanta Mylavarapu
2023-06-14 12:49 ` Manikanta Mylavarapu
2023-06-14 13:59 ` Krzysztof Kozlowski
2023-06-21 11:39 ` Manikanta Mylavarapu
2023-06-24 7:19 ` Krzysztof Kozlowski
2023-06-30 7:12 ` Manikanta Mylavarapu
2023-07-01 10:51 ` Krzysztof Kozlowski
2023-07-18 12:10 ` Manikanta Mylavarapu [this message]
2023-06-08 12:59 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 02/13] dt-bindings: mailbox: qcom: Add IPQ5018 APCS compatible Manikanta Mylavarapu
2023-05-30 10:59 ` Krzysztof Kozlowski
2023-05-21 22:28 ` [PATCH V2 03/13] dt-bindings: arm: qcom: Document the Qualcomm rdp432-c1 board Manikanta Mylavarapu
2023-05-30 10:59 ` Krzysztof Kozlowski
2023-06-05 5:29 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 04/13] dt-bindings: clock: qcom: gcc-ipq5018: remove q6 clocks macros Manikanta Mylavarapu
2023-05-30 11:01 ` Krzysztof Kozlowski
2023-06-01 18:55 ` Robert Marko
2023-06-05 6:22 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 05/13] dt-bindings: clock: qcom: gcc-ipq9574: remove q6 bring up clock macros Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 06/13] clk: qcom: ipq5018: remove q6 bring up clocks Manikanta Mylavarapu
2023-05-30 11:03 ` Krzysztof Kozlowski
2023-06-06 12:17 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 07/13] clk: qcom: ipq9574: " Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 08/13] firmware: qcom_scm: ipq5018: Add WCSS AHB pd support Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 09/13] remoteproc: qcom: q6v5: Add multipd interrupts support Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 10/13] remoteproc: qcom: Add Hexagon based multipd rproc driver Manikanta Mylavarapu
2023-06-24 7:28 ` Krzysztof Kozlowski
[not found] ` <54f06704-a849-7049-5956-31cb4765a1eb@quicinc.com>
2023-06-30 10:29 ` Manikanta Mylavarapu
2023-07-01 10:55 ` Krzysztof Kozlowski
2023-07-18 12:10 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 11/13] arm64: dtsi: qcom: ipq5018: enable nodes required for multipd Manikanta Mylavarapu
2023-05-30 11:05 ` Krzysztof Kozlowski
2023-06-05 5:35 ` Manikanta Mylavarapu
2023-06-05 5:38 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 12/13] arm64: dts: qcom: ipq5018: Add RDP432-c1 board support Manikanta Mylavarapu
2023-05-30 11:06 ` Krzysztof Kozlowski
2023-06-08 12:33 ` Manikanta Mylavarapu
2023-05-21 22:28 ` [PATCH V2 13/13] arm64: dtsi: qcom: ipq9574: Add nodes to bring up multipd Manikanta Mylavarapu
2023-06-24 7:01 ` Krzysztof Kozlowski
[not found] ` <15bdbd23-9066-ee20-1e29-1d086340c133@quicinc.com>
2023-06-30 7:11 ` Manikanta Mylavarapu
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=0fbbb9c9-f215-cf41-ec34-8c726a167bbf@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=mturquette@baylibre.com \
--cc=quic_anusha@quicinc.com \
--cc=quic_devipriy@quicinc.com \
--cc=quic_eberman@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_mojha@quicinc.com \
--cc=quic_poovendh@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).