[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181004134839.GZ5662@atomide.com>
Date: Thu, 4 Oct 2018 06:48:39 -0700
From: Tony Lindgren <tony@...mide.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Sudeep Holla <sudeep.holla@....com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Mark Rutland <mark.rutland@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-pm@...r.kernel.org, Kevin Hilman <khilman@...nel.org>,
Lina Iyer <ilina@...eaurora.org>,
Rob Herring <robh+dt@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 03/11] PM / Domains: Document flags for genpd
Hi,
* Ulf Hansson <ulf.hansson@...aro.org> [181003 14:43]:
> + * GENPD_FLAG_IRQ_SAFE: This informs genpd that its backend callbacks,
> + * ->power_on|off(), doesn't sleep. Hence, these
> + * can be invoked from within atomic context, which
> + * enables genpd to power on/off the PM domain,
> + * even when pm_runtime_is_irq_safe() returns true,
> + * for any of its attached devices. Note that, a
> + * genpd having this flag set, requires its
> + * masterdomains to also have it set.
> + *
Let's try to avoid adding more irq_safe stuff because of having that
propagate to the masterdomains..
I think you can just flag the power_on/off in genpd, then have cpu_pm
callbacks do it.
Regards,
Tony
Powered by blists - more mailing lists