From: Melody Olvera <quic_molvera@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Georgi Djakov <djakov@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Odelu Kukatla <quic_okukatla@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] dt-bindings: interconnect: Add rpmh virt devices
Date: Tue, 22 Nov 2022 11:57:19 -0600 [thread overview]
Message-ID: <e6ae7c01-47ca-f1da-3b0b-1f17d9e862bf@quicinc.com> (raw)
In-Reply-To: <b7cc4f5d-c1d6-919c-9604-7855ea802d17@linaro.org>
On 11/22/2022 1:50 AM, Krzysztof Kozlowski wrote:
> On 21/11/2022 18:39, Melody Olvera wrote:
>>
>> On 11/20/2022 5:13 AM, Krzysztof Kozlowski wrote:
>>> On 18/11/2022 19:22, Melody Olvera wrote:
>>>> Add documentation for virtual rpmh devices. These interconnects
>>>> are not controlled by the application processor and thus
>>>> require separate bindings. Also, move compatibles for sm8450 to
>>>> this document and add them for QDU1000/QRU1000 platforms.
>>>>
>>>> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
>>>> ---
>>>> .../bindings/interconnect/qcom,rpmh-virt.yaml | 55 +++++++++++++++++++
>>>> .../bindings/interconnect/qcom,rpmh.yaml | 2 -
>>>> 2 files changed, 55 insertions(+), 2 deletions(-)
>>>> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,rpmh-virt.yaml
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,rpmh-virt.yaml b/Documentation/devicetree/bindings/interconnect/qcom,rpmh-virt.yaml
>>>> new file mode 100644
>>>> index 000000000000..5cbaa51df863
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,rpmh-virt.yaml
>>>> @@ -0,0 +1,55 @@
>>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>>>> +%YAML 1.2
>>>> +---
>>>> +$id: http://devicetree.org/schemas/interconnect/qcom,rpmh-virt.yaml#
>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>> +
>>>> +title: Qualcomm RPMh Virtual Network-On-Chip Interconnect
>>>> +
>>>> +maintainers:
>>>> + - Georgi Djakov <georgi.djakov@linaro.org>
>>>> + - Odelu Kukatla <quic_okukatla@quicinc.com>
>>>> +
>>>> +description: |
>>>> + RPMh interconnect providers support system bandwidth requirements through
>>>> + RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
>>>> + able to communicate with the BCM through the Resource State Coordinator (RSC)
>>>> + associated with each execution environment. Provider nodes must point to at
>>>> + least one RPMh device child node pertaining to their RSC and each provider
>>>> + can map to multiple RPMh resources. Virtual interconnect providers are not
>>>> + controlled by AP and do not support QoS; they should not have associated
>>>> + register regions.
>>>> +
>>>> +allOf:
>>>> + - $ref: qcom,rpmh-common.yaml#
>>>> +
>>>> +properties:
>>>> + compatible:
>>>> + enum:
>>>> + - qcom,qdu1000-clk-virt
>>>> + - qcom,qdu1000-mc-virt
>>>> + - qcom,sm8450-clk-virt
>>>> + - qcom,sm8450-mc-virt
>>> You should also move qcom,sdx65-mc-virt, qcom,sc8280xp-mc-virt,
>>> qcom,sc8280xp-clk-virt and more.
>> Ok. I wasn't sure since some of these entries don't seem to conform to
>> these bindings, even though it seems they should.
> I have impression that devices I listed conform to these bindings, this
> is why I listed them. But if you are sure that they do not, then they
> should not be moved.
You're correct; those you listed do conform to the new bindings and should be moved.
I also caught qcom,sc7280-clk-virt which needs to be moved. I'll add to the new bindings.
Thanks,
Melody
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-11-22 17:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:22 [PATCH v4 0/3] Add interconnect support for QDU1000/QRU1000 SoCs Melody Olvera
2022-11-18 18:22 ` [PATCH v4 1/3] dt-bindings: interconnect: Add rpmh virt devices Melody Olvera
2022-11-20 11:13 ` Krzysztof Kozlowski
2022-11-21 17:39 ` Melody Olvera
2022-11-22 7:50 ` Krzysztof Kozlowski
2022-11-22 17:57 ` Melody Olvera [this message]
2022-11-24 10:30 ` Krzysztof Kozlowski
2022-11-28 17:25 ` Melody Olvera
2022-11-28 23:08 ` Melody Olvera
2022-11-28 23:14 ` Melody Olvera
2022-11-21 15:23 ` Georgi Djakov
2022-11-21 16:34 ` Krzysztof Kozlowski
2022-11-21 17:38 ` Melody Olvera
2022-11-18 18:22 ` [PATCH v4 2/3] dt-bindings: interconnect: Add QDU1000/QRU1000 devices Melody Olvera
2022-11-20 11:13 ` Krzysztof Kozlowski
2022-11-18 18:22 ` [PATCH v4 3/3] interconnect: qcom: Add QDU1000/QRU1000 interconnect driver Melody Olvera
2022-11-20 12:19 ` Christophe JAILLET
2022-11-21 17:55 ` Melody Olvera
2022-11-21 19:02 ` Christophe JAILLET
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=e6ae7c01-47ca-f1da-3b0b-1f17d9e862bf@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_okukatla@quicinc.com \
--cc=robh+dt@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).