From: Marek Vasut <marex@denx.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: linux-mips@linux-mips.org, Wills Wang <wills.wang@live.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Alban Bedel <albeu@free.fr>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
Paul Burton <paul.burton@imgtec.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC v5 01/15] WIP: clk: add Atheros AR933X SoCs clock driver
Date: Tue, 9 Feb 2016 12:05:36 +0100 [thread overview]
Message-ID: <201602091205.36276.marex@denx.de> (raw)
In-Reply-To: <1455005641-7079-2-git-send-email-antonynpavlov@gmail.com>
On Tuesday, February 09, 2016 at 09:13:47 AM, Antony Pavlov wrote:
> This driver can be easely upgraded for other Atheros
> SoCs (e.g. AR724X/AR913X) support.
>
Hi!
[...]
> +static unsigned long
> +ath79_pll_recalc_rate(struct clk_hw *hw, unsigned long parent_rate)
> +{
> + struct ath79_clk *ath79_clk = to_ath79_clk(hw);
> + struct ath79_cblk *cblk = ath79_clk->cblk;
> + const struct ath79_clk_info *clk_info =
> &cblk->clock_info[ath79_clk->idx]; + const struct ath79_pll_info
> *pll_info;
> + unsigned long rate;
> + unsigned long freq;
> + u32 clock_ctrl;
> + u32 cpu_config;
> + u32 t;
> +
> + BUG_ON(clk_info->type != ATH79_CLK_PLL);
> +
> + clock_ctrl = __raw_readl(cblk->base + AR933X_PLL_CLOCK_CTRL_REG);
> +
> + if (clock_ctrl & AR933X_PLL_CLOCK_CTRL_BYPASS) {
> + return parent_rate;
> + }
You can drop the {} here.
> + cpu_config = __raw_readl(cblk->base + AR933X_PLL_CPU_CONFIG_REG);
> +
> + t = (cpu_config >> AR933X_PLL_CPU_CONFIG_REFDIV_SHIFT) &
> + AR933X_PLL_CPU_CONFIG_REFDIV_MASK;
> + freq = parent_rate / t;
> +
> + t = (cpu_config >> AR933X_PLL_CPU_CONFIG_NINT_SHIFT) &
> + AR933X_PLL_CPU_CONFIG_NINT_MASK;
> + freq *= t;
> +
> + t = (cpu_config >> AR933X_PLL_CPU_CONFIG_OUTDIV_SHIFT) &
> + AR933X_PLL_CPU_CONFIG_OUTDIV_MASK;
> + if (t == 0)
> + t = 1;
> +
> + freq >>= t;
> +
> + pll_info = &clk_info->pll;
> +
> + t = ((clock_ctrl >> pll_info->div_shift) & pll_info->div_mask) + 1;
> + rate = freq / t;
> +
> + return rate;
> +}
[...]
> +static void __init ar9130_init(struct device_node *np)
> +{
> + int retval;
> + struct ath79_cblk *cblk;
> +
> + cblk = ath79_cblk_new(ar9331_clocks, ARRAY_SIZE(ar9331_clocks), np);
> + if (!cblk) {
> + pr_err("%s: failed to initialise clk block\n", __func__);
> + return;
> + }
> +
> + retval = ath79_cblk_register_clocks(cblk);
> + if (retval)
> + pr_err("%s: failed to register clocks\n", __func__);
> +}
> +CLK_OF_DECLARE(ar933x_clk, "qca,ar9330-pll", ar9130_init);
Is that ar9130_init name correct? Shouldn't it be ar9330_init ?
Looks good otherwise, thanks!
next prev parent reply other threads:[~2016-02-09 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455005641-7079-1-git-send-email-antonynpavlov@gmail.com>
2016-02-09 8:13 ` [RFC v5 01/15] WIP: clk: add Atheros AR933X SoCs clock driver Antony Pavlov
2016-02-09 11:05 ` Marek Vasut [this message]
2016-02-09 21:51 ` Alban
2016-02-11 12:50 ` Antony Pavlov
2016-02-12 2:21 ` Michael Turquette
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=201602091205.36276.marex@denx.de \
--to=marex@denx.de \
--cc=albeu@free.fr \
--cc=antonynpavlov@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mturquette@baylibre.com \
--cc=paul.burton@imgtec.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=wills.wang@live.com \
/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