On Thu, Aug 22, 2019 at 4:09 PM Ulf Hansson <[email protected]> wrote:
> On Fri, 16 Aug 2019 at 14:52, Geert Uytterhoeven
> <[email protected]> wrote:
> > The Renesas Clock Domain drivers do not implement the
> > generic_pm_domain.power_{on,off}() callbacks, as the domains themselves
> > cannot be powered down. Hence the domains should be marked as always-on
> > by setting the GENPD_FLAG_ALWAYS_ON flag.
> >
> > This patch series that issue for R-Car M1A, RZ/A1, RZ/A2, and
> > RZ/N1 SoCs.
> > SH/R-Mobile SoCs are fixed in "[PATCH] soc: renesas: rmobile-sysc: Set
> > GENPD_FLAG_ALWAYS_ON for always-on domain"
> > (https://lore.kernel.org/linux-renesas-soc/[email protected]/T/#u).
> > R-Car H1, Gen2, and Gen3 SoCs do not need a fix, as these SoCS use the
> > R-Car SYSC driver for Clock Domain creation, which already sets the
> > flag.
> >
> > To be queued in clk-renesas for v5.4.
> >
> > Thanks!
> >
> > Geert Uytterhoeven (3):
> > clk: renesas: mstp: Set GENPD_FLAG_ALWAYS_ON for clock domain
> > clk: renesas: r9a06g032: Set GENPD_FLAG_ALWAYS_ON for clock domain
> > clk: renesas: cpg-mssr: Set GENPD_FLAG_ALWAYS_ON for clock domain
> >
> > drivers/clk/renesas/clk-mstp.c | 3 ++-
> > drivers/clk/renesas/r9a06g032-clocks.c | 3 ++-
> > drivers/clk/renesas/renesas-cpg-mssr.c | 3 ++-
> > 3 files changed, 6 insertions(+), 3 deletions(-)
> >
>
> Feel free to add:
>
> Reviewed-by: Ulf Hansson <[email protected]>
Thanks, queuing in clk-renesas-for-v5.4, with enhanced commit description:
... to prevent the core PM Domain code from considering it for power-off,
and doing unnessary processing.
for all three of them, and
This also gets rid of a boot warning when the Clock Domain contains an
IRQ-safe device, e.g. on RZ/A1:
for the first patch.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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
