Re: strange dtc errors after adding sram node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Monday 25 April 2016 08:04:53 Stefan Wahren wrote:
> >>>                     reg = <0x80080000 0x10000>;
> >>
> >> Follwing the address map for the i.MX28 (p. 125ff) the AHB is mapped
> >> to
> >> different start addresses:
> >>
> >> Bus  MNEMONIC        START ADDRESS
> >> --------------------------------------
> >> AHB  OCRAM           0x00000000
> >> AHB  USBCTRL0        0x80080000
> >> AHB  OCROM           0xC0000000
> >>
> >> So instead of replacing ahb@80080000 by ahb@00000000 a new node
> >> should
> >> be created. However, I am not sure if this is really necessary, I
> >> haven't seen it for all device trees using "mmio-sram".
> >
> > Sorry, for not looking carefully enough at your patch. Haven't seen you
> > adjusted the 'reg' property. I tried with an additional ahb@00000000 no
> > de and this did work.
> >
> > So, there is really something odd here...
> 
> i've found reason for these errors. I missed to adjust the affected dts 
> files which refer to the ahb node.

Makes sense. Maybe you can just remove the address and 'reg' property from
the ahb node? That should solve the dtc problem and make the contents
more like what we have elsewhere.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux