Re: [PATCH 2/3] PCI: iproc: CRS state check in config request

2019-01-24 Thread Srinath Mannam
Hi Bjorn, Thanks for review, please see my comments below inline. On Fri, Jan 18, 2019 at 8:38 PM Bjorn Helgaas wrote: > > On Fri, Jan 18, 2019 at 09:53:22AM +0530, Srinath Mannam wrote: > > In the current implementation, config read of 0x0001 data > > is assumed as CRS completion. but somet

Re: [PATCH 2/3] PCI: iproc: CRS state check in config request

2019-01-18 Thread Bjorn Helgaas
On Fri, Jan 18, 2019 at 09:53:22AM +0530, Srinath Mannam wrote: > In the current implementation, config read of 0x0001 data > is assumed as CRS completion. but sometimes 0x0001 can be > a valid data. > IPROC PCIe RC has a register to show config request status flags > like SC, UR, CRS and C

[PATCH 2/3] PCI: iproc: CRS state check in config request

2019-01-17 Thread Srinath Mannam
In the current implementation, config read of 0x0001 data is assumed as CRS completion. but sometimes 0x0001 can be a valid data. IPROC PCIe RC has a register to show config request status flags like SC, UR, CRS and CA. So that extra check is added in the code to confirm the CRS state using