From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] ARM: shmobile: r8a73a4: safeguard against wrong clk_set_rate() uses
Date: Thu, 27 Jun 2013 07:16:52 +0000 [thread overview]
Message-ID: <20130627071652.GC25014@verge.net.au> (raw)
In-Reply-To: <1371798638-10530-2-git-send-email-g.liakhovetski@gmx.de>
On Fri, Jun 21, 2013 at 09:10:35AM +0200, Guennadi Liakhovetski wrote:
> clk_set_rate() should only be called with exact rates, returned by
> clk_round_rate(). However, it is still good to verify, that the value,
> passed to clock's .set_rate() method is at least valid. This patch adds
> such a check for the Z-clock on r8a73a4.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Thanks, I have queued this up for v3.12 in the soc branch.
> ---
> arch/arm/mach-shmobile/clock-r8a73a4.c | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-shmobile/clock-r8a73a4.c b/arch/arm/mach-shmobile/clock-r8a73a4.c
> index eb42740..cbf9852 100644
> --- a/arch/arm/mach-shmobile/clock-r8a73a4.c
> +++ b/arch/arm/mach-shmobile/clock-r8a73a4.c
> @@ -225,16 +225,28 @@ static int zclk_set_rate(struct clk *clk, unsigned long rate)
> goto done;
> }
>
> - frqcrc = clk->mapped_reg + (FRQCRC - (u32)clk->enable_reg);
> + /*
> + * Users are supposed to first call clk_set_rate() only with
> + * clk_round_rate() results. So, we don't fix wrong rates here, but
> + * guard against them anyway
> + */
>
> p_rate = clk_get_rate(clk->parent);
> if (rate = p_rate) {
> val = 0;
> } else {
> step = DIV_ROUND_CLOSEST(p_rate, 32);
> +
> + if (rate > p_rate || rate < step) {
> + ret = -EINVAL;
> + goto done;
> + }
> +
> val = 32 - rate / step;
> }
>
> + frqcrc = clk->mapped_reg + (FRQCRC - (u32)clk->enable_reg);
> +
> iowrite32((ioread32(frqcrc) & ~(clk->div_mask << clk->enable_bit)) |
> (val << clk->enable_bit), frqcrc);
>
> --
> 1.7.2.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-06-27 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 7:10 [PATCH 0/4] Add DVFS support on APE6EVM Guennadi Liakhovetski
2013-06-21 7:10 ` [PATCH 1/4] ARM: shmobile: r8a73a4: safeguard against wrong clk_set_rate() uses Guennadi Liakhovetski
2013-06-27 7:16 ` Simon Horman [this message]
2013-06-21 7:10 ` [PATCH 2/4] ARM: shmobile: r8a73a4: add I2C DT nodes and required clocks Guennadi Liakhovetski
2013-06-27 7:19 ` Simon Horman
2013-06-21 7:10 ` [PATCH 3/4] ARM: shmobile: ape6evm: add CPUFreq support Guennadi Liakhovetski
2013-06-21 7:10 ` [PATCH 4/4] ARM: shmobile: r8a73a4: add Z2 clock support Guennadi Liakhovetski
2013-06-27 7:16 ` Simon Horman
2013-06-27 4:45 ` [PATCH 0/4] Add DVFS support on APE6EVM Simon Horman
2013-06-27 5:29 ` Kuninori Morimoto
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=20130627071652.GC25014@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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