From: b.brezillon.dev@gmail.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: panic when the mck rate is zero
Date: Thu, 20 Mar 2014 17:34:09 +0100 [thread overview]
Message-ID: <532B1881.2050409@gmail.com> (raw)
In-Reply-To: <1395332062-4967-1-git-send-email-alexandre.belloni@free-electrons.com>
Le 20/03/2014 17:14, Alexandre Belloni a ?crit :
> If the mck rate is zero, we'll hit the following warning:
>
> WARNING: CPU: 0 PID: 0 at arch/arm/mach-at91/at91sam926x_time.c:257 at91sam926x_pit_init+0x13c/0x260()
>
> But the kernel will continue to try booting and face a lot of divisions by zero
> when trying to handle the various clocks.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> arch/arm/mach-at91/at91sam926x_time.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/mach-at91/at91sam926x_time.c b/arch/arm/mach-at91/at91sam926x_time.c
> index 0f04ffe9c5a8..f060f6371392 100644
> --- a/arch/arm/mach-at91/at91sam926x_time.c
> +++ b/arch/arm/mach-at91/at91sam926x_time.c
> @@ -250,6 +250,8 @@ void __init at91sam926x_pit_init(void)
> if (IS_ERR(mck))
> panic("AT91: PIT: Unable to get mck clk\n");
> pit_rate = clk_get_rate(mck) / 16;
> + if (pit_rate == 0)
> + panic("AT91: PIT: can't continue, mck rate is zero\n");
You're testing pit_rate why not printing:
"AT91: PIT: can't continue, *pit* rate is zero\n"
Otherwise,
Acked-by: Boris BREZILLON <b.brezillon.dev@gmail.com>
> pit_cycle = (pit_rate + HZ/2) / HZ;
> WARN_ON(((pit_cycle - 1) & ~AT91_PIT_PIV) != 0);
>
next prev parent reply other threads:[~2014-03-20 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 16:14 [PATCH] ARM: at91: panic when the mck rate is zero Alexandre Belloni
2014-03-20 16:34 ` Boris BREZILLON [this message]
2014-03-20 16:40 ` Alexandre Belloni
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=532B1881.2050409@gmail.com \
--to=b.brezillon.dev@gmail.com \
--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).