LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: David Dai <daidavid1@codeaurora.org>
Cc: georgi.djakov@linaro.org, bjorn.andersson@linaro.org,
evgreen@google.com, sboyd@kernel.org, ilina@codeaurora.org,
seansw@qti.qualcomm.com, elder@linaro.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 3/6] dt-bindings: interconnect: Update Qualcomm SDM845 DT bindings
Date: Wed, 15 Jan 2020 08:49:42 -0600 [thread overview]
Message-ID: <20200115144942.GA15075@bogus> (raw)
In-Reply-To: <1578630784-962-4-git-send-email-daidavid1@codeaurora.org>
On Thu, Jan 09, 2020 at 08:33:01PM -0800, David Dai wrote:
> Redefine the Network-on-Chip devices to more accurately describe
> the interconnect topology on Qualcomm's SDM845 platform. Each
> interconnect device can communicate with different instances of the
> RPMh hardware which are described as RSCs(Resource State Coordinators).
>
> Signed-off-by: David Dai <daidavid1@codeaurora.org>
> ---
> .../bindings/interconnect/qcom,sdm845.yaml | 49 ++++++++++++++++++----
> 1 file changed, 40 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,sdm845.yaml b/Documentation/devicetree/bindings/interconnect/qcom,sdm845.yaml
> index 61e0097..6741a12 100644
> --- a/Documentation/devicetree/bindings/interconnect/qcom,sdm845.yaml
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,sdm845.yaml
> @@ -13,21 +13,44 @@ description: |
> SDM845 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 reside within
> - an RPMh device node pertaining to their RSC and each provider maps to a
> - single RPMh resource.
> + 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.
>
> properties:
> + reg:
> + maxItems: 1
> +
> compatible:
> enum:
> - - qcom,sdm845-rsc-hlos
> + - qcom,sdm845-aggre1-noc
> + - qcom,sdm845-aggre2-noc
> + - qcom,sdm845-config-noc
> + - qcom,sdm845-dc-noc
> + - qcom,sdm845-gladiator-noc
> + - qcom,sdm845-mem-noc
> + - qcom,sdm845-mmss-noc
> + - qcom,sdm845-system-noc
>
> '#interconnect-cells':
> const: 1
>
> + qcom,bcm-voter-names:
> + items:
> + - const: apps
> + - const: disp
If these are always the names, why do you need them?
> +
> + qcom,bcm-voters:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: |
> + List of phandles to qcom,bcm-voter nodes that are required by
> + this interconnect to send RPMh commands.
Is the max length 2?
> +
> required:
> - compatible
> + - reg
> - '#interconnect-cells'
> + - qcom,bcm-voters
>
> additionalProperties: false
>
> @@ -35,9 +58,17 @@ examples:
> - |
> #include <dt-bindings/interconnect/qcom,sdm845.h>
>
> - apps_rsc: rsc {
> - rsc_hlos: interconnect {
> - compatible = "qcom,sdm845-rsc-hlos";
> - #interconnect-cells = <1>;
> - };
> + mem_noc: interconnect@1380000 {
> + compatible = "qcom,sdm845-mem-noc";
> + reg = <0 0x01380000 0 0x27200>;
> + #interconnect-cells = <1>;
> + qcom,bcm-voters = <&apps_bcm_voter>;
> + };
> +
> + mmss_noc: interconnect@1740000 {
> + compatible = "qcom,sdm845-mmss-noc";
> + reg = <0 0x01740000 0 0x1c1000>;
> + #interconnect-cells = <1>;
> + qcom,bcm-voter-names = "apps", "disp";
> + qcom,bcm-voters = <&apps_bcm_voter>, <&disp_bcm_voter>;
> };
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2020-01-15 14:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 4:32 [PATCH v2 0/6] Split SDM845 interconnect nodes and consolidate RPMh support David Dai
2020-01-10 4:32 ` [PATCH v2 1/6] dt-bindings: interconnect: Convert qcom,sdm845 to DT schema David Dai
2020-01-15 14:39 ` Rob Herring
2020-01-10 4:33 ` [PATCH v2 2/6] dt-bindings: interconnect: Add YAML schemas for QCOM bcm-voter David Dai
2020-01-15 14:44 ` Rob Herring
2020-01-10 4:33 ` [PATCH v2 3/6] dt-bindings: interconnect: Update Qualcomm SDM845 DT bindings David Dai
2020-01-15 14:49 ` Rob Herring [this message]
2020-01-17 0:07 ` David Dai
2020-01-31 21:35 ` Evan Green
2020-01-10 4:33 ` [PATCH v2 4/6] interconnect: qcom: Consolidate interconnect RPMh support David Dai
2020-02-04 18:22 ` Evan Green
2020-02-09 17:58 ` Sibi Sankar
2020-01-10 4:33 ` [PATCH v2 5/6] interconnect: qcom: sdm845: Split qnodes into their respective NoCs David Dai
2020-02-04 18:21 ` Evan Green
2020-02-09 18:04 ` Sibi Sankar
2020-01-10 4:33 ` [PATCH v2 6/6] arm64: dts: sdm845: Redefine interconnect provider DT nodes David Dai
2020-02-04 18:18 ` Evan Green
2020-02-09 18:03 ` Sibi Sankar
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=20200115144942.GA15075@bogus \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@google.com \
--cc=georgi.djakov@linaro.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=seansw@qti.qualcomm.com \
--subject='Re: [PATCH v2 3/6] dt-bindings: interconnect: Update Qualcomm SDM845 DT bindings' \
/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
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).