Geert Uytterhoeven <geert+rene...@glider.be> writes: > PM QoS device start/stop and save/restore state latencies are more or > less properties of the hardware. > In legacy code, they're specified from platform code. > On DT platforms, their values should come from DT. > > Signed-off-by: Geert Uytterhoeven <geert+rene...@glider.be> > --- > Should these properties be called "linux,*-latency"?
Hmm, the start/stop latencies are clearly properties of the hardware, but the save/restore latencies seem to be a function of the driver. e.g., some drivers may keep a shadow copy of their registers in memory so the save time is minimized. I don't have too strong of an opinion on this, but probably the drivers should just add their own values to the start/stop latencies to add the linux specific overhead. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
