From: Lukas Wunner <lukas@wunner.de>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Cc: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
oohall@gmail.com, Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Fontenot Nathan <Nathan.Fontenot@amd.com>
Subject: Re: [PATCH v3 1/2] PCI: pciehp: Add support for async hotplug with native AER and DPC/EDR
Date: Wed, 28 Jun 2023 15:29:44 +0200 [thread overview]
Message-ID: <20230628132944.GB14276@wunner.de> (raw)
In-Reply-To: <a79c82bb-e1fe-891c-87f9-6231a30e5ef2@amd.com>
On Tue, Jun 27, 2023 at 10:48:37AM -0700, Smita Koralahalli wrote:
> On 6/22/2023 4:22 PM, Sathyanarayanan Kuppuswamy wrote:
> > On 6/21/23 11:51 AM, Smita Koralahalli wrote:
> > > +static void dpc_handle_surprise_removal(struct pci_dev *pdev)
> > > +{
> > > + if (pdev->dpc_rp_extensions && dpc_wait_rp_inactive(pdev)) {
> > > + pci_err(pdev, "failed to retrieve DPC root port on async remove\n");
> > > + goto out;
> > > + }
> > > +
> > > + pci_aer_raw_clear_status(pdev);
> > > + pci_clear_surpdn_errors(pdev);
> > > +
> > > + pci_write_config_word(pdev, pdev->dpc_cap + PCI_EXP_DPC_STATUS,
> > > + PCI_EXP_DPC_STATUS_TRIGGER);
> >
> > Don't you need to wait for the link to go down?
>
> Yes will include, pcie_wait_for_link()..
>
> Should this check be here or at the beginning of the function before we
> check pdev->dpc_rp_extensions?
I'd just use the same order as dpc_reset_link(), i.e. checking for
!pcie_wait_for_link() happens before the check for pdev->dpc_rp_extensions.
Thanks,
Lukas
next prev parent reply other threads:[~2023-06-28 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 18:51 [PATCH v3 0/2] PCI: pciehp: Add support for native AER and DPC handling on async remove Smita Koralahalli
2023-06-21 18:51 ` [PATCH v3 1/2] PCI: pciehp: Add support for async hotplug with native AER and DPC/EDR Smita Koralahalli
2023-06-22 9:04 ` Lukas Wunner
2023-06-22 21:02 ` Smita Koralahalli
2023-06-22 21:22 ` Lukas Wunner
2023-06-22 23:22 ` Sathyanarayanan Kuppuswamy
2023-06-27 17:48 ` Smita Koralahalli
2023-06-28 13:29 ` Lukas Wunner [this message]
2023-06-21 18:51 ` [PATCH v3 2/2] PCI: pciehp: Clear the optional capabilities in DEVCTL2 on a hot-plug Smita Koralahalli
2023-06-22 6:31 ` Lukas Wunner
2023-06-22 10:04 ` Lukas Wunner
2023-06-22 21:02 ` Smita Koralahalli
2023-06-22 21:42 ` Lukas Wunner
2023-06-23 3:59 ` Felix Kuehling
2023-06-23 6:06 ` Lukas Wunner
2023-06-23 13:12 ` Jay Cornwall
2023-06-27 17:38 ` Smita Koralahalli
2023-06-28 13:25 ` Lukas Wunner
2023-07-01 6:29 ` Smita Koralahalli
2023-08-15 21:22 ` Smita Koralahalli
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=20230628132944.GB14276@wunner.de \
--to=lukas@wunner.de \
--cc=Nathan.Fontenot@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=yazen.ghannam@amd.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