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: [PATCH 1/2] pciehp: wait 1000 ms before Link Training check
Date: Thu, 10 Nov 2011 11:10:19 -0800 [thread overview]
Message-ID: <4EBC219B.5010403@oracle.com> (raw)
In-Reply-To: <4EBB7FF5.1040109@jp.fujitsu.com>
On 11/09/2011 11:40 PM, Kenji Kaneshige wrote:
> We need to wait for 1000 ms after Data Link Layer Link Active (DLLLA)
> bit reads 1b before sending configuration request. Currently pciehp
> does this wait after checking Link Training (LT) bit. But we need it
> before checking LT bit because LT is still set even after DLLLA bit is
> set on some platforms.
>
> Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Tested-by: Yinghai Lu <yinghai@kernel.org>
next prev parent reply other threads:[~2011-11-10 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EB88238.4050409@oracle.com>
[not found] ` <4EB8F434.6090003@jp.fujitsu.com>
[not found] ` <4EB94A51.6070809@oracle.com>
[not found] ` <4EB9A50D.1040302@oracle.com>
2011-11-10 7:39 ` [RFC PATCH] pciehp: Wait for link get trained in pci_check_link_status() 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 [this message]
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
[not found] ` <4ECDA602.9060103@oracle.com>
2011-11-27 3:25 ` pciehp for stable Greg KH
2011-12-02 23:21 ` 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=4EBC219B.5010403@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