From: Rob Herring <robh@kernel.org>
To: Pradeep P V K <ppvk@codeaurora.org>
Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org,
asutoshd@codeaurora.org, vbadigan@codeaurora.org,
stummala@codeaurora.org, sayalil@codeaurora.org,
rampraka@codeaurora.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [RFC 2/2] dt-bindings: mmc: sdhci-msm: Add Bus BW vote supported strings
Date: Fri, 13 Sep 2019 15:36:11 +0100 [thread overview]
Message-ID: <5d7ba95c.1c69fb81.edf8e.6556@mx.google.com> (raw)
In-Reply-To: <1567774037-2344-3-git-send-email-ppvk@codeaurora.org>
On Fri, Sep 06, 2019 at 06:17:17PM +0530, Pradeep P V K wrote:
> Add Bus bandwidth voting supported strings for qcom-sdhci controller.
What is bus bandwidth voting?
>
> Signed-off-by: Pradeep P V K <ppvk@codeaurora.org>
> ---
> .../devicetree/bindings/mmc/sdhci-msm.txt | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
> index da4edb1..8255d92 100644
> --- a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
> +++ b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
> @@ -39,6 +39,25 @@ Required properties:
> "cal" - reference clock for RCLK delay calibration (optional)
> "sleep" - sleep clock for RCLK delay calibration (optional)
>
> +Optional Properties:
> +* Following bus parameters are required for bus bw voting:
> +- interconnects: Pairs of phandles and interconnect provider specifier
> + to denote the edge source and destination ports of
> + the interconnect path. Please refer to
> + Documentation/devicetree/bindings/interconnect/
> + for more details.
> +- 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. Please refer to Documentation/devicetree/bindings/
> + interconnect/ for more details.
How many? What are the strings?
> +- qcom,msm-bus,name: string describing the bus path
> +- qcom,msm-bus,num-cases: number of configurations in which sdhc can operate in
> +- qcom,msm-bus,num-paths: number of paths to vote for
> +- qcom,msm-bus,vectors-KBps: Takes a tuple <ib ab>, <ib ab> (2 tuples for 2
ib and ab are what? Didn't we just add interconnect bindings for
expressing bandwidth?
> + num-paths) The number of these entries *must*
> + be same as num-cases.
Are all these properties SDHCI specific or can we expect to get these
for *all* the QCom blocks?
> +
> Example:
>
> sdhc_1: sdhci@f9824900 {
> @@ -56,6 +75,19 @@ Example:
>
> clocks = <&gcc GCC_SDCC1_APPS_CLK>, <&gcc GCC_SDCC1_AHB_CLK>;
> clock-names = "core", "iface";
> + interconnects = <&qnoc 50 &qnoc 512>,
> + <&qnoc 1 &qnoc 544>;
> + interconnect-names = "sdhc-ddr","cpu-sdhc";
> + qcom,msm-bus,name = "sdhc1";
> + qcom,msm-bus,num-cases = <3>;
> + qcom,msm-bus,num-paths = <2>;
> + qcom,msm-bus,vectors-KBps =
> + /* No Vote */
> + <0 0>, <0 0>,
> + /* 50 MB/s */
> + <130718 200000>, <133320 133320>,
> + /* 200 MB/s */
> + <1338562 4096000>, <1338562 4096000>;
> };
>
> sdhc_2: sdhci@f98a4900 {
> --
> 1.9.1
>
next prev parent reply other threads:[~2019-09-13 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 12:47 [RFC 0/2] Add Support for SDHC bus bandwidth voting Pradeep P V K
2019-09-06 12:47 ` [RFC 1/2] mmc: sdhci-msm: Add support for " Pradeep P V K
2019-09-06 12:51 ` ppvk
2019-09-06 21:02 ` Stephen Boyd
2019-09-12 15:01 ` ppvk
2019-09-12 12:56 ` Georgi Djakov
2019-09-25 6:24 ` ppvk
2019-09-12 16:45 ` Bjorn Andersson
2019-09-25 11:27 ` ppvk
2019-10-03 10:00 ` Ulf Hansson
2019-09-06 12:47 ` [RFC 2/2] dt-bindings: mmc: sdhci-msm: Add Bus BW vote supported strings Pradeep P V K
2019-09-13 14:36 ` Rob Herring [this message]
2019-09-30 14:32 ` ppvk
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=5d7ba95c.1c69fb81.edf8e.6556@mx.google.com \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ppvk@codeaurora.org \
--cc=rampraka@codeaurora.org \
--cc=sayalil@codeaurora.org \
--cc=stummala@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=vbadigan@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).