On Wed, Mar 11, 2015 at 6:49 PM, Nicolas Schichan <[email protected]> wrote:
> Moving the bcm63xx_gpio_init() call from board_prom_init() to > bcm63xx_register_devices() (an arch_initcall) is enough to get called when > kmalloc is working. If code poking GPIOs is invoked earlier by a board code, > it will have to move in the board_register_devices() function though there > doesn't seem to any problems with the mainline bcm63xx board code in that > regard. > > I can produce a patch for that if it is an accepted solution. It has the > advantage of not requiring changes to the gpiolib code. It would be *awesome* if you can come up with a patch like this. Because it makes our life so much more simple. (Maybe there is already such a patch in my INBOX somewhere...) Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
