From: Murali Karicheri <m-karicheri2@ti.com>
To: L H <swdevgid@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Hot reset in downstream direction (RC to EP)
Date: Tue, 12 Apr 2016 15:44:37 -0400 [thread overview]
Message-ID: <570D5025.4080905@ti.com> (raw)
In-Reply-To: <CAA8O7CpAB18JOC6ri9xf_hnrKqRAjv5TdPO1cEHfd+98BhhV7A@mail.gmail.com>
On 04/12/2016 02:28 PM, L H wrote:
> I've never observed a hot reset during enumeration. One of the
> possible triggers for the RC to issue a hot reset is after receipt of
> a fatal AER message (assuming AER is enabled).
>
Lance,
Ok. Thanks for the response.
Murali
> Lance
>
> On Fri, Apr 8, 2016 at 4:51 PM, Murali Karicheri <m-karicheri2@ti.com> wrote:
>> I see that hot reset is something the RC port initiate to have EP reset
>> through link management.
>>
>> ==========================================================================
>> PCIe reset sequences – The PCI Express protocol specifies a hot reset
>> mechanism, where downstream components reset through link notification.
>> Root ports should validate that this mechanism can be applied and the
>> hot reset indication is properly detected by a remote device.
>> Endpoint applications should determine the level of chip reset desired
>> in case of hot reset detection on the link to validate proper functionality.
>> ===========================================================================
>>
>> Does this happen during the enumeration? As this goes in in band, the EP's
>> link should be up. Can someone tell me what are the triggering points for
>> this from RC to EP? Does Linux RC support this? It is supposed to a bit
>> in RC's bridge configuration space that triggers this reset.
>>
>> --
>> Murali Karicheri
>> Linux Kernel, Keystone
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Murali Karicheri
Linux Kernel, Keystone
prev parent reply other threads:[~2016-04-12 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 21:51 Hot reset in downstream direction (RC to EP) Murali Karicheri
2016-04-12 18:28 ` L H
2016-04-12 19:44 ` Murali Karicheri [this message]
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=570D5025.4080905@ti.com \
--to=m-karicheri2@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=swdevgid@gmail.com \
/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).