On Tue, 16 Jul 2019 at 17:53, Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> wrote: > > On Mon, May 13, 2019 at 09:22:56PM +0200, Ulf Hansson wrote: > > When the hierarchical CPU topology layout is used in DT, let's allow the > > CPU to be power managed through its PM domain, via deploying runtime PM > > support. > > > > To know for which idle states runtime PM reference counting is needed, > > let's store the index of deepest idle state for the CPU, in a per CPU > > variable. This allows psci_cpu_suspend_enter() to compare this index with > > the requested idle state index and then act accordingly. > > I do not see why a system with two CPU CPUidle states, say CPU retention > and CPU shutdown, should not be calling runtime PM on CPU retention > entry. If the CPU idle governor did select the CPU retention for the CPU, it was probably because the target residency for the CPU shutdown state could not be met. In this case, there is no point in allowing any other deeper idle states for cluster/package/system, since those have even greater residencies, hence calling runtime PM doesn't make sense. > > The question then is what cluster/package/system states > are allowed for a given CPU idle state, to understand > what idle states can be actually entered at any hierarchy > level given the choice made for the CPU idle state. > > In the case above, a CPU entering retention state should prevent > runtime PM selecting a cluster shutdown state; most likely firmware > would demote the request to cluster retention but still, we should > find a way to describe these dependencies. See above. [...] Kind regards Uffe
