From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] irqchip: atmel-aic: Add irq RTC fixups
Date: Thu, 10 Jul 2014 20:32:49 +0200 [thread overview]
Message-ID: <20140710203249.23dd6444@bbrezillon> (raw)
In-Reply-To: <1405016741-2407-1-git-send-email-boris.brezillon@free-electrons.com>
On Thu, 10 Jul 2014 20:25:38 +0200
Boris BREZILLON <boris.brezillon@free-electrons.com> wrote:
> Hello,
>
> This patch series introduce the notion of irq fixups for atmel SoCs.
>
> In most at91 SoCs the first interrupt line is shared by several IPs, and
> some of these HW blocks might be in an unknown state when booting the
> Linux kernel.
> Hence these IPs might generate spurious interrupts if they've not masked
> their irqs and the shared irq line is requested by another peripheral.
>
> These fixups were previously done in arch/arm/mach-at91/sysirq_mask.c
> but as we're trying to use standard implementation (IRQCHIP_DECLARE and
> automatic call of irqchip_init within arch/arm/kernel/irq.c) we need to
> do those fixups in the irqchip driver.
This is what I was talking about:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/271425.htm
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-10 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 18:25 [PATCH 0/3] irqchip: atmel-aic: Add irq RTC fixups Boris BREZILLON
2014-07-10 18:25 ` [PATCH 1/3] irqchip: atmel-aic: Add irq fixup infrastructure Boris BREZILLON
2014-07-10 18:25 ` [PATCH 2/3] irqchip: atmel-aic: Implement RTC irq fixup Boris BREZILLON
2014-07-10 18:25 ` [PATCH 3/3] irqchip: atmel-aic: Define irq fixups for atmel SoCs Boris BREZILLON
2014-07-10 18:32 ` Boris BREZILLON [this message]
2014-07-10 18:36 ` [PATCH 0/3] irqchip: atmel-aic: Add irq RTC fixups Boris BREZILLON
2014-07-17 13:39 ` Jason Cooper
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=20140710203249.23dd6444@bbrezillon \
--to=boris.brezillon@free-electrons.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).