From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes
Date: Thu, 25 Sep 2014 18:56:12 -0300 [thread overview]
Message-ID: <20140925215612.GA3846@arch.cereza> (raw)
In-Reply-To: <1411643839-64925-1-git-send-email-jaz@semihalf.com>
Jason,
On 25 Sep 01:17 PM, Grzegorz Jaszczyk wrote:
> This patchset contains a set of fixes for issues found while doing some test
> with different interrupts configuration on Armada 375 and Armada 38x Marvell
> SoCs. The patches were tested and apply on v3.17-rc6.
>
> Any feedback is welcome.
>
> Grzegorz Jaszczyk (2):
> irqchip: armada-370-xp: fix MSI interrupt handling
> irqchip: armada-370-xp: fix MPIC interrupt handling
The second patch fixes an unhandled IRQ storm triggered by the mvpp2
ethernet driver, when the kernel is built with CONFIG_SMP=n.
When any network activity is attempted the kernel is interrupted by a per-cpu
IRQ (which is not the one the driver expects). The interrupt is not mapped
into Linux's virtual IRQ space, so the result is:
irq 0, desc: ee004000, depth: 1, count: 0, unhandled: 0
->handle_irq(): c00466e8, handle_bad_irq+0x0/0x260
->irq_data.chip(): c1181460, 0xc1181460
->action(): (null)
IRQ_NOPROBE set
IRQ_NOREQUEST set
For both patches:
Fixes: bc69b8adfe22 ("irqchip: armada-370-xp: Setup a chained handler for the MPIC")
Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Thanks,
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next parent reply other threads:[~2014-09-25 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1411643839-64925-1-git-send-email-jaz@semihalf.com>
2014-09-25 21:56 ` Ezequiel Garcia [this message]
2014-10-03 13:50 ` [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes Jason Cooper
2014-10-21 14:19 ` Ezequiel Garcia
2014-10-21 15:14 ` Jason Cooper
2014-10-21 21:22 ` Ezequiel Garcia
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=20140925215612.GA3846@arch.cereza \
--to=ezequiel.garcia@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).