> > Currently no other board requires this, but this is already part of the > > binding. The new stuff limits the range for a specific SoC, simply because > > that is the range supported by the control register. Not implementing, i.e. > > supporting the whole range from the property, which might get truncated, > > doesn't make much sense to me. > > With that driver we don't, but the previous design had the same > feature and it was used on more boards. It was simply initialized > statically in U-Boot, and not in Linux through the DT like it is done > here. If there are boards which do need it, then i'm fine with it. I would also prefer that Linux does set it, and don't rely on U-boot. Andrew -- 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
