[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 11 Nov 2021 18:32:28 +0100
From: Robert Święcki <robert@...ecki.net>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
linux-i2c <linux-i2c@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Linux PCI <linux-pci@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH] pci: Don't call resume callback for nearly bound devices
Hi,
> > Thank you very much for testing this. The patch changed the way we
> > use runtime PM, and the dmesg snippets below look like they could be
> > related to runtime PM issues.
> >
> > I think the conclusion is that we need to revert these commits:
> >
> > b5f9c644eb1b ("PCI: Remove struct pci_dev->driver")
> > 2a4d9408c9e8 ("PCI: Use to_pci_driver() instead of pci_dev->driver")
> >
> > from Linus' tree. I queued up those reverts on
> > https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=for-linus
>
> These reverts appeared in the Nov 11 linux-next tree. Any chance you
> could verify that they solve the i2c_dw_pci_resume() issue? If it's
> easier, you can apply them from:
> https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=for-linus
> instead.
Looks good with the most recent 3 commits from for-linus applied on
the top of the current linus' tree.
No problematic dmesg entries, my Win11/vfio/kvm/qemu boots fine.
--
Robert Święcki
Powered by blists - more mailing lists