Bug 38657 - Redwood: power state #4 not used
Summary: Redwood: power state #4 not used
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-24 15:45 UTC by mkgmafbt
Modified: 2019-11-19 08:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Part of dmesg with power states (5.66 KB, text/plain)
2011-06-24 15:45 UTC, mkgmafbt
no flags Details

Description mkgmafbt 2011-06-24 15:45:28 UTC
Created attachment 48390 [details]
Part of dmesg with power states

It's a Sapphire Radeon HD5670 512MB GDDR5. DRM reports 5 power states, but low profile won't use #4, wich is the 2D profile, nor does dynpm. All kernels with Evergreen pm support are affected by this (possible) bug, including 3.0-rc4.

cat /sys/class/drm/card0/device/power_profile 
low

cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 775000 kHz
current engine clock: 399990 kHz
default memory clock: 950000 kHz
current memory clock: 950000 kHz
voltage: 1100 mV
PCIE lanes: 16

(should be 150/300 MHz 0.9V)

lspci -nn | grep  VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8]
Comment 1 Alex Deucher 2011-06-28 09:00:51 UTC
The last state is a special state that is not used by default.
Comment 2 mkgmafbt 2011-06-28 09:40:38 UTC
Thanks for the reply.
Whats the purpose of this state?
Comment 3 Martin Peres 2019-11-19 08:20:52 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/198.


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.