From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations Date: Mon, 24 Mar 2014 19:40:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1956453185==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6428289CD8 for ; Mon, 24 Mar 2014 12:40:22 -0700 (PDT) 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 --===============1956453185== Content-Type: multipart/alternative; boundary="1395690022.Ba451BE51.9288"; charset="us-ascii" --1395690022.Ba451BE51.9288 Date: Mon, 24 Mar 2014 19:40:22 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=76564 --- Comment #7 from Alex Deucher --- (In reply to comment #6) > (In reply to comment #5) > > Probably a duplicate of bug 71753. > > Yes I read that report. What I don't understand is how the audio clock, uvd > clock, hdmi clock, etc relate to each other. > > For audio I use the realtek chip and it's SPDIF. I guess with the audio > clock, the HDMI audio clock is used? Which in my case is not used I guess. They are not really related on the hw side. UVD decodes as fast as it can based on it's own clocks. When the decoded frame is displayed is up to the application. The audio chip has it's own clock and the display has it's own clock. The hdmi audio information is embedded in the display stream. The monitor uses special packets that the GPU embeds in the display stream to reconstruct the audio stream on the monitor based on the display clock. There seem to be cases where the hdmi stream is not set up properly so the audio clock is not recovered properly on the monitor side. -- You are receiving this mail because: You are the assignee for the bug. --1395690022.Ba451BE51.9288 Date: Mon, 24 Mar 2014 19:40:22 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 7 on bug 76564 from 
(In reply to comment #6)
> (In reply to comment #5)
> > Probably a duplicate of bug 71753.
> 
> Yes I read that report. What I don't understand is how the audio clock, uvd
> clock, hdmi clock, etc relate to each other.
> 
> For audio I use the realtek chip and it's SPDIF. I guess with the audio
> clock, the HDMI audio clock is used? Which in my case is not used I guess.

They are not really related on the hw side.  UVD decodes as fast as it can
based on it's own clocks.  When the decoded frame is displayed is up to the
application.  The audio chip has it's own clock and the display has it's own
clock.  The hdmi audio information is embedded in the display stream.  The
monitor uses special packets that the GPU embeds in the display stream to
reconstruct the audio stream on the monitor based on the display clock.  There
seem to be cases where the hdmi stream is not set up properly so the audio
clock is not recovered properly on the monitor side.

You are receiving this mail because:
  • You are the assignee for the bug.
--1395690022.Ba451BE51.9288-- --===============1956453185== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1956453185==--