[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE9FiQWyuW_ukTiYR+Kb1ZoqK7cZSeUE7f8TYRh4B6cF=XywUA@mail.gmail.com>
Date: Sun, 3 Sep 2017 15:13:51 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Sinan Kaya <okaya@...eaurora.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
timur@...eaurora.org, Alex Williamson <alex.williamson@...hat.com>,
linux-arm-msm@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V13 1/4] PCI: Don't ignore valid response before CRS timeout
On Tue, Aug 29, 2017 at 12:53 PM, Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> Applied this series to pci/enumeration for v4.14. You didn't include a
> cover letter, but the series includes:
>
> [V13 1/4] PCI: Don't ignore valid response before CRS timeout
> [V13 2/4] PCI: Factor out pci_bus_wait_crs()
> [V13 3/4] PCI: Handle CRS ('device not ready') returned by device af
> [V13 4/4] PCI: Warn periodically while waiting for device to become
>
> I made some changes:
>
> - Renamed pci_bus_crs_visibility_pending() to pci_bus_crs_vendor_id()
> because the CRS completion is not "pending". It is not waiting
> somewhere for us to do something about it. The CRS completion has
> already occurred and is over. All we have now is a magic Vendor ID
> value that tells us that it happened.
>
> - Split addition of pci_bus_crs_vendor_id() to a separate patch, move
> it to probe.c, and make it static.
the calling of pci_bus_crs_vendor_id() in pci_bus_read_dev_vendor_id()
could be removed. pci_bus_wait_crs() have that calling inside.
-Yinghai
Powered by blists - more mailing lists