From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Maik Broemme <mbroemme@libmpq.org>,
Pawandeep Oza <poza@codeaurora.org>,
Sinan Kaya <okaya@codeaurora.org>
Subject: Re: [PATCHv2 4/6] PCI/DPC: Print AER status in DPC event handling
Date: Thu, 25 Jan 2018 14:19:49 -0700 [thread overview]
Message-ID: <20180125211949.GA20258@localhost.localdomain> (raw)
In-Reply-To: <20180125211521.GB19484@localhost.localdomain>
On Thu, Jan 25, 2018 at 02:15:21PM -0700, Keith Busch wrote:
> On Thu, Jan 25, 2018 at 01:55:12PM -0600, Bjorn Helgaas wrote:
>
> > After we clear PCI_EXP_DPC_STATUS_TRIGGER, we're supposed to "honor
> > timing requirements ... with respect to the first Configuration Read
> > following a Conventional Reset" (PCIe r4.0, sec 7.9.15.4). Where does
> > that happen?
>
> That is referring to reading the downstream port, and that is not
> handled by the DPC driver. The expectation is that the link is down on a
> DPC event, and the Link Up is handled by the pciehp driver, which
> should be honoring those timing requirements.
Sorry, I didn't mean "reading the downstream port". You can config read
that anytime. I meant issuing a config read to the device connected
downstream the contained port.
next prev parent reply other threads:[~2018-01-25 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 5:22 [PATCHv2 0/6] PCI/DPC updates Keith Busch
2018-01-17 5:22 ` [PATCHv2 1/6] PCI/AER: Return correct value when AER is not supported Keith Busch
2018-01-17 5:22 ` [PATCHv2 2/6] PCI/AER: API for obtaining AER information Keith Busch
2018-01-17 5:22 ` [PATCHv2 3/6] PCI/DPC: Enable DPC in conjuction with AER Keith Busch
2018-01-17 5:22 ` [PATCHv2 4/6] PCI/DPC: Print AER status in DPC event handling Keith Busch
2018-01-25 19:55 ` Bjorn Helgaas
2018-01-25 21:15 ` Keith Busch
2018-01-25 21:19 ` Keith Busch [this message]
2018-01-17 5:22 ` [PATCHv2 5/6] PCI/DPC: Fix interrupt message number print Keith Busch
2018-01-17 5:22 ` [PATCHv2 6/6] PCI/DPC: Enable ERR_COR Keith Busch
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=20180125211949.GA20258@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mbroemme@libmpq.org \
--cc=okaya@codeaurora.org \
--cc=poza@codeaurora.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).