On Fri, Apr 21, 2017 at 11:19 AM, Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote: > I clearly don't want to block this, but I believe this is a very good > illustration of why stable DT bindings simply don't work. We are > realizing here that having each GPIO bank represented as a separate DT > node doesn't work, because this blinking functionality is not per GPIO > bank, but global to all GPIO banks. > > I am totally fine with compromise, and having things simple first, and > extend them later if needed. But this stable DT binding rule makes this > quite impossible: what is a compromise today might put you in big > troubles tomorrow. Really "stable bindings" I never believed in. It's just a pipe dream. Well they might become stable when the system is "finished" whenever that happens. I think a better rationale is that of the IETF: "rough consensus and running code", make deployed DTs work, if they are not deployed, or only getting deployed together with the kernel, changing the bindings are not a problem. 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
