[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8c91a923-1a3a-55fb-e812-62dd69d99975@codeaurora.org>
Date: Tue, 22 May 2018 22:40:16 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: Lukas Wunner <lukas@...ner.de>
Cc: linux-pci@...r.kernel.org, timur@...eaurora.org, ryan@...nie.org,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, stable@...r.kernel.org,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Frederick Lawler <fred@...dlawl.com>,
Dongdong Liu <liudongdong3@...wei.com>,
Gabriele Paoloni <gabriele.paoloni@...wei.com>,
Keith Busch <keith.busch@...el.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] PCI/portdrv: do not disable device on remove()
On 5/22/2018 10:24 PM, Lukas Wunner wrote:
> On Tue, May 22, 2018 at 01:58:00PM -0400, Sinan Kaya wrote:
>> --- a/drivers/pci/pcie/portdrv_core.c
>> +++ b/drivers/pci/pcie/portdrv_core.c
>> @@ -409,7 +409,6 @@ void pcie_port_device_remove(struct pci_dev *dev)
>> {
>> device_for_each_child(&dev->dev, NULL, remove_iter);
>> pci_free_irq_vectors(dev);
>> - pci_disable_device(dev);
>> }
>
> Shutdown aside, pci_disable_device() is also not called in the ->remove
> path with this patch, right? Seems wrong. E.g. when unbinding the driver
> from the root port device, or when unplugging a port (happens all the time
> with Thunderbolt).
Agreed. I'll spin another version where I skip disable on shutdown path only.
>
> Thanks,
>
> Lukas
>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists