From: ppvk@codeaurora.org
To: Matthias Kaehlcke <mka@chromium.org>
Cc: bjorn.andersson@linaro.org, adrian.hunter@intel.com,
robh+dt@kernel.org, ulf.hansson@linaro.org,
vbadigan@codeaurora.org, sboyd@kernel.org,
georgi.djakov@linaro.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-mmc-owner@vger.kernel.org,
rnayak@codeaurora.org, sibis@codeaurora.org,
matthias@chromium.org
Subject: Re: [PATCH V4 1/2] mmc: sdhci-msm: Add interconnect bandwidth scaling support
Date: Tue, 16 Jun 2020 18:37:53 +0530 [thread overview]
Message-ID: <3681c3e2a49b5c8b832d277873b6fa49@codeaurora.org> (raw)
In-Reply-To: <20200615231207.GX4525@google.com>
Hi Matthias,
Thanks!
On 2020-06-16 04:42, Matthias Kaehlcke wrote:
> On Tue, Jun 09, 2020 at 02:07:25PM +0530, Pradeep P V K wrote:
>> Interconnect bandwidth scaling support is now added as a
>> part of OPP. So, make sure interconnect driver is ready
>> before handling interconnect scaling.
>>
>> Signed-off-by: Pradeep P V K <ppvk@codeaurora.org>
>> Reviewed-by: Sibi Sankar <sibis@codeaurora.org>
>
> Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
>
> Do you plan to send also patches that add the necessary DT entries?
> I'm particularly interested in SC7180.
Yes, we will send the DT entries soon.
next prev parent reply other threads:[~2020-06-16 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 8:37 [PATCH V4 0/2] Add SDHC interconnect bandwidth scaling Pradeep P V K
2020-06-09 8:37 ` [PATCH V4 1/2] mmc: sdhci-msm: Add interconnect bandwidth scaling support Pradeep P V K
2020-06-15 23:12 ` Matthias Kaehlcke
2020-06-16 13:07 ` ppvk [this message]
2020-06-16 11:32 ` Ulf Hansson
2020-06-09 8:37 ` [PATCH V4 2/2] dt-bindings: mmc: sdhci-msm: Add interconnect BW scaling strings Pradeep P V K
2020-06-16 11:32 ` Ulf Hansson
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=3681c3e2a49b5c8b832d277873b6fa49@codeaurora.org \
--to=ppvk@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=bjorn.andersson@linaro.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=matthias@chromium.org \
--cc=mka@chromium.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sibis@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).