From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73378] [drm:radeon_uvd_send_upll_ctlreq] *ERROR* Timeout setting UVD clocks!
Date: Sat, 31 Jan 2015 10:18:06 +0000 [thread overview]
Message-ID: <bug-73378-502-dCaGrGhMgc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73378-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1104 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73378
--- Comment #24 from Christian König <deathsimple@vodafone.de> ---
(In reply to Chernovsky Oleg from comment #23)
> Wow! Pls forget my last comment completely.
>
> Just tried to watch H264 video and it was slow as hell :(
Which is the espected result if you don't setup the clocks :)
In this case the UVD block runs with the default 100Mhz instead of the desired
400,500,900 or whatever the power tables say we should programm it to. At least
we now knew that the input frequency works well.
Now take a look at si_set_uvd_clocks in si.c. Especially try to figure out if
the first or the second call to radeon_uvd_send_upll_ctlreq fails.
Additional to that please install radeontool and get me the content of the
CG_UPLL_* registers. E.g. I need the output of:
radeontool regmatch 0x634
radeontool regmatch 0x638
radeontool regmatch 0x63c
radeontool regmatch 0x644
radeontool regmatch 0x648
radeontool regmatch 0x650
Thanks,
Christian.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2015 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-31 10:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 1:38 [Bug 73378] New: [UVD] uvd cannot enable on my RadeonHD7870 bugzilla-daemon
2014-01-08 1:49 ` [Bug 73378] [UVD] uvd cannot decode h264 or vc1 " bugzilla-daemon
2014-01-08 1:50 ` [Bug 73378] [radeonsi] " bugzilla-daemon
2014-01-09 9:54 ` [Bug 73378] [drm:radeon_uvd_send_upll_ctlreq] *ERROR* Timeout setting UVD clocks! bugzilla-daemon
2014-01-09 9:57 ` bugzilla-daemon
2014-03-23 19:09 ` bugzilla-daemon
2014-03-23 19:10 ` bugzilla-daemon
2014-03-24 14:45 ` bugzilla-daemon
2014-05-05 8:04 ` bugzilla-daemon
2014-05-05 13:22 ` bugzilla-daemon
2014-05-14 22:00 ` bugzilla-daemon
2014-10-12 20:40 ` bugzilla-daemon
2014-10-12 20:41 ` bugzilla-daemon
2014-10-12 20:49 ` bugzilla-daemon
2014-12-07 15:20 ` bugzilla-daemon
2014-12-08 15:52 ` bugzilla-daemon
2014-12-26 12:25 ` bugzilla-daemon
2014-12-26 12:37 ` bugzilla-daemon
2015-01-28 17:29 ` bugzilla-daemon
2015-01-28 18:35 ` bugzilla-daemon
2015-01-28 18:47 ` bugzilla-daemon
2015-01-28 20:44 ` bugzilla-daemon
2015-01-28 21:43 ` bugzilla-daemon
2015-01-29 10:44 ` bugzilla-daemon
2015-01-30 20:13 ` bugzilla-daemon
2015-01-30 23:35 ` bugzilla-daemon
2015-01-30 23:43 ` bugzilla-daemon
2015-01-31 10:18 ` bugzilla-daemon [this message]
2015-01-31 22:19 ` bugzilla-daemon
2015-01-31 23:33 ` bugzilla-daemon
2015-02-01 10:10 ` bugzilla-daemon
2015-02-01 11:01 ` bugzilla-daemon
2015-02-05 22:36 ` bugzilla-daemon
2015-02-06 9:19 ` bugzilla-daemon
2015-02-15 9:37 ` bugzilla-daemon
2015-02-15 10:12 ` bugzilla-daemon
2015-02-15 11:09 ` bugzilla-daemon
2015-02-15 11:12 ` bugzilla-daemon
2015-02-16 17:21 ` bugzilla-daemon
2015-02-16 17:56 ` bugzilla-daemon
2015-02-16 21:15 ` bugzilla-daemon
2015-02-18 20:53 ` bugzilla-daemon
2015-02-19 8:43 ` bugzilla-daemon
2015-03-10 19:46 ` bugzilla-daemon
2015-03-11 8:29 ` bugzilla-daemon
2015-03-22 11:42 ` bugzilla-daemon
2015-03-23 14:29 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-73378-502-dCaGrGhMgc@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox