Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1718484
| From | Oza Oza <oza.oza@broadcom.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP |
| Date | 2017-08-23 18:10 +0200 |
| Message-ID | <uhGo9-2JU-3@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <uho7T-7sy-1@gated-at.bofh.it> <uhB58-7JE-11@gated-at.bofh.it> <uhEml-1ex-3@gated-at.bofh.it> <uhG4O-2mD-19@gated-at.bofh.it> <uhGeu-2rq-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya <okaya@codeaurora.org> wrote: > Hi Oza, > >> In working Enumuration case I get following: >> [ 9.125976] pci 0000:00:00.0: bridge configuration invalid ([bus >> 00-00]), re-configuring >> [ 9.134267] where=0x0 val=0xffff0001 >> [ 9.146946] where=0x0 val=0xffff0001 >> [ 9.158943] where=0x0 val=0xffff0001 >> [ 9.170945] where=0x0 val=0xffff0001 >> [ 9.186945] where=0x0 val=0xffff0001 >> [ 9.210944] where=0x0 val=0xffff0001 >> [ 9.250943] where=0x0 val=0xffff0001 >> [ 9.322942] where=0x0 val=0xffff0001 >> [ 9.458943] where=0x0 val=0xffff0001 >> [ 9.726942] where=0x0 val=0x9538086 >> actual vendor and device id. >> >> so I think I have to retry in RC driver, so the old code still holds good. >> except that I have to do factoring out > You need to return 0xFFFF0001 for vendor ID register and return 0xFFFFFFFF for > other registers like COMMAND register during the CRS period. > Hi Sinan, Although I don't disagree entirely with your suggestion, but at the same time, I am not sure, in RC driver I should have special case for vendor id and device id, and have another case for rest of the configuration access. my thinking is, the RC driver should closely reflect the PCI iproc HW behaviour (in a generic way, rather than handling vendor/device id case separately) Bjorn, please comment as how do you see it being handled. Regards, Oza. >> >> please let me know If I missed anything, or you want me to try anything else. > > Sinan
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Pawandeep <oza.oza@broadcom.com> - 2017-08-21 18:00 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Bjorn Helgaas <helgaas@kernel.org> - 2017-08-22 22:40 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Oza <oza.oza@broadcom.com> - 2017-08-23 12:30 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Bjorn Helgaas <helgaas@kernel.org> - 2017-08-23 16:00 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Oza <oza.oza@broadcom.com> - 2017-08-23 17:50 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Sinan Kaya <okaya@codeaurora.org> - 2017-08-23 18:00 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Oza <oza.oza@broadcom.com> - 2017-08-23 18:10 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Bjorn Helgaas <helgaas@kernel.org> - 2017-08-23 20:10 +0200
Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Oza <oza.oza@broadcom.com> - 2017-08-24 06:50 +0200
csiph-web