Hi Linus, On Thu, Feb 22, 2018 at 3:23 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven > <geert+renesas@xxxxxxxxx> wrote: > >> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable >> when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO >> block's module clock (if exists) is manually kept running during system >> suspend, to make sure the device stays active. >> >> However, this explicit clock handling is merely a workaround for a >> failure to properly communicate wakeup information to the device core. >> >> Instead, set the device's power.wakeup_path field, to indicate this >> device is part of the wakeup path. Depending on the PM Domain's >> active_wakeup configuration, the genpd core code will keep the device >> enabled (and the clock running) during system suspend when needed. >> This allows for the removal of all explicit clock handling code from the >> driver. >> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > Acked-by: Linus Walleij <linus.walleij@xxxxxxxxxx> > > Can I apply this and only this patch to GPIO? Yes please. > Should it be applied for fixes, next? No, as it depends on infrastructure (device_set_wakeup_path()) and fixes (various "Keep wakeup sources active during system suspend") in v4.16-rc1. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- 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