On Saturday 15 March 2014, Tanmay Inamdar wrote:
> On Fri, Mar 14, 2014 at 5:07 AM, Arnd Bergmann <a...@arndb.de> wrote:
> > On Thursday 06 March 2014, Tanmay Inamdar wrote:
> >> + pcie0: pcie@1f2b0000 {
> >> + status = "disabled";
> >> + device_type = "pci";
> >> + compatible = "apm,xgene-storm-pcie",
> >> "apm,xgene-pcie";
> >> + #interrupt-cells = <1>;
> >> + #size-cells = <2>;
> >> + #address-cells = <3>;
> >> + reg = < 0x00 0x1f2b0000 0x0 0x00010000 /*
> >> Controller registers */
> >> + 0xe0 0xd0000000 0x0 0x00200000>; /* PCI
> >> config space */
> >> + reg-names = "csr", "cfg";
> >> + ranges = <0x01000000 0x00 0x00000000 0xe0 0x00000000
> >> 0x00 0x00010000 /* io */
> >> + 0x02000000 0x00 0x10000000 0xe0 0x10000000
> >> 0x00 0x80000000>; /* mem */
> >> + dma-ranges = <0x42000000 0x40 0x00000000 0x40
> >> 0x00000000 0x40 0x00000000>;
> >> + interrupt-map-mask = <0x0 0x0 0x0 0x7>;
> >> + interrupt-map = <0x0 0x0 0x0 0x1 &gic 0x0 0xc2 0x1
> >> + 0x0 0x0 0x0 0x2 &gic 0x0 0xc3 0x1
> >> + 0x0 0x0 0x0 0x3 &gic 0x0 0xc4 0x1
> >> + 0x0 0x0 0x0 0x4 &gic 0x0 0xc5 0x1>;
> >> + clocks = <&pcie0clk 0>;
> >> + };
> >
> > Is 0x40.0x00000000 the start of your RAM? I had expected RAM to start at
> > 0.0,
> > and in that case the dma-ranges property would be wrong.
>
> RAM starting address is 0x40_00000000.
Ok, it's good then. Thanks for the clarification, I keep losing track of how
each of
the ~40 SoCs I'm dealing with handles these things.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
