On May 29, 09 09:40:13 -0400, Alex Deucher wrote:
This is the tricky part of power management. You need to slow the clock at the right times otherwise you can negatively impact the user experience. If you are going to run with reduced clocks you need to take into account the bandwidth requirements (display controllers, 2D engine, 3D engine, overlays, etc.) and latency requirements (frame has to be rendered in this amount of time). That's why the best place for
Also note that we're doing *no* bandwidth requirement calculation at the moment. They tend to be tricky. So the best we can do for calculating memory speeds is guessing. Which is a contradiction by itself.
power management will be in the new kms drm since only there does the driver have the full view of the hw (modesetting and command streams) so that it can change the clocks on demand in response to the current demands of the chip.
Also note that AFAIK there is no interface for that defined yet.
Matthias
--
Matthias Hopf