From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ARM: shmobile: sh73a0: fix spurious irqpin interrupts
Date: Tue, 23 Jul 2013 01:47:01 +0000 [thread overview]
Message-ID: <20130723014701.GH16481@verge.net.au> (raw)
In-Reply-To: <1374510105-21896-1-git-send-email-g.liakhovetski@gmx.de>
On Mon, Jul 22, 2013 at 06:21:42PM +0200, Guennadi Liakhovetski wrote:
> On sh73a0 irqpin interrupts have to be masked on the parent GIC controller.
> This can only be done if interrupts are mapped when the first spurious IRQ
> occurs. Patch 2 in this series maps all irqpin interrupts at probe time to
> fix the problem. The third patch adds support for an irqpin IRQ to
> kzm9g-reference.
>
> Cc: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Magnus, could you review this?
>
> Guennadi Liakhovetski (3):
> ARM: shmobile: sh73a0: fix spurious irqpin interrupts in the DT case
> irqchip: intc-irqpin: pre-map all interrupts in the DT case
> ARM: shmobile: kzm9g-reference: use GPIO for card detection on SDHI2
>
> arch/arm/boot/dts/sh73a0-kzm9g-reference.dts | 2 +-
> arch/arm/boot/dts/sh73a0.dtsi | 2 ++
> drivers/irqchip/irq-renesas-intc-irqpin.c | 10 +++++++++-
> 3 files changed, 12 insertions(+), 2 deletions(-)
>
> --
> 1.7.2.5
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
next prev parent reply other threads:[~2013-07-23 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 16:21 [PATCH v2 0/3] ARM: shmobile: sh73a0: fix spurious irqpin interrupts Guennadi Liakhovetski
2013-07-23 1:47 ` Simon Horman [this message]
2013-07-24 6:41 ` Magnus Damm
2013-07-24 7:02 ` Guennadi Liakhovetski
2013-07-24 7:13 ` Magnus Damm
2013-07-24 7:47 ` Guennadi Liakhovetski
2013-07-24 9:19 ` Magnus Damm
2013-07-24 10:33 ` Laurent Pinchart
2013-07-24 11:04 ` Magnus Damm
2013-07-24 12:51 ` Laurent Pinchart
2013-07-24 13:35 ` Magnus Damm
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=20130723014701.GH16481@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).