From: Rajendra Nayak <rnayak@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: bjorn.andersson@linaro.org, agross@kernel.org,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
mka@chromium.org, Alok Chauhan <alokc@codeaurora.org>,
Akash Asthana <akashast@codeaurora.org>
Subject: Re: [PATCH 1/3] spi: spi-qcom-qspi: Use OPP API to set clk/perf state
Date: Tue, 7 Jul 2020 09:57:29 +0530 [thread overview]
Message-ID: <c49404d6-d9e1-2d19-92f4-0b2e1e2187a8@codeaurora.org> (raw)
In-Reply-To: <20200703170157.GA54804@sirena.org.uk>
On 7/3/2020 10:31 PM, Mark Brown wrote:
> On Fri, Jul 03, 2020 at 03:11:31PM +0530, Rajendra Nayak wrote:
>> QSPI needs to vote on a performance state of a power domain depending on
>> the clock rate. Add support for it by specifying the perf state/clock rate
>> as an OPP table in device tree.
>
> This doesn't apply against current code, please check and resend.
Hey Mark, as mentioned in the cover letter I wanted this to land via the
qcom tree, since Bjorn already has a patch in his tree which would otherwise
conflict with this change, if you were to pull this.
Hence I had this rebased on qcom for-next and requested Bjorn to pull it in,
with your ACK. Hope thats fine with you.
thanks,
Rajendra
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-07-07 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 9:41 [PATCH 0/3] QSPI: Add DVFS support Rajendra Nayak
2020-07-03 9:41 ` [PATCH 1/3] spi: spi-qcom-qspi: Use OPP API to set clk/perf state Rajendra Nayak
2020-07-03 17:01 ` Mark Brown
2020-07-07 4:27 ` Rajendra Nayak [this message]
2020-07-03 9:41 ` [PATCH 2/3] arm64: dts: sdm845: Add qspi opps and power-domains Rajendra Nayak
2020-07-06 15:56 ` Matthias Kaehlcke
2020-07-03 9:41 ` [PATCH 3/3] arm64: dts: sc7180: " Rajendra Nayak
2020-07-06 15:58 ` Matthias Kaehlcke
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=c49404d6-d9e1-2d19-92f4-0b2e1e2187a8@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=agross@kernel.org \
--cc=akashast@codeaurora.org \
--cc=alokc@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mka@chromium.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).