From: Georgi Djakov <georgi.djakov@linaro.org> To: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org Cc: rjw@rjwysocki.net, robh+dt@kernel.org, mturquette@baylibre.com, khilman@baylibre.com, vincent.guittot@linaro.org, skannan@codeaurora.org, bjorn.andersson@linaro.org, amit.kucheria@linaro.org, seansw@qti.qualcomm.com, daidavid1@codeaurora.org, evgreen@chromium.org, mark.rutland@arm.com, lorenzo.pieralisi@arm.com, abailon@baylibre.com, arnd@arndb.de, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [PATCH v7 7/8] dt-bindings: Introduce interconnect consumers bindings Date: Tue, 31 Jul 2018 19:13:39 +0300 [thread overview] Message-ID: <20180731161340.13000-8-georgi.djakov@linaro.org> (raw) In-Reply-To: <20180731161340.13000-1-georgi.djakov@linaro.org> Add documentation for the interconnect consumer bindings, that will allow to link a device node (consumer) to its interconnect controller hardware. Tha aim is to enable drivers to request a framework API to configure an interconnect path by providing their struct device pointer and a name. Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> --- .../bindings/interconnect/interconnect.txt | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt index 6e2b2971b094..5cb7d3c8d44d 100644 --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt @@ -31,3 +31,30 @@ Example: clocks = <&rpmcc RPM_SMD_SNOC_CLK>, <&rpmcc RPM_SMD_SNOC_A_CLK>; }; + + += interconnect consumers = + +The interconnect consumers are device nodes which dynamically express their +bandwidth requirements along interconnect paths they are connected to. There +can be multiple interconnect providers on a SoC and the consumer may consume +multiple paths from different providers depending on use case and the +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. + +Optional properties: +interconnect-names : List of interconnect path name strings sorted in the same + order as the interconnects property. Consumers drivers will use + interconnect-names to match interconnect paths with interconnect + specifiers. + +Example: + + sdhci@7864000 { + ... + interconnects = <&pnoc MASTER_SDCC_1 &bimc SLAVE_EBI_CH0>; + interconnect-names = "ddr"; + };
WARNING: multiple messages have this Message-ID (diff)
From: georgi.djakov@linaro.org (Georgi Djakov) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v7 7/8] dt-bindings: Introduce interconnect consumers bindings Date: Tue, 31 Jul 2018 19:13:39 +0300 [thread overview] Message-ID: <20180731161340.13000-8-georgi.djakov@linaro.org> (raw) In-Reply-To: <20180731161340.13000-1-georgi.djakov@linaro.org> Add documentation for the interconnect consumer bindings, that will allow to link a device node (consumer) to its interconnect controller hardware. Tha aim is to enable drivers to request a framework API to configure an interconnect path by providing their struct device pointer and a name. Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> --- .../bindings/interconnect/interconnect.txt | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt index 6e2b2971b094..5cb7d3c8d44d 100644 --- a/Documentation/devicetree/bindings/interconnect/interconnect.txt +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt @@ -31,3 +31,30 @@ Example: clocks = <&rpmcc RPM_SMD_SNOC_CLK>, <&rpmcc RPM_SMD_SNOC_A_CLK>; }; + + += interconnect consumers = + +The interconnect consumers are device nodes which dynamically express their +bandwidth requirements along interconnect paths they are connected to. There +can be multiple interconnect providers on a SoC and the consumer may consume +multiple paths from different providers depending on use case and the +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. + +Optional properties: +interconnect-names : List of interconnect path name strings sorted in the same + order as the interconnects property. Consumers drivers will use + interconnect-names to match interconnect paths with interconnect + specifiers. + +Example: + + sdhci at 7864000 { + ... + interconnects = <&pnoc MASTER_SDCC_1 &bimc SLAVE_EBI_CH0>; + interconnect-names = "ddr"; + };
next prev parent reply other threads:[~2018-07-31 16:13 UTC|newest] Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-31 16:13 [PATCH v7 0/8] Introduce on-chip interconnect API Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-07-31 16:13 ` [PATCH v7 1/8] interconnect: Add generic " Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-02 0:05 ` Randy Dunlap 2018-08-02 0:05 ` Randy Dunlap 2018-08-02 11:58 ` Georgi Djakov 2018-08-02 11:58 ` Georgi Djakov 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-07-31 16:13 ` [PATCH v7 2/8] dt-bindings: Introduce interconnect provider bindings Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-02 21:02 ` Rob Herring 2018-08-02 21:02 ` Rob Herring 2018-08-07 14:54 ` Georgi Djakov 2018-08-07 14:54 ` [PATCH " Georgi Djakov 2018-08-07 14:54 ` Georgi Djakov 2018-08-20 15:32 ` [PATCH " Maxime Ripard 2018-08-20 15:32 ` Maxime Ripard 2018-08-20 15:32 ` Maxime Ripard 2018-08-24 14:51 ` Georgi Djakov 2018-08-24 14:51 ` Georgi Djakov 2018-08-24 14:51 ` Georgi Djakov 2018-08-24 15:35 ` Rob Herring 2018-08-24 15:35 ` Rob Herring 2018-08-24 15:35 ` Rob Herring 2018-08-27 15:11 ` Maxime Ripard 2018-08-27 15:11 ` Maxime Ripard 2018-08-27 15:11 ` Maxime Ripard 2018-08-29 12:33 ` Georgi Djakov 2018-08-29 12:33 ` Georgi Djakov 2018-08-29 12:33 ` Georgi Djakov 2018-08-30 7:47 ` Maxime Ripard 2018-08-30 7:47 ` Maxime Ripard 2018-08-30 7:47 ` Maxime Ripard 2018-08-27 15:08 ` Maxime Ripard 2018-08-27 15:08 ` Maxime Ripard 2018-08-27 15:08 ` Maxime Ripard 2018-08-29 12:31 ` Georgi Djakov 2018-08-29 12:31 ` Georgi Djakov 2018-08-29 12:31 ` Georgi Djakov 2018-07-31 16:13 ` [PATCH v7 3/8] interconnect: Add debugfs support Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-07-31 16:13 ` [PATCH v7 4/8] interconnect: qcom: Add RPM communication Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-07-31 16:13 ` [PATCH v7 5/8] dt-bindings: interconnect: Document qcom, msm8916 NoC bindings Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-07-31 16:13 ` [PATCH v7 5/8] dt-bindings: interconnect: Document qcom,msm8916 " Georgi Djakov 2018-07-31 16:13 ` [PATCH v7 6/8] interconnect: qcom: Add msm8916 interconnect provider driver Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-07-31 16:13 ` Georgi Djakov [this message] 2018-07-31 16:13 ` [PATCH v7 7/8] dt-bindings: Introduce interconnect consumers bindings Georgi Djakov 2018-07-31 16:13 ` [PATCH v7 8/8] interconnect: Allow endpoints translation via DT Georgi Djakov 2018-07-31 16:13 ` Georgi Djakov 2018-08-01 22:57 ` skannan 2018-08-01 22:57 ` skannan at codeaurora.org 2018-08-02 12:07 ` Georgi Djakov 2018-08-02 12:07 ` Georgi Djakov 2018-08-02 19:12 ` skannan 2018-08-02 19:12 ` skannan at codeaurora.org 2018-08-09 14:17 ` Georgi Djakov 2018-08-09 14:17 ` Georgi Djakov 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green 2018-08-03 22:59 ` Evan Green
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=20180731161340.13000-8-georgi.djakov@linaro.org \ --to=georgi.djakov@linaro.org \ --cc=abailon@baylibre.com \ --cc=amit.kucheria@linaro.org \ --cc=arnd@arndb.de \ --cc=bjorn.andersson@linaro.org \ --cc=daidavid1@codeaurora.org \ --cc=evgreen@chromium.org \ --cc=gregkh@linuxfoundation.org \ --cc=khilman@baylibre.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@arm.com \ --cc=mturquette@baylibre.com \ --cc=rjw@rjwysocki.net \ --cc=robh+dt@kernel.org \ --cc=seansw@qti.qualcomm.com \ --cc=skannan@codeaurora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.