From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCHv4] pcie: Add driver for Downstream Port Containment
Date: Fri, 6 May 2016 11:20:27 -0500 [thread overview]
Message-ID: <20160506162027.GA20010@localhost> (raw)
In-Reply-To: <20160502202538.GK24851@localhost>
On Mon, May 02, 2016 at 03:25:38PM -0500, Bjorn Helgaas wrote:
> On Thu, Apr 28, 2016 at 04:24:48PM -0600, Keith Busch wrote:
> > This adds driver support for root and downstream ports that implement
> > the PCI-Express Downstream Port Containment extended capability. DPC is
> > an optional capability to contain uncorrectable errors below a port.
> >
> > For more information on DPC, please see PCI Express Base Specification
> > Revision 4, section 7.31, or view the PCI-SIG DPC ECN here:
> >
> > https://pcisig.com/sites/default/files/specification_documents/ECN_DPC_2012-02-09_finalized.pdf
> >
> > When a DPC event is triggered, the h/w disables downstream links, so
> > the DPC driver schedules removal for all devices below this port. This
> > may happen concurrently with a PCI-e hotplug driver if enabled. When all
> > downstream devices are removed and the link state transitions to disabled,
> > the DPC driver clears the DPC status and interrupt bits so the link may
> > retrain for a newly connected device.
> >
> > The pcie device naming is updated to accomodate the additional service
> > driver. From Lukas Wunner <lukas@wunner.de>:
> >
> > The names of port service devices previously used one nibble to encode
> > the port type and another nibble to encode the service type. Since this
> > commit introduces a fifth service type, it changes device names to use
> > one *byte* to encode the service type. E.g. a hotplug port service on a
> > downstream bridge was previously called pcie24 and is now called pcie204.
> >
> > Signed-off-by: Keith Busch <keith.busch@intel.com>
> > Cc: Lukas Wunner <lukas@wunner.de>
>
> Applied to pci/dpc for v4.7, thanks, Keith.
>
> > +static void dpc_remove(struct pcie_device *dev)
> > +{
> > + struct dpc_dev *dpc = get_service_data(dev);
> > + struct pci_dev *pdev = dev->port;
> > + u16 ctl;
> > +
> > + pci_read_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_CTL, &ctl);
> > + ctl |= ~(PCI_EXP_DPC_CTL_EN_NONFATAL | PCI_EXP_DPC_CTL_INT_EN);
>
> This looks like a typo; I assume you meant:
>
> ctl &= ~(PCI_EXP_DPC_CTL_EN_NONFATAL | PCI_EXP_DPC_CTL_INT_EN);
>
> so we *clear* (not set) these bits on removal. I made this change on
> my branch.
Hi Keith, can you double-check and confirm that this was indeed a typo
and that what's in my next branch is correct?
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=next&id=26e515713342b6f7c553aa3c66b21c6ab7cf82af
next prev parent reply other threads:[~2016-05-06 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:24 [PATCHv4] pcie: Add driver for Downstream Port Containment Keith Busch
2016-05-02 20:25 ` Bjorn Helgaas
2016-05-06 16:20 ` Bjorn Helgaas [this message]
2016-05-06 17:06 ` Keith Busch
2016-05-11 16:08 ` Bjorn Helgaas
2016-05-11 17:06 ` Keith Busch
2016-05-11 18:28 ` Bjorn Helgaas
2016-05-11 19:55 ` Lukas Wunner
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=20160506162027.GA20010@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.