All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60858] [radeon HD 4570m]  Error setting UVD clocks
Date: Mon, 09 Sep 2013 19:43:24 +0000	[thread overview]
Message-ID: <bug-60858-2300-rQejdMdkkR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60858-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=60858

--- Comment #9 from Pinak Ahuja <pinak.ahuja@gmail.com> ---
(In reply to Christian König from comment #8)
> You could dig into the code and try to figure out why the post dividers
> (vclk_div and dclk_div) turn out as 0.
> 
> The two involved functions are rv770_set_uvd_clocks which can be found here
> drivers/gpu/drm/radeon/rv770.c and radeon_uvd_calc_upll_dividers which can
> be found here drivers/gpu/drm/radeon/radeon_uvd.c.

I'll go through the code a little later and see if i can find something useful.


> The most interesting value is rdev->clock.spll.reference_freq, it is the
> reference clock frequency coming from a bios table. If that is wrong the
> whole calculation doesn't work any more and the UPLL generates an invalid
> frequency.
> 
> Insert something like DRM_ERROR("Test %d\n",
> rdev->clock.spll.reference_freq) into the code and see what it spits out on
> the next reboot.

I did this, heres the output:
[    8.346601] [drm:radeon_uvd_calc_upll_dividers] *ERROR* Test 2700

here's the full log:

http://pastebin.com/31Pe119f

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-09-09 19:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 15:16 [Bug 60858] New: [radeon HD 4570m] Error setting UVD clocks bugzilla-daemon
2013-09-05 15:20 ` [Bug 60858] " bugzilla-daemon
2013-09-05 15:23 ` bugzilla-daemon
2013-09-05 15:24 ` bugzilla-daemon
2013-09-05 15:32 ` bugzilla-daemon
2013-09-05 15:43 ` bugzilla-daemon
2013-09-05 15:55 ` bugzilla-daemon
2013-09-09  6:47 ` bugzilla-daemon
2013-09-09  8:20 ` bugzilla-daemon
2013-09-09 19:43 ` bugzilla-daemon [this message]
2013-09-15 12:31 ` bugzilla-daemon
2013-09-16  3:36 ` bugzilla-daemon
2013-09-16 15:45 ` bugzilla-daemon
2013-09-16 15:46 ` bugzilla-daemon
2013-09-16 15:56 ` bugzilla-daemon
2013-09-16 16:26 ` bugzilla-daemon
2013-09-16 16:26 ` bugzilla-daemon
2013-10-01 11:43 ` bugzilla-daemon
2013-10-01 18:47 ` bugzilla-daemon
2014-01-09  8:06 ` bugzilla-daemon
2014-01-09  9:06 ` 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-60858-2300-rQejdMdkkR@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.