Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1412871
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops |
| Date | 2016-06-03 09:50 +0200 |
| Message-ID | <rFS1H-kK-7@gated-at.bofh.it> (permalink) |
| References | <rFdBf-8pl-3@gated-at.bofh.it> <rFzip-5oX-11@gated-at.bofh.it> <rFBtU-6Tw-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thursday, June 2, 2016 9:00:01 AM CEST Bjorn Helgaas wrote:
> > I just did a count of the implementations of pci_ops: I found 107
> > instances of 'struct pci_ops', and 67 of them treat type0 and type1
> > access differently in some form.
> >
> > I'd estimate that about half of them, or roughly a third of the total
> > instances would benefit from my change, if we were to do them again.
> > Clearly there is no need to change the existing code here when it works,
> > unless the benefit is very clear and the code is actively maintained.
> >
> > In some cases, the difference is only that the root bus has a limited
> > set of devices that are allowed to be accessed, so there would
> > likely be no benefit of this, compared to e.g. yet another callback
> > that checks the validity.
> > Some other instances have type0 registers at a different memory location
> > from type1, some use different layout inside of that space, and some
> > are completely different.
>
> The type0/type1 distinction still seems out of place to me at the call
> site. Is there any other reason a caller would care about the
> difference between type0 and type1?
The callers really shouldn't care, but they also shouldn't call the
pci_ops function pointer (and as we found earlier, there are only
three such callers).
The distinction between type0 and type1 in my mind is an implementation
detail of the pci_{read,write}_config_{byte,word,dword} functions
that call the low-level operations here.
Arnd
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-01 14:40 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Bjorn Helgaas <helgaas@kernel.org> - 2016-06-01 17:10 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-01 17:50 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Bjorn Helgaas <helgaas@kernel.org> - 2016-06-01 21:10 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-02 13:50 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Bjorn Helgaas <helgaas@kernel.org> - 2016-06-02 16:10 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-02 17:50 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-03 09:50 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Bjorn Helgaas <helgaas@kernel.org> - 2016-06-07 02:30 +0200
Re: [PATCH 1/3] pci: introduce read_bridge/write_bridge pci ops Arnd Bergmann <arnd@arndb.de> - 2016-06-07 10:20 +0200
csiph-web