On Tue, Sep 11, 2018 at 9:38 PM Fabio Estevam <festevam@xxxxxxxxx> wrote: > > Hi Rob, > > On Tue, Sep 11, 2018 at 6:54 PM, Rob Herring <robh@xxxxxxxxxx> wrote: > > It appears that many i.MX platforms have duplicate, incomplete memory > > nodes with both "memory" and "memory@<addr>" nodes. Are you all aware > > of this? Plan to fix it? I guess u-boot fixes things enough to work. > > I was not aware. > > I spent some time fixing all the memory node errors reported by dtc with W=1. Unfortunately, dtc is not catching it because we have 'memory' with just device_type and 'memory@<addr>' with reg. > Any suggestions on how to fix the remaining issues? Make sure every memory@<addr> has device_type added and remove the 'memory' nodes. > Also, how can I trigger such warnings? Install the schema tools: pip3 install git+https://github.com/robherring/yaml-bindings.git@master --process-dependency-links Use this kernel branch with the build support: https://github.com/robherring/linux/commits/yaml-bindings And this dtc: https://github.com/robherring/dtc/tree/yaml Rob
