From: Yinghai Lu <yinghai.lu@oracle.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [RFC PATCH] pciehp: Wait for link get trained in pci_check_link_status()
Date: Tue, 08 Nov 2011 07:27:13 -0800 [thread overview]
Message-ID: <4EB94A51.6070809@oracle.com> (raw)
In-Reply-To: <4EB8F434.6090003@jp.fujitsu.com>
On 11/08/2011 01:19 AM, Kenji Kaneshige wrote:
> (2011/11/08 10:13), Yinghai Lu wrote:
>>
>> Found one PCI Express Modules has link training error after hotplug.
>> It turns out that after DLLLA is set, LT is still set for a while.
>> So pciehp will delcare that hotplug fail in 1s.
>
> I think DLLLA bit reads 1b means LT is completed. So I don't know why LT
> is still set on your platform.
recovery training ?
>
>>
>> HW guys say that pciehp is against PCI-e SPEC:
>> From PCI Express Base Specification Revision 2.1, Section 6.7.3.3:
>> Software must allow 1 second after the Data Link Layer Link Active bit reads 1b
>> before it is permitted to determine that a hot plugged device which fails to
>> return a Successful Completion for a Valid Configuration Request is a broken
>> device (see section 6.6).
>>
>> Try to wait for long enough by adding LT checking in 1s.
>
> The pciehp driver already have this 1 second wait in board_added().
> So I still don't understand what in pciehp is against PCIe spec clearly.
> Can you explain more about this?
should be fail in 1s after DLLLA, is set.
even we should not check LT, and should try pci conf reading to new added device.
>
> What about the patch below? I think it's much simpler and has less impact.
Should work. will try it today.
Thanks
Yinghai Lu
next prev parent reply other threads:[~2011-11-08 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:13 [RFC PATCH] pciehp: Wait for link get trained in pci_check_link_status() Yinghai Lu
2011-11-08 9:19 ` Kenji Kaneshige
2011-11-08 15:27 ` Yinghai Lu [this message]
2011-11-08 21:54 ` Yinghai Lu
2011-11-10 7:39 ` Kenji Kaneshige
2011-11-10 7:40 ` [PATCH 1/2] pciehp: wait 1000 ms before Link Training check Kenji Kaneshige
2011-11-10 19:10 ` Yinghai Lu
2011-11-10 7:42 ` [PATCH 2/2] pciehp: wait 100 ms after " Kenji Kaneshige
2011-11-10 19:10 ` Yinghai Lu
2011-11-11 17:32 ` Jesse Barnes
2011-11-11 17:33 ` Yinghai Lu
2011-11-11 17:40 ` Greg KH
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=4EB94A51.6070809@oracle.com \
--to=yinghai.lu@oracle.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox