From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Jackson <Andrew.Jackson@arm.com>
Cc: Dave Airlie <airlied@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] drm/i2c: tda998x: Allow for different audio sample rates
Date: Tue, 18 Nov 2014 18:00:37 +0000 [thread overview]
Message-ID: <20141118180036.GC4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <546B8452.6030701@arm.com>
On Tue, Nov 18, 2014 at 05:39:30PM +0000, Andrew Jackson wrote:
> On HDMI, the audio data are carried across the HDMI link which is
> driven by the TDMS clock. The TDMS clock is dependent on the video pixel
> rate.
>
> This patch sets the denominator (Cycle Time Stamp) appropriately
> allowing the driver to send audio to a wider range of HDMI sinks
> (i.e. monitors).
This is actually pointless, because we don't use "manual" CTS mode.
If the clocks for the video and audio are coherent, then you can program
both the N and CTS values to allow the sink to properly recover the
synchronous audio clock.
However, in most cases, the audio and video clocks are not coherent, and
since the recovered audio clock has to match the source audio clock, the
only way this can be done is by the TDA998x (or in fact other HDMI
encoder) to measure the audio clock rate and generate the CTS value
itself.
This is the mode we drive the TDA998x - so the programmed CTS value is
irrelevant.
See the HDMI spec, section 7.2 for a discussion about this, especially
non-coherent clocks.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/i2c: tda998x: Allow for different audio sample rates
Date: Tue, 18 Nov 2014 18:00:37 +0000 [thread overview]
Message-ID: <20141118180036.GC4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <546B8452.6030701@arm.com>
On Tue, Nov 18, 2014 at 05:39:30PM +0000, Andrew Jackson wrote:
> On HDMI, the audio data are carried across the HDMI link which is
> driven by the TDMS clock. The TDMS clock is dependent on the video pixel
> rate.
>
> This patch sets the denominator (Cycle Time Stamp) appropriately
> allowing the driver to send audio to a wider range of HDMI sinks
> (i.e. monitors).
This is actually pointless, because we don't use "manual" CTS mode.
If the clocks for the video and audio are coherent, then you can program
both the N and CTS values to allow the sink to properly recover the
synchronous audio clock.
However, in most cases, the audio and video clocks are not coherent, and
since the recovered audio clock has to match the source audio clock, the
only way this can be done is by the TDA998x (or in fact other HDMI
encoder) to measure the audio clock rate and generate the CTS value
itself.
This is the mode we drive the TDA998x - so the programmed CTS value is
irrelevant.
See the HDMI spec, section 7.2 for a discussion about this, especially
non-coherent clocks.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Jackson <Andrew.Jackson@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i2c: tda998x: Allow for different audio sample rates
Date: Tue, 18 Nov 2014 18:00:37 +0000 [thread overview]
Message-ID: <20141118180036.GC4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <546B8452.6030701@arm.com>
On Tue, Nov 18, 2014 at 05:39:30PM +0000, Andrew Jackson wrote:
> On HDMI, the audio data are carried across the HDMI link which is
> driven by the TDMS clock. The TDMS clock is dependent on the video pixel
> rate.
>
> This patch sets the denominator (Cycle Time Stamp) appropriately
> allowing the driver to send audio to a wider range of HDMI sinks
> (i.e. monitors).
This is actually pointless, because we don't use "manual" CTS mode.
If the clocks for the video and audio are coherent, then you can program
both the N and CTS values to allow the sink to properly recover the
synchronous audio clock.
However, in most cases, the audio and video clocks are not coherent, and
since the recovered audio clock has to match the source audio clock, the
only way this can be done is by the TDA998x (or in fact other HDMI
encoder) to measure the audio clock rate and generate the CTS value
itself.
This is the mode we drive the TDA998x - so the programmed CTS value is
irrelevant.
See the HDMI spec, section 7.2 for a discussion about this, especially
non-coherent clocks.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-18 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 17:39 [PATCH] drm/i2c: tda998x: Allow for different audio sample rates Andrew Jackson
2014-11-18 17:39 ` Andrew Jackson
2014-11-18 17:39 ` Andrew Jackson
2014-11-18 18:00 ` Russell King - ARM Linux [this message]
2014-11-18 18:00 ` Russell King - ARM Linux
2014-11-18 18:00 ` Russell King - ARM Linux
2014-11-19 11:21 ` Andrew Jackson
2014-11-19 11:21 ` Andrew Jackson
2014-11-19 11:21 ` Andrew Jackson
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=20141118180036.GC4042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Andrew.Jackson@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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.