From: Georgi Djakov <georgi.djakov@linaro.org>
To: linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, bjorn.andersson@linaro.org,
sibis@codeaurora.org, mka@chromium.org, dianders@chromium.org,
georgi.djakov@linaro.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/7] dt-bindings: interconnect: Document the support of optional path tag
Date: Thu, 6 Aug 2020 19:31:21 +0300 [thread overview]
Message-ID: <20200806163126.22667-3-georgi.djakov@linaro.org> (raw)
In-Reply-To: <20200806163126.22667-1-georgi.djakov@linaro.org>
Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT property. This information would be
populated when the xlate_extended() callback is used.
Specifying the tag in DT will allow the interconnect framework to do the
aggregation based on the tag automatically. The users can still use the
icc_set_tag() API if/when needed.
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
---
.../bindings/interconnect/interconnect.txt | 24 ++++++++++++++++++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt
index 6f5d23a605b7..138c544c8c8c 100644
--- a/Documentation/devicetree/bindings/interconnect/interconnect.txt
+++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt
@@ -19,7 +19,8 @@ directly.
Required properties:
- compatible : contains the interconnect provider compatible string
- #interconnect-cells : number of cells in a interconnect specifier needed to
- encode the interconnect node id
+ encode the interconnect node id and optionally add a
+ path tag
Example:
@@ -44,6 +45,10 @@ components it has to interact with.
Required properties:
interconnects : Pairs of phandles and interconnect provider specifier to denote
the edge source and destination ports of the interconnect path.
+ An optional path tag value could specified as additional argument
+ to both endpoints and in such cases, this information will be passed
+ to the interconnect framework to do aggregation based on the attached
+ tag.
Optional properties:
interconnect-names : List of interconnect path name strings sorted in the same
@@ -62,3 +67,20 @@ Example:
interconnects = <&pnoc MASTER_SDCC_1 &bimc SLAVE_EBI_CH0>;
interconnect-names = "sdhc-mem";
};
+
+Example with path tags:
+
+ gnoc: interconnect@17900000 {
+ ...
+ interconnect-cells = <2>;
+ };
+
+ mnoc: interconnect@1380000 {
+ ...
+ interconnect-cells = <2>;
+ };
+
+ cpu@0 {
+ ...
+ interconnects = <&gnoc MASTER_APPSS_PROC 3 &mnoc SLAVE_EBI1 3>;
+ }
next prev parent reply other threads:[~2020-08-06 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 16:31 [PATCH v2 0/7] interconnect: Introduce xlate_extended() Georgi Djakov
2020-08-06 16:31 ` [PATCH v2 1/7] interconnect: Introduce xlate_extended() callback Georgi Djakov
2020-08-06 16:31 ` Georgi Djakov [this message]
2020-08-17 21:55 ` [PATCH v2 2/7] dt-bindings: interconnect: Document the support of optional path tag Rob Herring
2020-08-06 16:31 ` [PATCH v2 3/7] interconnect: qcom: Implement xlate_extended() to parse tags Georgi Djakov
2020-08-06 16:31 ` [PATCH v2 4/7] interconnect: qcom: sdm845: Replace xlate with xlate_extended Georgi Djakov
2020-08-06 16:31 ` [PATCH v2 5/7] arm64: dts: qcom: sdm845: Increase the number of interconnect cells Georgi Djakov
2020-08-19 20:07 ` Doug Anderson
2020-08-06 16:31 ` [PATCH v2 6/7] interconnect: qcom: sc7180: Replace xlate with xlate_extended Georgi Djakov
2020-08-06 16:31 ` [PATCH v2 7/7] arm64: dts: qcom: sc7180: Increase the number of interconnect cells Georgi Djakov
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=20200806163126.22667-3-georgi.djakov@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.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).