From: Abhishek Sahu <absahu@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: "Banavathi, Pradeep" <pradeepb@codeaurora.org>,
andy.gross@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, mturquette@baylibre.com,
galak@codeaurora.org, mmcclint@codeaurora.org,
varada@codeaurora.org, sricharan@codeaurora.org,
architt@codeaurora.org, ntelkar@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/5] clk: qcom: ipq4019: Modified the fixed clock rate to proper values
Date: Fri, 3 Jun 2016 00:45:32 +0530 [thread overview]
Message-ID: <20160602191532.GA23619@chewinlnx07.qualcomm.com> (raw)
In-Reply-To: <20160602183540.GK28218@codeaurora.org>
On Thu, Jun 02, 2016 at 11:35:40AM -0700, Stephen Boyd wrote:
> On 06/02, Banavathi, Pradeep wrote:
> > The PLLs on IPQ4019 cannot be reconfigured by design. The
> > recommendation is to program these PLLS only once. Since, the
> > Bootloaders configure the PLLs and clocks already. we did not
> > support the recalc rate and marked them as fixed clocks.
> >
>
> (Please don't top post)
>
> That doesn't matter. We recalculate PLL rates on all other qcom
> SoCs by reading the hardware even though an overwhelming majority
> of them are fixed by the bootloader.
>
We will check for this. Already we added the APSS CPU PLL divider
in clock framework in next 3 patches of this patchset. Could you
please review the same so that we can follow the similar thing for
other PLL and dividers.
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-06-02 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 14:32 [PATCH 0/5] Patches for QCOM IPQ4019 clock driver Abhishek Sahu
2016-05-30 14:32 ` [PATCH 1/5] clk: qcom: ipq4019: Modified the fixed clock rate to proper values Abhishek Sahu
2016-06-01 22:18 ` Stephen Boyd
2016-06-02 14:18 ` Banavathi, Pradeep
2016-06-02 18:35 ` Stephen Boyd
2016-06-02 19:15 ` Abhishek Sahu [this message]
2016-05-30 14:32 ` [PATCH 2/5] clk: qcom: ipq4019: Added the apss cpu pll divider clock node Abhishek Sahu
2016-05-30 14:32 ` [PATCH 3/5] clk: qcom: ipq4019: Added the cpu pll divider and changed regmap limit Abhishek Sahu
2016-05-30 14:32 ` [PATCH 4/5] clk: qcom: ipq4019: Added the cpu clock frequency change notifier Abhishek Sahu
2016-05-30 14:32 ` [PATCH 5/5] clk: qcom: ipq4019: Added the turbo frequency for apps cpu Abhishek Sahu
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=20160602191532.GA23619@chewinlnx07.qualcomm.com \
--to=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mmcclint@codeaurora.org \
--cc=mturquette@baylibre.com \
--cc=ntelkar@codeaurora.org \
--cc=pawel.moll@arm.com \
--cc=pradeepb@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sricharan@codeaurora.org \
--cc=varada@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).