[PATCH 0/3] PM / Domains: Fix device stop and domain power off governor functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi all,

It turns out that the PM domains device stop and domain power off governor
functions I invented some time ago don't really make sense, because they
should only decide whether or not the resulting low-power state will be
too deep and that only depends on latencies.  In particular, the time
when devices have been suspended doesn't really matter here, so the
results returned by those functions shouldn't depend on it either (as it
shouldn't depend on any "break even" values that only make sense when we
know how much time in advance the device is going to be used, but this
information is not related to the PM QoS latency constraint).

If this functions are fixed (patches [1/3] and [2/3]), then some ugly
computations can be removed from rpm_suspend() and other places and the
whole framework can be simplified quite a bit (patch [3/3]).

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-sh" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux OMAP]     [Linux USB Devel]     [Linux ARM Kernel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [X.Org]

Add to Google Powered by Linux