[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3d27d0a4-2115-fa72-8990-a84910e4215f@kernel.org>
Date: Wed, 23 Sep 2020 21:15:09 -0400
From: Sinan Kaya <okaya@...nel.org>
To: "Kuppuswamy, Sathyanarayanan"
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Bjorn Helgaas <helgaas@...nel.org>
Cc: bhelgaas@...gle.com, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, ashok.raj@...el.com,
Jay Vosburgh <jay.vosburgh@...onical.com>
Subject: Re: [PATCH v3 1/1] PCI/ERR: Fix reset logic in pcie_do_recovery()
call
On 9/22/2020 7:44 PM, Kuppuswamy, Sathyanarayanan wrote:
>> here does the restore happen here? I.e., what function does this?
>
> DLLSC link down event will remove affected devices/drivers. And link up
> event
> will re-create all devices.
>
> on DLLSC link down event
> ->pciehp_ist()
> ->pciehp_handle_presence_or_link_change()
> ->pciehp_disable_slot()
> ->__pciehp_disable_slot()
> ->remove_board()
> ->pciehp_unconfigure_device()
>
> on DLLSC link up event
> ->pciehp_ist()
> ->pciehp_handle_presence_or_link_change()
> ->pciehp_enable_slot()
> ->__pciehp_enable_slot()
> ->board_added()
> ->pciehp_configure_device()
AFAIK, DLLSC is a requirement not optional. Why is this not supported by
non-hotplug ports?
Powered by blists - more mailing lists