From: Roberto Fichera <kernel@tekno-soft.it>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Richard Zhu <hongxing.zhu@nxp.com>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: iMX6q: Kernel panic when enabling interrupt for more than 2 cards behind a PCIe-to-PCI bridge
Date: Wed, 23 Mar 2016 12:01:38 +0100 [thread overview]
Message-ID: <56F27792.9080600@tekno-soft.it> (raw)
In-Reply-To: <1458730121.2171.44.camel@pengutronix.de>
On 03/23/2016 11:48 AM, Lucas Stach wrote:
> Am Mittwoch, den 23.03.2016, 11:39 +0100 schrieb Roberto Fichera:
>> On 03/23/2016 11:26 AM, Lucas Stach wrote:
>>
>> Hi Lucas,
>>
>>> Am Mittwoch, den 23.03.2016, 07:13 -0300 schrieb Fabio Estevam:
>>>> On Tue, Mar 22, 2016 at 1:36 PM, Roberto Fichera <kernel@tekno-soft.it> wrote:
>>>>> Hi All,
>>>>>
>>>>> I'm getting a kernel panic with a kernel v4.4.x when enabling interrupt for 2 cards behind a PCIe-to-PCI bridge
>>>>> not sharing the same IRQ. If they don't share the same IRQ most often I'm getting a message claiming the emmc
>>>>> is stuck. I've disabled MSI from PCI config because the cards are not getting any interrupt delivered.
>>> Is the interrupt-map on your PCIe-to-PCI bridge correct? If it isn't the
>>> CPU may drown in unhandled IRQ storms.
>> Can you please be more specific? Are you talking about INTA/B/C/D mapping?
>>
> Yes. If you are using legacy interrupts that are not shared between
> devices I suppose you are using multiple IRQ pins.
>
> The interrupt-map on the i.MX6 PCI controller maps those legacy IRQs to
> the internal ARM GIC IRQs, but it doesn't say anything about how your
> bridge maps them.
>
> If it doesn't map them 1:1, you need to have an interrupt-map property
> at the bridge to define how the mapping is done.
Ok! Now I see! The bridge uses only INTA/B for the miniPCI slots
>
> Regards,
> Lucas
>
>
>
prev parent reply other threads:[~2016-03-23 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 16:36 iMX6q: Kernel panic when enabling interrupt for more than 2 cards behind a PCIe-to-PCI bridge Roberto Fichera
2016-03-23 10:13 ` Fabio Estevam
2016-03-23 10:26 ` Lucas Stach
2016-03-23 10:39 ` Roberto Fichera
2016-03-23 10:48 ` Lucas Stach
2016-03-23 11:01 ` Roberto Fichera [this message]
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=56F27792.9080600@tekno-soft.it \
--to=kernel@tekno-soft.it \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.