[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230809072330.GB11676@atomide.com>
Date: Wed, 9 Aug 2023 10:23:30 +0300
From: Tony Lindgren <tony@...mide.com>
To: Kevin Hilman <khilman@...nel.org>
Cc: Dhruva Gole <d-gole@...com>, Andrew Davis <afd@...com>,
Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
Santosh Shilimkar <ssantosh@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, Viresh Kumar <viresh.kumar@...aro.org>,
Praneeth Bajjuri <praneeth@...com>,
Dave Gerlach <d-gerlach@...com>,
Vibhore Vardhan <vibhore@...com>, Georgi Vlaev <g-vlaev@...com>
Subject: Re: [PATCH V6 4/4] firmware: ti_sci: Introduce system suspend resume
support
* Kevin Hilman <khilman@...nel.org> [230809 00:20]:
> To me, it sounds like you might want to use ->resume_early() or maybe
> ->resume_noirq() in the pinctrl driver for this so that IO isolation can
> be disabled sooner?
For calls that need to happen just before the SoC is disabled or first
thing on resume path, cpu_cluster_pm_enter() and cpu_cluster_pm_exit()
notifiers work nice and allow distributing the code across the related
SoC specific code and device drivers. See for example the usage in
drivers/irqchip/irq-gic.c for CPU_CLUSTER_PM_ENTER.
Regards,
Tony
Powered by blists - more mailing lists