From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>, Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: gcc-qcs404: Use floor ops for sdcc clks
Date: Mon, 9 Sep 2019 13:18:39 +0530 [thread overview]
Message-ID: <adaad84a-15ce-3212-9fec-7ff387da2a88@codeaurora.org> (raw)
In-Reply-To: <20190906203827.A2259208C3@mail.kernel.org>
Hi Stephen, Vinod,
On 9/7/2019 2:08 AM, Stephen Boyd wrote:
> Quoting Vinod Koul (2019-09-05 21:56:59)
>> Update the gcc qcs404 clock driver to use floor ops for sdcc clocks. As
>> disuccsed in [1] it is good idea to use floor ops for sdcc clocks as we
>> dont want the clock rates to do round up.
>>
>> [1]: https://lore.kernel.org/linux-arm-msm/20190830195142.103564-1-swboyd@chromium.org/
>>
>> Signed-off-by: Vinod Koul <vkoul@kernel.org>
>> ---
>
> Is Taniya writing the rest? Please don't dribble it out over the next
> few weeks!
I have pushed the patch : https://patchwork.kernel.org/patch/11137393/
Vinod, I have taken care of the QCS404 in the same patch, so as to keep
the change in one patch.
>
>> drivers/clk/qcom/gcc-qcs404.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
--
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:[~2019-09-09 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 4:56 [PATCH] clk: qcom: gcc-qcs404: Use floor ops for sdcc clks Vinod Koul
2019-09-06 19:55 ` Bjorn Andersson
2019-09-06 20:38 ` Stephen Boyd
2019-09-07 7:48 ` Vinod Koul
2019-09-09 7:48 ` Taniya Das [this message]
2019-09-09 10:24 ` Stephen Boyd
2019-09-09 10:25 ` Stephen Boyd
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=adaad84a-15ce-3212-9fec-7ff387da2a88@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=vkoul@kernel.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).