Thread (1 message) 1 message, 1 author, 2016-07-15

Purpose of pci_remap_iospace

From: arnd@arndb.de (Arnd Bergmann)
Date: 2016-07-15 06:56:39
Also in: linux-pci, lkml

On Friday, July 15, 2016 5:21:20 AM CEST Bharat Kumar Gogada wrote:
quoted
On Thu, Jul 14, 2016 at 01:32:13PM +0000, Bharat Kumar Gogada wrote:

[...]
quoted
Hi Lorenzo,

I missed something in my device tree now I corrected it.

ranges = <0x01000000 0x00000000 0xe0000000 0x00000000 0xe0000000 0
0x00010000   //io

You have not missed anything, you changed the PCI bus address at which
your host bridge responds to IO space and it must match your configuration.
At what PCI bus address your host bridge maps IO space ?
Our host bridge does not have dedicted address space mapped for IO transactions.
For generation of IO transactions it requires some register read and write operations
in bridge logic.

So the above PCI address does not come in to picture also, is there alternate way to handle IO
Bars with our kind of hardware architecture.
Hisilicon has a similar thing on one of their LPC bridges, and
Rongrong Zou has implemented something for it in the past, but I
think it never got merged.

https://lkml.org/lkml/2015/12/29/154 has one version of his
proposal, not sure if that was the latest one or if something
newer exists.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help