Le 19/01/2015 11:30, Ludovic Desroches a écrit : > On Mon, Jan 19, 2015 at 11:12:45AM +0100, Linus Walleij wrote: >> On Wed, Jan 14, 2015 at 4:03 PM, Ludovic Desroches >> <ludovic.desroches@xxxxxxxxx> wrote: >> >>> From my point of view, it is two distinct topics. One is a very >>> important fix because our SAMA5D4 device is not booting without it. The >>> other one is a proper way to manage gpio ranges but alone I don't think >>> it can solve my issue. >> >> Can you make me a minimal, sane patch that fixes the boot regression? >> >> I hate regressions so these need to be fixed first... >> >> The rest we can discuss I guess. >> >> Or is it not possible to solve the boot regression without the larger >> fix? > > No I don't think we can have a smaller patch than this one to fix it. > Next step is to decide if we go further as you suggested, knowing that we > would have to modify the device tree. Moreover we will have to rework > our pinctrl driver (or write a new one) since we will have new pio > controller on future devices. Yes, all the upcoming AT91 SoCs will embed a totally new pinctrl/pinmux IP. We will write a new driver for it and we will be able to use the up-to-date standards of the framework. In the meantime, this fix allows us to use the SAMA5D4 without too much changes to the original version of our current driver and without modification to all the current SoCs device trees. Bye, -- Nicolas Ferre -- 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
