From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v4] ARM: at91: fix at91_sysirq_mask_rtc for sam9x5 SoCs
Date: Fri, 9 May 2014 16:51:25 +0200 [thread overview]
Message-ID: <20140509145125.GD6776@localhost> (raw)
In-Reply-To: <1399646610-18816-1-git-send-email-boris.brezillon@free-electrons.com>
On Fri, May 09, 2014 at 04:43:30PM +0200, Boris BREZILLON wrote:
> sam9x5 SoCs have the following errata:
> "RTC: Interrupt Mask Register cannot be used
> Interrupt Mask Register read always returns 0."
>
> Hence we should not rely on what IMR claims about already masked IRQs
> and just disable all IRQs.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: <stable@vger.kernel.org> # v3.10+
> Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Reviewed-by: Johan Hovold <jhovold@gmail.com>
Looks good, but for the future: Why do you break the comment lines you
added at column 60?
Thanks,
Johan
> ---
> Hello,
>
> Again, sorry for the noise, but I forgot to add Nicolas' ack and to keep
> Andrew and the stable ML in cc.
>
> Best Regards,
>
> Boris
>
> Changes since v3:
> - fix commit message and comment
> Changes since v2:
> - removed unused variable 'mask'
> Changes since v1:
> - use a macro to define IRQs bitmask
> - read IMR register to ensure the write to IDR has been flushed
> - quote atmel's datasheet errata in commit message
> - comment the code to describe why we're not using IMR to disable
> the interrupts
>
> arch/arm/mach-at91/sysirq_mask.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm/mach-at91/sysirq_mask.c b/arch/arm/mach-at91/sysirq_mask.c
> index 2ba694f..f8bc351 100644
> --- a/arch/arm/mach-at91/sysirq_mask.c
> +++ b/arch/arm/mach-at91/sysirq_mask.c
> @@ -25,24 +25,28 @@
>
> #include "generic.h"
>
> -#define AT91_RTC_IDR 0x24 /* Interrupt Disable Register */
> -#define AT91_RTC_IMR 0x28 /* Interrupt Mask Register */
> +#define AT91_RTC_IDR 0x24 /* Interrupt Disable Register */
> +#define AT91_RTC_IMR 0x28 /* Interrupt Mask Register */
> +#define AT91_RTC_IRQ_MASK 0x1f /* Available IRQs mask */
>
> void __init at91_sysirq_mask_rtc(u32 rtc_base)
> {
> void __iomem *base;
> - u32 mask;
>
> base = ioremap(rtc_base, 64);
> if (!base)
> return;
>
> - mask = readl_relaxed(base + AT91_RTC_IMR);
> - if (mask) {
> - pr_info("AT91: Disabling rtc irq\n");
> - writel_relaxed(mask, base + AT91_RTC_IDR);
> - (void)readl_relaxed(base + AT91_RTC_IMR); /* flush */
> - }
> + /*
> + * sam9x5 SoCs have the following errata:
> + * "RTC: Interrupt Mask Register cannot be used
> + * Interrupt Mask Register read always returns 0."
> + *
> + * Hence we're not relying on IMR values to disable
> + * interrupts.
> + */
> + writel_relaxed(AT91_RTC_IRQ_MASK, base + AT91_RTC_IDR);
> + (void)readl_relaxed(base + AT91_RTC_IMR); /* flush */
>
> iounmap(base);
> }
next prev parent reply other threads:[~2014-05-09 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 14:43 [RESEND PATCH v4] ARM: at91: fix at91_sysirq_mask_rtc for sam9x5 SoCs Boris BREZILLON
2014-05-09 14:51 ` Johan Hovold [this message]
2014-05-09 15:00 ` 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=20140509145125.GD6776@localhost \
--to=jhovold@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).