On Mon, Sep 18, 2017 at 6:52 PM, Rob Herring <robh@xxxxxxxxxx> wrote: > In theory yes, but reality is pretty much everyone follows it. There's > no other way to specify active high vs. low for example. Furthermore, > if someone wanted to do flags in their own custom way, that would > still work. It is still the controller (or GPIO core) that interprets > the flags, not the client. > > This is a new binding, so only new DT will have it and we can apply > new standards. I'd like to get a picture of any one-cell GPIO DTS:es and/or drivers still around. I would like to deal with them somehow. When we started the big DT migration this was one of the areas we made some screwups in, admittedly, but someone just has to go first, and that was incidentally GPIO controllers. At this time people were even playing around with DT bindings in BNF form, which is why the GPIO binding is a bit .. esoteric at times. I guess I should fix that. Yours, Linus Walleij -- 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
