From: Matthias Kaehlcke <mka@chromium.org>
To: Pradeep P V K <ppvk@codeaurora.org>
Cc: adrian.hunter@intel.com, georgi.djakov@linaro.org,
robh+dt@kernel.org, ulf.hansson@linaro.org,
asutoshd@codeaurora.org, vbadigan@codeaurora.org,
stummala@codeaurora.org, sayalil@codeaurora.org,
rampraka@codeaurora.org, sboyd@kernel.org,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
agross@kernel.org, linux-mmc-owner@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [RFC-v2 0/2] Add Support for SDHC bus bandwidth voting
Date: Thu, 30 Jan 2020 13:38:12 -0800 [thread overview]
Message-ID: <20200130213812.GK71044@google.com> (raw)
In-Reply-To: <1573220319-4287-1-git-send-email-ppvk@codeaurora.org>
Hi Pradeep,
what is the status of this series, do you plan to send v3 soon or
is it abandonded?
Thanks
Matthias
On Fri, Nov 08, 2019 at 07:08:37PM +0530, Pradeep P V K wrote:
> Vote for the MSM bus bandwidth required by SDHC driver
> based on the clock speed and bus width of the card.
> Otherwise, the system clocks may run at minimum clock
> speed and thus affecting the performance.
>
> Adapt to the new ICB framework for bus bandwidth voting.
>
> This requires the source/destination port ids.
> Also this requires a tuple of values.
>
> The tuple is for two different paths - from SDHC master
> to BIMC slave. The other is from CPU master to SDHC slave.
> This tuple consists of the average and peak bandwidth.
>
> This change is based on Georgi Djakov [RFC]
> (https://lkml.org/lkml/2018/10/11/499)
>
> ---
> changed since v1:
> * Addressed all the Review comments.
> * Minor code rebasing.
>
> Pradeep P V K (2):
> dt-bindings: mmc: sdhci-msm: Add Bus BW vote supported strings
> mmc: sdhci-msm: Add support for bus bandwidth voting
>
> .../devicetree/bindings/mmc/sdhci-msm.txt | 32 ++
> drivers/mmc/host/sdhci-msm.c | 366 ++++++++++++++++++++-
> 2 files changed, 395 insertions(+), 3 deletions(-)
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2020-01-30 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 13:38 [RFC-v2 0/2] Add Support for SDHC bus bandwidth voting Pradeep P V K
2019-11-08 13:38 ` [RFC-v2 1/2] dt-bindings: mmc: sdhci-msm: Add Bus BW vote supported strings Pradeep P V K
2019-11-13 13:16 ` Georgi Djakov
2019-12-09 14:41 ` ppvk
2019-11-08 13:38 ` [RFC-v2 2/2] mmc: sdhci-msm: Add support for bus bandwidth voting Pradeep P V K
2020-04-03 17:04 ` Doug Anderson
2020-04-08 12:58 ` ppvk
2020-04-08 14:34 ` Doug Anderson
2020-01-30 21:38 ` Matthias Kaehlcke [this message]
2020-02-03 7:20 ` [RFC-v2 0/2] Add Support for SDHC " 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=20200130213812.GK71044@google.com \
--to=mka@chromium.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=asutoshd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc-owner@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ppvk@codeaurora.org \
--cc=rampraka@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sayalil@codeaurora.org \
--cc=sboyd@kernel.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).