From: Pradeep P V K <ppvk@codeaurora.org>
To: adrian.hunter@intel.com, robh+dt@kernel.org,
ulf.hansson@linaro.org, asutoshd@codeaurora.org,
stummala@codeaurora.org, sayalil@codeaurora.org,
rampraka@codeaurora.org, vbadigan@codeaurora.org,
sboyd@kernel.org, georgi.djakov@linaro.org
Cc: 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,
mka@chromium.org, Pradeep P V K <ppvk@codeaurora.org>
Subject: [RFC v3 0/2] Add SDHC interconnect bandwidth scaling
Date: Fri, 7 Feb 2020 20:14:53 +0530 [thread overview]
Message-ID: <1581086695-16645-1-git-send-email-ppvk@codeaurora.org> (raw)
Add interconnect bandwidths for SDHC driver using OPP framework that
is required by SDHC driver based on the clock frequency and bus width
of the card. Otherwise, the system clocks may run at minimum clock
speed and thus affecting the performance.
This change is based on Georgi Djakov [RFC]
(https://lkml.org/lkml/2018/10/11/499) and
Saravana Kannan [PATCH v6]
(https://lkml.org/lkml/2019/12/6/740)
change from RFC v2 -> v3 changes:
- Modified interconnect bandwidth support using OPP framework.
- Addressed review comments on v2.
Pradeep P V K (2):
mmc: sdhci-msm: Add interconnect bus bandwidth scaling support
dt-bindings: mmc: sdhci-msm: Add interconnect BW scaling strings
.../devicetree/bindings/mmc/sdhci-msm.txt | 18 ++
drivers/mmc/host/sdhci-msm.c | 251 ++++++++++++++++++++-
2 files changed, 265 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2020-02-07 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 14:44 Pradeep P V K [this message]
2020-02-07 14:44 ` [RFC v3 1/2] mmc: sdhci-msm: Add interconnect bus bandwidth scaling support Pradeep P V K
2020-02-08 0:42 ` Matthias Kaehlcke
2020-02-12 15:10 ` ppvk
2020-02-08 23:39 ` Bjorn Andersson
2020-02-18 11:11 ` ppvk
2020-02-07 14:44 ` [RFC v3 2/2] dt-bindings: mmc: sdhci-msm: Add interconnect BW scaling strings Pradeep P V K
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=1581086695-16645-1-git-send-email-ppvk@codeaurora.org \
--to=ppvk@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=asutoshd@codeaurora.org \
--cc=devicetree@vger.kernel.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=mka@chromium.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).