Re: [PATCH 0/2] cpufreq/opp: rework regulator initialization

From: Sudeep Holla
Date: Fri Feb 08 2019 - 06:01:08 EST

On Thu, Feb 07, 2019 at 01:22:25PM +0100, Marek Szyprowski wrote:
> Dear All,
> This is a scenario that triggers the above issue:


> 1. system disables non-boot cpu's at the end of system suspend procedure,
> 2. this in turn deinitializes cpufreq drivers for the disabled cpus,
> 3. early in the system resume procedure all cpus are got back to online
> state,
> 4. this in turn causes cpufreq to be initialized for the newly onlined
> cpus,
> 5. cpufreq-dt acquires all its resources (clocks, regulators) during
> ->init() callback,

This is strictly not just restricted to cpufreq-dt, but to any driver
supporting multiple policies. So we need a generic fix not just
cpufreq-dt specific.