Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1589365
| From | Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 13/20] PCI: iproc-platform: update PCI config space remap function |
| Date | 2017-02-28 12:10 +0100 |
| Message-ID | <tfNPk-3Bl-17@gated-at.bofh.it> (permalink) |
| References | <tfvfH-7o7-3@gated-at.bofh.it> <tfvfJ-7o7-39@gated-at.bofh.it> <tfBuO-38U-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Ray,
On Mon, Feb 27, 2017 at 01:21:39PM -0800, Ray Jui wrote:
> Hi Lorenzo,
>
> On 2/27/2017 7:14 AM, Lorenzo Pieralisi wrote:
> > PCI configuration space should be mapped with a memory region type that
> > generates on the CPU host bus non-posted write transations. Update the
> > driver to use the devm_pci_remap_cfg* interface to make sure the correct
> > memory mappings for PCI configuration space are used.
> >
> > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > Cc: Ray Jui <rjui@broadcom.com>
> > Cc: Jon Mason <jonmason@broadcom.com>
> > ---
> > drivers/pci/host/pcie-iproc-platform.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/host/pcie-iproc-platform.c b/drivers/pci/host/pcie-iproc-platform.c
> > index f4909bb..b48d0db 100644
> > --- a/drivers/pci/host/pcie-iproc-platform.c
> > +++ b/drivers/pci/host/pcie-iproc-platform.c
> > @@ -67,7 +67,8 @@ static int iproc_pcie_pltfm_probe(struct platform_device *pdev)
> > return ret;
> > }
> >
> > - pcie->base = devm_ioremap(dev, reg.start, resource_size(®));
> > + pcie->base = devm_pci_remap_cfgspace(dev, reg.start,
> > + resource_size(®));
>
> Note these are NOT config space registers; instead, they are host
> controller registers. iProc PCIe controller access config space
> registers indirectly through two of the controller registers instead of
> directly mapped.
Yes but IIUC those registers that allow indirection live in the address
space pointed at by pcie->base, right ? Question is whether it is fine
to access those registers through mappings resulting on posted writes
and that's a question I need your help to answer as I said in the cover
letter.
Thanks a lot for flagging this up, that's exactly the feedback I need.
Lorenzo
>
> Thanks,
>
> Ray
>
> > if (!pcie->base) {
> > dev_err(dev, "unable to map controller registers\n");
> > return -ENOMEM;
> >
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 13/20] PCI: iproc-platform: update PCI config space remap function Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2017-02-27 16:20 +0100
Re: [PATCH 13/20] PCI: iproc-platform: update PCI config space remap function Ray Jui <ray.jui@broadcom.com> - 2017-02-27 23:00 +0100
Re: [PATCH 13/20] PCI: iproc-platform: update PCI config space remap function Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2017-02-28 12:10 +0100
Re: [PATCH 13/20] PCI: iproc-platform: update PCI config space remap function Ray Jui <ray.jui@broadcom.com> - 2017-02-28 20:40 +0100
csiph-web