Bug 21234

Summary: clockgating doesnt reset to default clock after getting back from lowpower mode
Product: xorg Reporter: Paulo Dias <paulo.miguel.dias>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Paulo Dias 2009-04-16 12:32:07 UTC
New bug, since clockgating works now for my rs482, dynamicPM is able to lower my core to 71MHz when i'm on battery mode, BUT when i put the AC back, the clock stays at 71Mhz instead of going up to 400 and plus MHz.
Also, when the DPMS is activated, dynamicpm lowers the core to 71MHz again, but when it should reset it to the default, it stays again at 71MHz.

So, dynamic can lower but can't restore the default state.
im using rovclock to restore the clock back to 4xxMhz, till a fix emerges.

best regards.
Comment 1 Alex Deucher 2009-04-16 12:58:55 UTC
The DynamicPM option only changes the power state when the screens are blank (DPMS active).  If you are getting changes in power states on AC/DC changes, then something else is messing with the chip, perhaps the bios.
Comment 2 Paulo Dias 2009-04-16 13:26:04 UTC
(In reply to comment #1)
> The DynamicPM option only changes the power state when the screens are blank
> (DPMS active).  If you are getting changes in power states on AC/DC changes,
> then something else is messing with the chip, perhaps the bios.
> 

I believe you but if its so, the bios wasn't changing anything before i activated the clockgating. anyway, i can confirm the same behaviour when the dpms is activated (back to 71Mhz), doesn't restore the default when the screen comes back.

best regards and keep up the good work 
Comment 3 Alex Deucher 2009-04-16 13:47:07 UTC
Should be fixed now:
efa1476fc0765b53298624198137dc5cc71d37a8
Comment 4 Paulo Dias 2009-04-16 14:06:24 UTC
(In reply to comment #3)
> Should be fixed now:
> efa1476fc0765b53298624198137dc5cc71d37a8
> 

Hum.. :P well.. now it stays at 4xxMhz even with dpms more on.

also, now when i go into batery mode it doesnt go down to 71Mhz.

Strange indeed. any more fixes? :)

best regards
Comment 5 Paulo Dias 2009-04-16 14:07:17 UTC
im reopening it, since the behaviour just switched sides, didnt fix it , sorry
Comment 6 Paulo Dias 2009-04-16 14:37:06 UTC
 ok, i can confirm it does work, strange it doesnt change frequency when dpms is called with vbetool, like i was doing. sorry, my mistake.

groo@kerberos:~$ sleep 5; xset dpms force off; sudo sh -c 'rovclock -i'
Radeon overclock 0.6e by Hasw (hasw@hasw.net)

Found ATI card on 01:05, device id: 0x5975
I/O base address: 0x9000
Video BIOS shadow found @ 0xc0000
Reference clock from BIOS: 14.32 MHz
Memory size: 131072 kB
Memory channels: 0, CD,CH only: 0
tRcdRD: 3
tRcdWR: 1
tRP: 3
tRAS: 6
tRRD: 1
tR2W-CL: 1
tWR: 1
tW2R: 0
tW2Rsb: 0
tR2R: 1
tRFC: 13
tWL(0.5): 0
tCAS: 0
tCMD: 0
tSTR: 0
XTAL: 14.32 MHz, RefDiv: 6

Core: 71.60 MHz, Mem: 0.0 MHz
groo@kerberos:~$ sudo sh -c 'rovclock -i'
Radeon overclock 0.6e by Hasw (hasw@hasw.net)

Found ATI card on 01:05, device id: 0x5975
I/O base address: 0x9000
Video BIOS shadow found @ 0xc0000
Reference clock from BIOS: 14.32 MHz
Memory size: 131072 kB
Memory channels: 0, CD,CH only: 0
tRcdRD: 3
tRcdWR: 1
tRP: 3
tRAS: 6
tRRD: 1
tR2W-CL: 1
tWR: 1
tW2R: 0
tW2Rsb: 0
tR2R: 1
tRFC: 13
tWL(0.5): 0
tCAS: 0
tCMD: 0
tSTR: 0
XTAL: 14.32 MHz, RefDiv: 6

Core: 300.72 MHz, Mem: 0.0 MHz
Edit/Delete Message
Comment 7 Alex Deucher 2009-04-16 15:33:28 UTC
(In reply to comment #6)
>  ok, i can confirm it does work, strange it doesnt change frequency when dpms
> is called with vbetool, like i was doing. sorry, my mistake.

Don't use vbetool.  It goes behind the driver's back and messes with the hardware directly.  The same is true of other apps and utilities that bang on the hw directly.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.