From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang
Date: Wed, 2 Oct 2013 15:48:21 +0200 [thread overview]
Message-ID: <20131002154821.385e0921@skate> (raw)
In-Reply-To: <524C1C34.5050403@keymile.com>
Dear Gerlando Falauto,
On Wed, 02 Oct 2013 15:14:28 +0200, Gerlando Falauto wrote:
> > Hum? The driver you're touching is a GPIO driver, while
> > drivers/irqchip/irq-orion.c is an interrupt controller driver. The
> > gpio-mvebu driver can be used on all mvebu platforms that are DT
> > capable, but the main interrupt controller is different from one
> > platform to another: we already have irq-armada-370-xp.c for Armada
> > 370/XP, while Sebastian's irq-orion.c is for older families of SoCs.
>
> My foreword was "if I understand correctly", which I clearly didn't. ;-)
>
> OK, so Sebastian's rework irq-orion.c is about the MAIN interrupt
> controller (replaces arch/arm/plat-orion/irq.c), which also cascades
> interrupts from GPIOs.
> These are then either handled by gpio-mvebu.c (for all platforms which
> are DT capable) or by arch/arm/plat-orion/gpio.c (legacy).
> Is that right?
Yes, that's right.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-02 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 12:31 [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang Gerlando Falauto
2013-10-02 12:34 ` [PATCH 1/1] gpio: mvebu: enable and use IRQ_GC_MASK_CACHE_PER_TYPE Gerlando Falauto
2013-10-11 11:13 ` Linus Walleij
2013-10-02 12:45 ` [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang Thomas Petazzoni
2013-10-02 13:14 ` Gerlando Falauto
2013-10-02 13:48 ` Thomas Petazzoni [this message]
2013-10-11 11:15 ` Linus Walleij
2013-10-11 11:21 ` Gerlando Falauto
2013-10-11 12:44 ` Linus Walleij
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=20131002154821.385e0921@skate \
--to=thomas.petazzoni@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