From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 73378] [drm:radeon_uvd_send_upll_ctlreq] *ERROR* Timeout setting UVD clocks! Date: Sun, 15 Feb 2015 10:12:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0303868229==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4A8BD6E3EC for ; Sun, 15 Feb 2015 02:12:49 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0303868229== Content-Type: multipart/alternative; boundary="1423995169.68A03.27081"; charset="UTF-8" --1423995169.68A03.27081 Date: Sun, 15 Feb 2015 10:12:49 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D73378 --- Comment #32 from Christian K=C3=B6nig --- (In reply to Chernovsky Oleg from comment #31) > Tried to launch vdpau-accelerated mpv with fglrx driver and mmiotrace. > Interesting, the CG_UPLL_FUNC_CNTL always has flags 0x100 | 0x600 >=20 > R 4 456.556542 1 0xf0000634 0x707 0x0 0 > W 4 456.556547 1 0xf0000634 0x705 0x0 0 > R 4 456.556553 1 0xf0000634 0x705 0x0 0 > W 4 456.556576 1 0xf0000634 0x705 0x0 0 > R 4 456.556688 1 0xf0000634 0x705 0x0 0 > W 4 456.556693 1 0xf0000634 0x705 0x0 0 > R 4 456.556709 1 0xf0000634 0x705 0x0 0 > R 4 456.556725 1 0xf0000634 0x705 0x0 0 > W 4 456.556730 1 0xf0000634 0x705 0x0 0 > R 4 456.556771 1 0xf0000634 0x705 0x0 0 > W 4 456.556776 1 0xf0000634 0x704 0x0 0 > R 4 456.556837 1 0xf0000634 0x704 0x0 0 > W 4 456.556842 1 0xf0000634 0x700 0x0 0 > W 4 456.556847 1 0xf0000634 0x708 0x0 0 >=20 > Any ideas what can 0x100 mask be for? Strange, the hardware docs say this is for routing the reset signal and shouldn't be touched by the driver, e.g. it should always be 1. Is that bit 0 when you use the open source driver? --=20 You are receiving this mail because: You are the assignee for the bug. --1423995169.68A03.27081 Date: Sun, 15 Feb 2015 10:12:49 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 32 on bug 73378<= /a> from Christian K=C3=B6nig 
(In reply to Chernovsky Oleg from comment #31)
> Tried to launch vdpau-accelerated mpv with fglrx=
 driver and mmiotrace.
> Interesting, the CG_UPLL_FUNC_CNTL always has flags 0x100 | 0x600
>=20
> R 4 456.556542 1 0xf0000634 0x707 0x0 0
> W 4 456.556547 1 0xf0000634 0x705 0x0 0
> R 4 456.556553 1 0xf0000634 0x705 0x0 0
> W 4 456.556576 1 0xf0000634 0x705 0x0 0
> R 4 456.556688 1 0xf0000634 0x705 0x0 0
> W 4 456.556693 1 0xf0000634 0x705 0x0 0
> R 4 456.556709 1 0xf0000634 0x705 0x0 0
> R 4 456.556725 1 0xf0000634 0x705 0x0 0
> W 4 456.556730 1 0xf0000634 0x705 0x0 0
> R 4 456.556771 1 0xf0000634 0x705 0x0 0
> W 4 456.556776 1 0xf0000634 0x704 0x0 0
> R 4 456.556837 1 0xf0000634 0x704 0x0 0
> W 4 456.556842 1 0xf0000634 0x700 0x0 0
> W 4 456.556847 1 0xf0000634 0x708 0x0 0
>=20
> Any ideas what can 0x100 mask be for?

Strange, the hardware docs say this is for routing the reset signal and
shouldn't be touched by the driver, e.g. it should always be 1.

Is that bit 0 when you use the open source driver?

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1423995169.68A03.27081-- --===============0303868229== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0303868229==--