linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 14:00:04 +0200	[thread overview]
Message-ID: <4B28CBC4.4010501@embedded-sol.com> (raw)
In-Reply-To: <0949C49693EF1A47A54B0F0113CDB4A6076776@zin33exm23.fsl.freescale.net>

Mahajan Vivek-B08308 wrote:
>> From: Felix Radensky [mailto:felix@embedded-sol.com] 
>> Sent: Wednesday, December 16, 2009 2:56 PM
>> To: Mahajan Vivek-B08308
>> Cc: linuxppc-dev@ozlabs.org; Aggrwal Poonam-B10812; Kumar Gala
>> Subject: Re: Problem with mini-PCI-E slot on P2020RDB
>>
>> Hi,
>>     
>>> 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 ?
>>     
>
> As per the p2020rm, PCIe legacy INTA is shared with IRQ0 for 
> this ctlr, which is the exactly the case with other SoC's 
> p2020ds, mpc8536ds, mpc8572ds. To me it seems like a board 
> issue and it needs to be followed up.
>
> I plugged in ralink rt2860 pcie wirless card in the mini-pcie 
> slot of p2020rdb, which ran fine becaused it used MSI by default.
> How hard is it to enable MSI in the atheros wireless driver.
>
>   

I've enabled MSI in ath9k driver, by simply adding pci_enable_msi() and
pci_disable_msi() at relevant places. The MSI interrupt is allocated.

irq: irq 0 on host /soc@ffe00000/msi@41600 mapped to virtual irq 18
phy0: Atheros AR9280 MAC/BB Rev:2 AR5133 RF Rev:d0: mem=0xf2160000, irq=18

cat /proc/interrupts
           CPU0
 18:          0   FSL-MSI   Edge      ath9k

lspci -v shows that MSI was enabled on device

But I don't get any interrupts. I've posted a question to ath9k list, 
maybe folks there
will have some ideas.

Thanks.

Felix.

  reply	other threads:[~2009-12-16 12:00 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
2009-12-16  9:52     ` Mahajan Vivek-B08308
2009-12-16 12:00       ` Felix Radensky [this message]
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=4B28CBC4.4010501@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=B08308@freescale.com \
    --cc=B10812@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).