Hi Ulf,
On Thu, Apr 4, 2019 at 10:55 AM Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote:
> On Wed, 20 Mar 2019 at 11:39, Geert Uytterhoeven
> <geert+renesas@xxxxxxxxx> wrote:
> > If a device is part of the wake-up path, it should indicate this by
> > setting its power.wakeup_path field. This allows the genpd core code to
> > keep the device enabled during system suspend when needed.
> >
> > As regulators powering devices are not handled by genpd, the driver
> > handles these itself, and thus must skip regulator control when the
> > device is part of the wake-up path.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
> > ---
> > Note that I don't really need this on the Renesas Ebisu-4D board, as
> > there is no regulator or PM Domain controlling power to the GPIO
> > expander on that board. I did want to have all wake-up path processing
> > implemented in the driver for completeness, and did test its behavior
> > with gpio-keys configured as a wake-up source.
>
> All above makes perfect sense to me.
> Reviewed-by: Ulf Hansson <ulf.hansson@xxxxxxxxxx>
Thanks!
> > However, while this approach is known to work fine on other boards, with
> > other GPIO and interrupt controllers (gpio-rcar, irq-renesas-irqc,
> > irq-renesas-intc-irqpin), it wouldn't work on Ebisu-4D, due to different
> > device suspend ordering.
> >
> > The proper ordering is:
> > 1. When gpio-keys is suspended, its suspend handler calls
> > enable_irq_wake(), invoking pca953x_irq_set_wake(), and causing
> > pca953x_chip.wakeup_path to be incremented,
> > 2. When gpio-pca953x is suspended, it checks pca953x_chip.wakeup_path,
> > and marks the device to be part of the wake-up path.
>
> Right.
>
> >
> > However, gpio-keys is suspended _after_ gpio-pca953x, breaking the
> > scheme :-(
>
> Would it make sense to fixup the ordering issue via creating a
> parent/child relationship or setting up a device link?
Could that be due to gpio_keys not having rudimentary Runtime PM support?
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
