2009/4/21 Matthias Hopf
On Apr 17, 09 16:40:34 -0700, Yang Zhao wrote:
The wait-for-idle code for radeonhd is more fine grained and is not actually exposed in its entirety, so the current RHDSetEngineClock() and RHDSetMemoryClock() do not work reliably outside of init time. This is why DPMS-driven downclocking was not implemented.
What would you need to actually implement this correctly? I'm asking because we would probably want to increase the frequencies to maximum if 3D is active (unless some special use case is found, like composition managers).
rhdAllIdle() is internalized to rhd_driver.c, so it needs to be exposed. The name is actually inaccurate now as idling the CS needs to be done through other functions. IIRC, there's also no modularized code for bringing the CRTCs up again after rhdAllIdle() shuts them down. The non-CS idling code needs to be refactored in general to be more accomodating as there wasn't a need to have it callable from outside rhd_driver.c before.
Also, did you implement voltage regulation functions as well?
No. -- Yang Zhao http://yangman.ca -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org