From: Felix Radensky <felix@embedded-sol•com>
To: Mahajan Vivek-B08308 <B08308@freescale•com>
Cc: linuxppc-dev@ozlabs•org, Aggrwal Poonam-B10812 <B10812@freescale•com>
Subject: Re: Problem with mini-PCI-E slot on P2020RDB
Date: Wed, 16 Dec 2009 11:26:27 +0200 [thread overview]
Message-ID: <4B28A7C3.6040209@embedded-sol.com> (raw)
In-Reply-To: <0949C49693EF1A47A54B0F0113CDB4A607674F@zin33exm23.fsl.freescale.net>
Hi,
Mahajan Vivek-B08308 wrote:
>
>> Hi,
>>
>> I'm trying to use mini-PCI-E WLAN card on P2020RDB running
>> 2.6.32, but so far without success.
>> ath9k driver identifies the device, I can run ifconfig,
>> iwconfig and hostapd on wlan0, but device is not getting any
>> interrupts, so I suspect the interrupt configuration is
>> wrong. Atheros ath9k driver reports:
>>
>> phy0: Atheros AR9280 MAC/BB Rev:2 AR5133 RF Rev:d0:
>> mem=0xf1060000, irq=16
>>
>> The mapping for irq 16 is:
>>
>> irq: irq 1 on host /soc@ffe00000/pic@40000 mapped to virtual irq 16
>>
>> According to /proc/interrupts:
>>
>> CPU0
>> 16: 0 OpenPIC Edge ath9k
>>
>> The same problem happens if Atheros card is plugged (with
>> adapter) into regular PCI-E slot.
>>
>> It seems that p2020rdb device tree is missing
>> interrupt-map-mask and interrupt-map properties in PCI-E nodes.
>>
>> I've tried running kernel from latest FSL BSP for this board
>> (based on 2.6.32-rc3). The device tree has the
>> interrupt-map-mask and interrupt-map properties, and
>> interrupt mapping is different:
>>
>> irq: irq 0 on host /soc@ffe00000/pic@40000 mapped to virtual irq 16
>>
>> In /proc/interrups I see
>> CPU0
>> 16: 100001 OpenPIC Level ath9k
>>
>> However, when ath9k driver is loaded I get this:
>>
>> irq 16: nobody cared (try booting with the "irqpoll" option)
>> Call Trace:
>> [efbefa40] [c00074b0] show_stack+0x4c/0x16c (unreliable)
>> [efbefa70] [c0073970] __report_bad_irq+0x38/0xd0 [efbefa90]
>> [c0073bd4] note_interrupt+0x1cc/0x22c [efbefac0] [c00747d0]
>> handle_fasteoi_irq+0xf4/0x128 [efbefae0] [c0004eb8]
>> do_IRQ+0xc8/0xf4 [efbefb00] [c001081c]
>> ret_from_except+0x0/0x18 [efbefbc0] [00000000] (null)
>> [efbefc10] [c0004d24] do_softirq+0x60/0x64 [efbefc20]
>> [c0044670] irq_exit+0x88/0xa8 [efbefc30] [c0004ebc]
>> do_IRQ+0xcc/0xf4 [efbefc50] [c001081c]
>> ret_from_except+0x0/0x18 [efbefd10] [c00730b4]
>> __setup_irq+0x320/0x39c [efbefd30] [c0073214]
>> request_threaded_irq+0xe4/0x148 [efbefd60] [f2244218]
>> ath_pci_probe+0x1b0/0x3a4 [ath9k] [efbefda0] [c01c386c]
>> local_pci_probe+0x24/0x34 [efbefdb0] [c01c3bc0]
>> pci_device_probe+0x84/0xa8 [efbefde0] [c01e86b8]
>> driver_probe_device+0xa8/0x1a8 [efbefe00] [c01e8874]
>> __driver_attach+0xbc/0xc0 [efbefe20] [c01e7d88]
>> bus_for_each_dev+0x70/0xac [efbefe50] [c01e84d8]
>> driver_attach+0x24/0x34 [efbefe60] [c01e7504]
>> bus_add_driver+0xb8/0x278 [efbefe90] [c01e8bec]
>> driver_register+0x84/0x178 [efbefeb0] [c01c3e6c]
>> __pci_register_driver+0x54/0xe4 [efbefed0] [f2244434]
>> ath_pci_init+0x28/0x38 [ath9k] [efbefee0] [f215702c]
>> ath9k_init+0x2c/0x100 [ath9k] [efbefef0] [c0001d34]
>> do_one_initcall+0x3c/0x1e8 [efbeff20] [c006f9f0]
>> sys_init_module+0xf8/0x220 [efbeff40] [c00101c4]
>> ret_from_syscall+0x0/0x3c
>> handlers:
>> [<f223badc>] (ath_isr+0x0/0x1b4 [ath9k]) Disabling IRQ #16
>>
>
> Looks like INTA is not being routed to IRQ0 properly for this
> PCIe ctlr. Try changing the interrupt-map prop for the ctlr
> at 0xffe0a000 to the following, temporarily:-
>
> interrupt-map = <
> /* IDSEL 0x0 */
> 0000 0x0 0x0 0x1 &mpic 0x1 0x1
> 0000 0x0 0x0 0x2 &mpic 0x2 0x1
> 0000 0x0 0x0 0x3 &mpic 0x3 0x1
> 0000 0x0 0x0 0x4 &mpic 0x0 0x1
>
Thanks for your help. With this change "nobody cared" message disappears,
but interrupts are not coming at all.
Is it a SoC problem or a board problem ?
Thanks.
Felix.
next prev parent reply other threads:[~2009-12-16 9:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 21:25 Problem with mini-PCI-E slot on P2020RDB Felix Radensky
2009-12-16 6:49 ` Mahajan Vivek-B08308
2009-12-16 9:26 ` Felix Radensky [this message]
2009-12-16 9:52 ` Mahajan Vivek-B08308
2009-12-16 12:00 ` Felix Radensky
2009-12-16 12:27 ` Mahajan Vivek-B08308
2009-12-17 7:22 ` Felix Radensky
2009-12-17 7:59 ` Mahajan Vivek-B08308
2009-12-17 8:56 ` Felix Radensky
2009-12-17 8:59 ` Mahajan Vivek-B08308
2009-12-17 17:01 ` Kumar Gala
2009-12-17 20:28 ` Felix Radensky
2011-04-07 17:20 ` Leon Woestenberg
2011-04-08 3:53 ` Kushwaha Prabhakar-B32579
2011-04-11 8:23 ` Fabian Bertholm
2011-04-11 9:06 ` Kushwaha Prabhakar-B32579
2011-04-11 8:39 ` Felix Radensky
2011-04-11 11:09 ` Kushwaha Prabhakar-B32579
2011-04-11 13:45 ` Felix Radensky
[not found] <071A08F2C6A57E4E94D980ECA553F87417069A@039-SN1MPN1-004.039d.mgd.msft.net>
2011-04-12 4:05 ` Aggrwal Poonam-B10812
2011-04-12 4:35 ` Benjamin Herrenschmidt
2011-04-12 4:45 ` Felix Radensky
2011-04-12 4:54 ` Felix Radensky
2011-04-13 9:22 ` Leon Woestenberg
[not found] <470DB7CE2CD0944E9436E7ADEFC02FE314BF85@039-SN1MPN1-001.039d.mgd.msft.net>
2011-04-13 4:40 ` Kushwaha Prabhakar-B32579
[not found] <45903308677306428B6EE7E6FF5A520410D3E6@039-SN1MPN1-004.039d.mgd.msft.net>
2011-04-15 6:27 ` Kushwaha Prabhakar-B32579
2011-04-15 7:20 ` Felix Radensky
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=4B28A7C3.6040209@embedded-sol.com \
--to=felix@embedded-sol$(echo .)com \
--cc=B08308@freescale$(echo .)com \
--cc=B10812@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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