From: Felix Radensky <felix@embedded-sol•com>
To: Kushwaha Prabhakar-B32579 <B32579@freescale•com>
Cc: Mahajan Vivek-B08308 <B08308@freescale•com>,
Aggrwal Poonam-B10812 <B10812@freescale•com>,
Leon Woestenberg <leon.woestenberg@gmail•com>,
"linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>,
Gupta Maneesh-B18878 <B18878@freescale•com>,
Fabian Bertholm <fabeisageek@googlemail•com>
Subject: Re: Problem with mini-PCI-E slot on P2020RDB
Date: Mon, 11 Apr 2011 11:39:37 +0300 [thread overview]
Message-ID: <4DA2BE49.9000003@embedded-sol.com> (raw)
In-Reply-To: <071A08F2C6A57E4E94D980ECA553F87416F971@039-SN1MPN1-004.039d.mgd.msft.net>
Hi,
Assuming I have all patches in place, will this problem be
resolved on earlier board revisions (before rev D) ?
Felix.
On 04/11/2011 12:06 PM, Kushwaha Prabhakar-B32579 wrote:
> Hi Fabe,
>
> Yes .. P1020/P1011 RDB has same issue as of P2020RDB.
>
> It was because of some missing patches at u-boot and Linux.
>
> U-boot patch : It is already present in open source. Please use latest code base
> Linux patch : I am in process of posting in open source. Please make mentioned changes of IDSEL.
>
> --Prabhakar
>
>> -----Original Message-----
>> From: Fabian Bertholm [mailto:fabeisageek@googlemail•com]
>> Sent: Monday, April 11, 2011 1:53 PM
>> To: Kushwaha Prabhakar-B32579
>> Cc: Leon Woestenberg; linuxppc-dev@ozlabs•org; Mahajan Vivek-B08308;
>> Felix Radensky; Aggrwal Poonam-B10812; Gupta Maneesh-B18878
>> Subject: Re: Problem with mini-PCI-E slot on P2020RDB
>>
>> Hello Kushwaha Prabhakar,
>>
>> Our impression is that there is the same issue on the P1020/P1011 RDB.
>> Can you confirm this?
>>
>> Best Regards,
>> Fabe
>>
>>
>> 2011/4/8 Kushwaha Prabhakar-B32579<B32579@freescale•com>:
>>>
>>>> -----Original Message-----
>>>> From: Leon Woestenberg [mailto:leon.woestenberg@gmail•com]
>>>> Sent: Thursday, April 07, 2011 10:50 PM
>>>> To: linuxppc-dev@ozlabs•org
>>>> Cc: Kumar Gala; Mahajan Vivek-B08308; Aggrwal Poonam-B10812; Felix
>>>> Radensky; Kushwaha Prabhakar-B32579
>>>> Subject: Re: Problem with mini-PCI-E slot on P2020RDB
>>>>
>>>> Hello,
>>>>
>>>> On Thu, Dec 17, 2009 at 9:28 PM, Felix Radensky
>>>> <felix@embedded-sol•com>
>>>> wrote:
>>>>> Kumar Gala wrote:
>>>>>> On Dec 17, 2009, at 2:59 AM, Mahajan Vivek-B08308 wrote:
>>>>>>>> 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 hardware fix. Right ?
>>>>>>>>
>>>>>>> Correct
>>>>>> I'm confused. What's the issue with IRQ0 on the P2020RDB? Is it
>>>>>> used for another purpose?
>>>>> There's a problem with IRQ0 with respect to mini-PCI-E slot. I have
>>>>> Atheros 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
>>>>> conclusion 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.
>>>>
>>>>
>>> Hello Leon,
>>>
>>> Yes you are right, PCIe leagacy interrupt is shared with IRQ0. For
>> Atheros issue.
>>> Can you please try followings, Meanwhile I will try to dig into it.
>>>
>>> http://old.nabble.com/Problem-with-mini-PCI-E-slot-on-P2020RDB-td26802
>>> 038.html
>>>
>>> Regarding sata_sil24, Please see my e-mail on Linux-ide for correct
>> IDSEL value.
>>> Please first try IDSEL value mentioned in email on Linux-ide. Then try
>> this URL..
>>> --Prabhakar
>>>
>>> _______________________________________________
>>> Linuxppc-dev mailing list
>>> Linuxppc-dev@lists•ozlabs.org
>>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>>>
>
next prev parent reply other threads:[~2011-04-11 11:03 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
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 [this message]
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=4DA2BE49.9000003@embedded-sol.com \
--to=felix@embedded-sol$(echo .)com \
--cc=B08308@freescale$(echo .)com \
--cc=B10812@freescale$(echo .)com \
--cc=B18878@freescale$(echo .)com \
--cc=B32579@freescale$(echo .)com \
--cc=fabeisageek@googlemail$(echo .)com \
--cc=leon.woestenberg@gmail$(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