[PATCH 24/32] pci: PCIe driver for Marvell Armada 370/XP systems
Jason Gunthorpe
jgunthorpe at obsidianresearch.com
Wed Mar 13 02:57:49 EST 2013
On Tue, Mar 12, 2013 at 08:08:52AM +0100, Thierry Reding wrote:
> So to recapitulate, we agree that configuration space can be translated
> through the "ranges" property. That means the only missing link is a new
> function to translate not only "assigned-addresses" but also the "reg"
> property for PCI devices. Is that it?
No, the first conclusion is that placing a config space in ranges is
against the language in the current spec (see section 12).
The second conclusion is that there is probably a way forward to
update the spec in a backwards compatible way to model ECAM, but would
require more analysis.
Finally, there was no objections to the approach in Thomas's patch,
other than the note to fix the '@1,0' and the extra device_type="pci"
..
> And for Marvell the non-configuration-space per-root-port registers need
> to be mapped separately from the configuration space windows?
No, there are no configuration space windows on Marvell, so only one mapping.
Regards,
Jason
More information about the devicetree-discuss
mailing list