From: <Nicolas.Ferre@microchip.com>
To: <alexandre.belloni@bootlin.com>, <sboyd@kernel.org>
Cc: <mturquette@baylibre.com>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: at91: fix at91sam9x5 peripheral clock number
Date: Wed, 20 Feb 2019 11:18:40 +0000 [thread overview]
Message-ID: <23696765-c2c7-0df8-1bfd-2dfd96f65e9d@microchip.com> (raw)
In-Reply-To: <20190219165114.2366-1-alexandre.belloni@bootlin.com>
On 19/02/2019 at 17:51, Alexandre Belloni wrote:
> nck() looks at the last id in an array and unfortunately,
> at91sam9x35_periphck has a sentinel, hence the id is 0 and the calculated
> number of peripheral clocks is 1 instead of a maximum of 31.
>
> Fixes: 1eabdc2f9dd8 ("clk: at91: add at91sam9x5 PMCs driver")
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: <stable@vger.kernel.org> # v4.20+
It would be nice to queue it as a fix the soonest, as it impacts 5.0 but
not 4.20 due to a switch from one DT binding to another (read: a real
regression)... But I know it's a bit late in the cycle...
Regards,
Nicolas
> ---
> drivers/clk/at91/at91sam9x5.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/clk/at91/at91sam9x5.c b/drivers/clk/at91/at91sam9x5.c
> index 2fe225a697df..d37e7ed9eb90 100644
> --- a/drivers/clk/at91/at91sam9x5.c
> +++ b/drivers/clk/at91/at91sam9x5.c
> @@ -144,8 +144,7 @@ static void __init at91sam9x5_pmc_setup(struct device_node *np,
> return;
>
> at91sam9x5_pmc = pmc_data_allocate(PMC_MAIN + 1,
> - nck(at91sam9x5_systemck),
> - nck(at91sam9x35_periphck), 0);
> + nck(at91sam9x5_systemck), 31, 0);
> if (!at91sam9x5_pmc)
> return;
>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2019-02-20 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 16:51 [PATCH] clk: at91: fix at91sam9x5 peripheral clock number Alexandre Belloni
2019-02-20 10:20 ` Nicolas.Ferre
2019-02-20 10:29 ` Alexandre Belloni
2019-02-20 10:48 ` Nicolas.Ferre
2019-02-20 11:18 ` Nicolas.Ferre [this message]
2019-02-20 19:39 ` Stephen Boyd
2019-02-20 19:39 ` Stephen Boyd
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=23696765-c2c7-0df8-1bfd-2dfd96f65e9d@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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