Re: Problem with mini-PCI-E slot on P2020RDB
From: Leon Woestenberg <hidden>
Date: 2011-04-07 17:20:28
Hello, On Thu, Dec 17, 2009 at 9:28 PM, Felix Radensky [off-list ref] wr= ote:
Kumar Gala wrote:quoted
On Dec 17, 2009, at 2:59 AM, Mahajan Vivek-B08308 wrote:quoted
quoted
Thanks a lot. If I understand you correctly, the only way I can get ath9k driver to work on this board using legacy interrupts is to wait =
for a
quoted
quoted
quoted
hardware fix. Right ?CorrectI'm confused. =A0What's the issue with IRQ0 on the P2020RDB? =A0Is it us=
ed for
quoted
another purpose?There's a problem with IRQ0 with respect to mini-PCI-E slot. I have Ather=
os
wireless card plugged into it. ath9k wireless driver for this card uses legacy PCI-E interrupts=
,
and I get "irq 16: nobody cared" message when driver executes request_irq(). Vivek has come to a conclusio=
n
that the problem is related to incorrect IRQ0 routing for mini-PCI-E slot on P2020RDB.
I would like to understand this issue better, as I seem to be running into something similar, and it puts my board design on hold. Can someone (from Freescale) explain what happens if a PCI Express end point on the mini-PCIe slot raises a legacy interrupt, and where this goes wrong?
From what document or source code file can I conclude that the PCIe
legacy interrupt is shared with IRQ0? I found this: P1020E/P2020E RDB System Errata, Last Update: 2/15/2010: Problem:IRQ0 held low Fix: Add 4.7K pull-up (to 3.3.V) for RTC_INT_N. See R420 in Rev D schematic. Add 4.7K pull-up (to 3.3.V) for MCU_INT_N. See R423 in Rev D schematic. Regards, --=20 Leon