On Tue, Jul 14, 2015 at 2:05 PM, Geert Uytterhoeven <[email protected]> wrote: > On Tue, Jun 30, 2015 at 11:49 AM, Laurent Pinchart > <[email protected]> wrote:
>>> To fix this, add a "gpio-ranges" property to the gpio device node, so >>> the ranges are added by of_gpiochip_add_pin_range(), which is called by >>> of_gpiochip_add() before the call to of_gpiochip_scan_hogs(). >>> >>> Signed-off-by: Geert Uytterhoeven <[email protected]> >> >> This looks sane to me, even though referencing the same DT node seems a bit >> dodgy. I'll let Linus comment on that, but for the implementation itself, >> >> Acked-by: Laurent Pinchart <[email protected]> > > Thank you! > > Any wise words from Linus? I don't know if I'm wise but I'm OK with this: Acked-by: Linus Walleij <[email protected]> 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
