From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: at91: fix num_parents test in at91sam9260 slow clk implementation
Date: Tue, 02 Sep 2014 14:45:06 -0700 [thread overview]
Message-ID: <20140902214506.5251.1412@quantum> (raw)
In-Reply-To: <1409671671-13544-1-git-send-email-boris.brezillon@free-electrons.com>
Quoting Boris BREZILLON (2014-09-02 08:27:51)
> The slow clk block provided by at91sam9260 and derived SoCs should always
> have 2 parents.
>
> Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> ---
>
> Hello Mike,
>
> Could you take this fix for the next 3.17 rc ?
> Without this fix you won't be able to use programmable clks (the slow
> clk is one of the parents of prog clks), and these prog clks are used,
> among other things, to provide clks to external audio chips.
>
> No need to backport this fix to previous stable releases, as CCF support
> for at91sam9260 (and derived) SoCs only appeared in 3.17.
Pulled into clk-fixes.
Regards,
Mike
>
> Best Regards,
>
> Boris
>
> drivers/clk/at91/clk-slow.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/at91/clk-slow.c b/drivers/clk/at91/clk-slow.c
> index 0300c46..32f7c1b 100644
> --- a/drivers/clk/at91/clk-slow.c
> +++ b/drivers/clk/at91/clk-slow.c
> @@ -447,7 +447,7 @@ void __init of_at91sam9260_clk_slow_setup(struct device_node *np,
> int i;
>
> num_parents = of_count_phandle_with_args(np, "clocks", "#clock-cells");
> - if (num_parents <= 0 || num_parents > 1)
> + if (num_parents != 2)
> return;
>
> for (i = 0; i < num_parents; ++i) {
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-09-02 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 15:27 [PATCH] clk: at91: fix num_parents test in at91sam9260 slow clk implementation Boris BREZILLON
2014-09-02 21:45 ` Mike Turquette [this message]
2014-09-03 7:42 ` Boris BREZILLON
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=20140902214506.5251.1412@quantum \
--to=mturquette@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).