On Thursday 13 February 2014 10:22:25 Kumar Gala wrote:
> On Feb 13, 2014, at 5:07 AM, Will Deacon <will.deacon@xxxxxxx> wrote:
> > Happy to change it, but I'm also struggling for names. Maybe "linux,…"?
>
> I was thinking that as well, I’d say go with “linux,”.
I see nothing linux specific in there. I would only use that namespace
for things we don't expect to work with another OS.
> >>> +- ranges : As described in IEEE Std 1275-1994, but must provide
> >>> + at least a definition of one or both of IO and Memory
> >>> + Space.
> >>> +
> >>> +- #address-cells : Must be 3
> >>> +
> >>> +- #size-cells : Must be 2
> >>> +
> >>> +- reg : The Configuration Space base address, as accessed by the
> >>> + parent bus.
> >>
> >> Isn’t the size fixed here for cam or ecam?
> >
> > Yes, which is why reg just specifies the base address.
>
> Huh? The reg property clearly has the size in it (as shown in the example below).
> I guess I was just asking for the description here to say what the size was for
> the 2 compatibles since its fixed and known.
It's still an open question whether the config space in the reg property should
cover all 256 buses or just the ones in the bus-range. In the latter case,
it would be variable (but predictable) size.
> You could clean it up a bit to be human readable even if its kvmtool that’s creating it.
>
> pci {
> compatible = "arm,pci-cam-generic”;
> #address-cells = <3>;
> #size-cells = <2>;
> #interrupt-cells = <1>
> reg = <0x0 0x40000000>;
> ranges = <
> 0x1000000 0x0 0x00000000 0x0 0x00000000 0x0 0x00010000
> 0x2000000 0x0 0x41000000 0x0 0x41000000 0x0 0x3f000000
> >;
Make it
ranges = <0x1000000 0x0 0x00000000 0x0 0x00000000 0x0 0x00010000>,
<0x2000000 0x0 0x41000000 0x0 0x41000000 0x0 0x3f000000>;
and it will be perfect ;-)
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
