From: Jingoo Han <jg1.han@samsung.com>
To: 'Marek Vasut' <marex@denx.de>,
'Richard Zhu' <Hong-Xing.Zhu@freescale.com>
Cc: 'Mohit KUMAR DCG' <Mohit.KUMAR@st.com>,
'Pratyush ANAND' <pratyush.anand@st.com>,
'Arnd Bergmann' <arnd@arndb.de>,
'Kishon Vijay Abraham I' <kishon@ti.com>,
linux-pci@vger.kernel.org, 'Tim Harvey' <tharvey@gateworks.com>,
'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [Query/Discussion]: IO translation with designware PCIe controller
Date: Tue, 10 Dec 2013 16:02:34 +0900 [thread overview]
Message-ID: <001201cef575$cd4fc960$67ef5c20$%han@samsung.com> (raw)
In-Reply-To: <2CC2A0A4A178534D93D5159BF3BCB66189F9536CE2@EAPEX1MAIL1.st.com>
On Tuesday, December 10, 2013 3:31 PM, Mohit KUMAR DCG wrote:
> On Tuesday, December 10, 2013 10:55 AM, Jingoo Han wrote:
> > On Tuesday, December 10, 2013 1:34 PM, Pratyush Anand wrote:
> > > On Tue, Dec 10, 2013 at 12:09:37AM +0800, Arnd Bergmann wrote:
> > > > On Monday 09 December 2013, Pratyush Anand wrote:
> > > > > > I think it does handle this correctly, look at
> > > > > >
> > > > > > static int dw_pcie_setup(int nr, struct pci_sys_data *sys) {
> > > > > > ...
> > > > > > if (global_io_offset < SZ_1M && pp->config.io_size > 0) {
> > > > > > sys->io_offset = global_io_offset - pp->config.io_bus_addr;
> > > > > > pci_ioremap_io(sys->io_offset, pp->io.start);
> > > > > > global_io_offset += SZ_64K;
> > > > > > pci_add_resource_offset(&sys->resources, &pp->io,
> > > > > > sys->io_offset);
> > > > > > }
> > > > > > ...
> > > > > > }
> > > > > >
> > > > > > I believe this does the right thing, but you have to put the
> > > > > > correct translation into the 'ranges' property of the host bridge node
> > in DT.
> > > > >
> > > > > May be not exactly. pp->io is the realio, and it is passed
> > > > > correctly to pci_add_resource_offset. But, as you had also said
> > > > > that pci_ioremap_io will receive cpu physical address space as
> > > > > input, therefore I think following modification will be needed to
> > > > > work io transaction properly.
> > > >
> > > > I see. I think you are right.
> > > >
> > > > > diff --git a/drivers/pci/host/pcie-designware.c
> > > > > b/drivers/pci/host/pcie-designware.c
> > > > > index be6ce30..cf68632 100644
> > > > > --- a/drivers/pci/host/pcie-designware.c
> > > > > +++ b/drivers/pci/host/pcie-designware.c
> > > > > @@ -378,6 +378,7 @@ int __init dw_pcie_host_init(struct pcie_port
> > *pp)
> > > > > + global_io_offset);
> > > > > pp->config.io_size = resource_size(&pp->io);
> > > > > pp->config.io_bus_addr = range.pci_addr;
> > > > > + pp->io_base = range.cpu_addr;
> > > > > }
> > > > > if (restype == IORESOURCE_MEM) {
> > > > > of_pci_range_to_resource(&range, np, &pp->mem);
> > @@ -403,7
> > > > > +404,6 @@ int __init dw_pcie_host_init(struct pcie_port *pp)
> > > > >
> > > > > pp->cfg0_base = pp->cfg.start;
> > > > > pp->cfg1_base = pp->cfg.start + pp->config.cfg0_size;
> > > > > - pp->io_base = pp->io.start;
> > > > > pp->mem_base = pp->mem.start;
> > > > >
> > > > > pp->va_cfg0_base = devm_ioremap(pp->dev, pp->cfg0_base,
> > > >
> > > > This looks correct to me and it seems to also fix a bug in
> > > > dw_pcie_prog_viewport_io_outbound if I read this correctly.
> > >
> > > Yes, now outbound viewport for IO translation will get correct input
> > > address.
> > >
> > > >
> > > > > @@ -667,7 +667,7 @@ static int dw_pcie_setup(int nr, struct
> > > > > pci_sys_data *sys)
> > > > >
> > > > > if (global_io_offset < SZ_1M && pp->config.io_size > 0) {
> > > > > sys->io_offset = global_io_offset - pp->config.io_bus_addr;
> > > > > - pci_ioremap_io(sys->io_offset, pp->io.start);
> > > > > + pci_ioremap_io(sys->io_offset, pp->io_base);
> > > > > global_io_offset += SZ_64K;
> > > > > pci_add_resource_offset(&sys->resources, &pp->io,
> > > > > sys->io_offset);
> > > >
> > > > I think there is still a related bug in here: we should pass
> > > > global_io_offset rather than sys->io_offset to pci_ioremap_io, so we
> > > > map the new window into the first available spot in the Linux view
> > > > of the I/O space, rather than passing a number that might be zero
> > > > for any bus, if the 'ranges' are set up to have an identity mapping
> > > > between Linux I/O spaces and PCI I/O spaces. You should be able to
> > > > verify this by setting the I/O range for the bus to a random 4KB
> > > > multiple in DT and observe that Linux start allocating ports from 0x1000
> > but the raw BAR values would contain the value you have chosen.
> > >
> > > OK.
> > >
> > > @ Jingoo, Mohit
>
> - Now its working properly for SPEAr1310 tested with directly connected EP(xhc cards) as well as EP
> Connected through switch(Lecroy PTC in AIC mode). Without this patch my EP devices were not working
> when
> connected through Switch.
Hi Marek, Richard,
How about testing the following Pratyush's patch on imx6 platform
with the Pericom PI7C9X2G303EL PCIe switch?
As Mohit tested, it looks to resolve the i.MX6 problem when the
PCIe switch is connected to the i.MX6 platform.
Best regards,
Jingoo Han
[.....]
diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
index be6ce30..b83f5e8 100644
--- a/drivers/pci/host/pcie-designware.c
+++ b/drivers/pci/host/pcie-designware.c
@@ -378,6 +378,7 @@ int __init dw_pcie_host_init(struct pcie_port *pp)
+ global_io_offset);
pp->config.io_size = resource_size(&pp->io);
pp->config.io_bus_addr = range.pci_addr;
+ pp->io_base = range.cpu_addr;
}
if (restype == IORESOURCE_MEM) {
of_pci_range_to_resource(&range, np, &pp->mem);
@@ -403,7 +404,6 @@ int __init dw_pcie_host_init(struct pcie_port *pp)
pp->cfg0_base = pp->cfg.start;
pp->cfg1_base = pp->cfg.start + pp->config.cfg0_size;
- pp->io_base = pp->io.start;
pp->mem_base = pp->mem.start;
pp->va_cfg0_base = devm_ioremap(pp->dev, pp->cfg0_base,
@@ -667,7 +667,7 @@ static int dw_pcie_setup(int nr, struct pci_sys_data *sys)
if (global_io_offset < SZ_1M && pp->config.io_size > 0) {
sys->io_offset = global_io_offset - pp->config.io_bus_addr;
- pci_ioremap_io(sys->io_offset, pp->io.start);
+ pci_ioremap_io(global_io_offset, pp->io_base);
global_io_offset += SZ_64K;
pci_add_resource_offset(&sys->resources, &pp->io,
sys->io_offset);
next prev parent reply other threads:[~2013-12-10 7:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 5:04 [Query/Discussion]: IO translation with designware PCIe controller Pratyush Anand
2013-12-05 21:33 ` Arnd Bergmann
2013-12-06 9:12 ` Pratyush Anand
2013-12-06 14:46 ` Arnd Bergmann
2013-12-09 7:12 ` Pratyush Anand
2013-12-09 16:09 ` Arnd Bergmann
2013-12-10 4:34 ` Pratyush Anand
2013-12-10 5:25 ` Jingoo Han
2013-12-10 6:31 ` Mohit KUMAR DCG
2013-12-10 6:57 ` Pratyush Anand
2013-12-10 7:02 ` Jingoo Han [this message]
2013-12-13 7:36 ` Hong-Xing.Zhu
2013-12-10 13:26 ` Marek Vasut
2013-12-10 22:22 ` Jingoo Han
2013-12-10 23:23 ` Tim Harvey
2013-12-10 23:25 ` Marek Vasut
2013-12-10 23:58 ` Jingoo Han
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001201cef575$cd4fc960$67ef5c20$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=Hong-Xing.Zhu@freescale.com \
--cc=Mohit.KUMAR@st.com \
--cc=arnd@arndb.de \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=pratyush.anand@st.com \
--cc=tharvey@gateworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).