On Thu, Jan 19, 2017 at 6:41 PM, Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: > That's not true anymore. And while it's true that it reduces the > amount of maintainance on the kernel side and more on the DT side. And > from what you're constantly saying, the thing we can't plan on fixing > / upgrading is the DT, while the kernel is easy to change. > > Which means that if we ever want to fix a non-upgradable DT, the only > way to do that would be to add quirks fixing it in the kernel > itself. Adding more maintainance burden to the kernel. This is a good argument to not put groups and functions into the DT at all. If the following propositions hold: - Functions and group definitions will contain bugs - Those bugs will need to be fixed by changing the buggy definitions - It is hard to change the DTB, it is easy to change the zImage Then by logical deduction the definitions should be in the kernel to minimize maintenance burden. There is a pattern amongst firmware people that they think that they always get the group and function definitions right on first try. As long as there are humans involved in the process, this stance is provedly wrong, just use git log and you will see how much of such bugs we fix, even in drivers and DTSes produced by the vendors themselves. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html