Quoting Geert Uytterhoeven (2019-08-16 12:59:32) > Hi Stephen, > > On Fri, Aug 16, 2019 at 8:01 PM Stephen Boyd <sboyd@xxxxxxxxxx> wrote: > > Quoting Geert Uytterhoeven (2019-08-16 05:52:23) > > > The CPG/MSTP Clock Domain driver does not implement the > > > generic_pm_domain.power_{on,off}() callbacks, as the domain itself > > > cannot be powered down. Hence the domain should be marked as always-on > > > by setting the GENPD_FLAG_ALWAYS_ON flag. > > > > > > This gets rid of the following boot warning on RZ/A1: > > > > > > sh_mtu2 fcff0000.timer: PM domain cpg_clocks will not be powered off > > > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > > --- > > > > Are you going to add a Fixes tag? > > I didn't add a Fixes tag, as there's no clear point in history where the > problem appeared: the Clock Domain code in this driver predates the > introduction of the GENPD_FLAG_ALWAYS_ON flag by ca. 18 months. > > Candidates are: > d716f4798ff8c65a ("PM / Domains: Support IRQ safe PM domains") > ffaa42e8a40b7f10 ("PM / Domains: Enable users of genpd to specify > always on PM domains") > 075c37d59ecd4a8b ("PM / Domains: Don't warn about IRQ safe device for > an always on PM domain") > > Do you think it's worth adding one or more of the above? > Thanks! > Well is it actually a problem to not specify the flag? I guess it's just a potential problem if the genpd is ever powered off, but given that the governor decides to leave it always enabled it doesn't actually matter? So it's not really fixing anything besides silencing a harmless warning?