19 Jan
2016
19 Jan
'16
6:06 p.m.
On Tue, Jan 19, 2016 at 02:40:34PM +0100, Arnaud Pouliquen wrote:
- /* update N parameter */
- ret = hdmi_audio_compute_n_cts(params->sample_rate,
hdmi->mode.clock, &n_cts);
- if (ret < 0)
return ret;
- DRM_DEBUG_DRIVER("sample_frequency= %d, pix clock = %d\n",
params->sample_rate, hdmi->mode.clock);
- DRM_DEBUG_DRIVER("n= %d, cts = %d\n", n_cts.n, n_cts.cts);
- hdmi_write(hdmi, n_cts.n, HDMI_AUDN);
This looks like you only make use of the N parameter, which suggests that your hardware measures the CTS parameter itself - which means you have the non-coherent clock case. You'll want to refer to the HDMI specs and use different N values from the coherent case.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.