From: icenowy@aosc.io
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] clk: sunxi-ng: add mux and pll notifiers for A64 CPU clock
Date: Thu, 28 Sep 2017 18:42:39 +0800 [thread overview]
Message-ID: <975c0c884d9a83faad6141df474a93af@aosc.io> (raw)
In-Reply-To: <20170928102752.ceo54qccqakb4xyx@flea>
在 2017-09-28 18:27,Maxime Ripard 写道:
> Hi,
>
> On Sat, Sep 23, 2017 at 12:15:29AM +0000, Icenowy Zheng wrote:
>> The A64 PLL_CPU clock has the same instability if some factor changed
>> without the PLL gated like other SoCs with sun6i-style CCU, e.g. A33,
>> H3.
>>
>> Add the mux and pll notifiers for A64 CPU clock to workaround the
>> problem.
>>
>> Fixes: c6a0637460c2 ("clk: sunxi-ng: Add A64 clocks")
>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
>> ---
>> drivers/clk/sunxi-ng/ccu-sun50i-a64.c | 28
>> +++++++++++++++++++++++++++-
>> 1 file changed, 27 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/clk/sunxi-ng/ccu-sun50i-a64.c
>> b/drivers/clk/sunxi-ng/ccu-sun50i-a64.c
>> index 2bb4cabf802f..b55fa69dd0c1 100644
>> --- a/drivers/clk/sunxi-ng/ccu-sun50i-a64.c
>> +++ b/drivers/clk/sunxi-ng/ccu-sun50i-a64.c
>> @@ -879,11 +879,26 @@ static const struct sunxi_ccu_desc
>> sun50i_a64_ccu_desc = {
>> .num_resets = ARRAY_SIZE(sun50i_a64_ccu_resets),
>> };
>>
>> +static struct ccu_pll_nb sun50i_a64_pll_cpu_nb = {
>> + .common = &pll_cpux_clk.common,
>> + /* copy from pll_cpux_clk */
>> + .enable = BIT(31),
>> + .lock = BIT(28),
>> +};
>> +
>> +static struct ccu_mux_nb sun50i_a64_cpu_nb = {
>> + .common = &cpux_clk.common,
>> + .cm = &cpux_clk.mux,
>> + .delay_us = 1, /* > 8 clock cycles at 24 MHz */
>> + .bypass_index = 1, /* index of 24 MHz oscillator */
>> +};
>> +
>>
>> static int sun50i_a64_ccu_probe(struct platform_device *pdev)
>> {
>> struct resource *res;
>> void __iomem *reg;
>> u32 val;
>> + int ret;
>>
>> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> reg = devm_ioremap_resource(&pdev->dev, res);
>> @@ -897,7 +912,18 @@ static int sun50i_a64_ccu_probe(struct
>> platform_device *pdev)
>>
>> writel(0x515, reg + SUN50I_A64_PLL_MIPI_REG);
>>
>> - return sunxi_ccu_probe(pdev->dev.of_node, reg,
>> &sun50i_a64_ccu_desc);
>> + ret = sunxi_ccu_probe(pdev->dev.of_node, reg, &sun50i_a64_ccu_desc);
>> + if (ret)
>> + return ret;
>> +
>> + /* Gate then ungate PLL CPU after any rate changes */
>> + ccu_pll_notifier_register(&sun50i_a64_pll_cpu_nb);
>> +
>> + /* Reparent CPU during PLL CPU rate changes */
>> + ccu_mux_notifier_register(pll_cpux_clk.common.hw.clk,
>> + &sun50i_a64_cpu_nb);
>> +
>> + return 0;
>
> So this is the fourth user of the exact same code, can you turn that
> into a shared function?
I think it's not so worthful to extract the code, as:
- the notifier structs contains info of the clocks
- A31 seems not to need the PLL notifier.
>
> Thanks!
> Maxime
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-09-28 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 0:15 [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC Icenowy Zheng
2017-09-23 0:15 ` [PATCH 1/3] clk: sunxi-ng: add mux and pll notifiers for A64 CPU clock Icenowy Zheng
2017-09-28 10:27 ` Maxime Ripard
2017-09-28 10:42 ` icenowy [this message]
2017-09-28 14:20 ` Maxime Ripard
2017-09-28 14:24 ` icenowy
2017-09-28 14:31 ` Maxime Ripard
2017-09-23 0:15 ` [PATCH 2/3] arm64: allwinner: a64: add CPU opp table Icenowy Zheng
2017-09-25 17:38 ` [linux-sunxi] " Samuel Holland
2017-09-23 0:15 ` [PATCH 3/3] arm64: allwinner: a64: set CPU regulator for Pine64 Icenowy Zheng
2017-09-25 10:10 ` [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC Maxime Ripard
2017-09-25 10:12 ` Icenowy Zheng
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:29 ` [linux-sunxi] " Icenowy Zheng
2017-09-25 10:43 ` Maxime Ripard
2017-09-27 11:51 ` icenowy
2017-09-28 10:28 ` Maxime Ripard
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=975c0c884d9a83faad6141df474a93af@aosc.io \
--to=icenowy@aosc.io \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.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