HDMI codec, way forward?

[Vinod Koul]

On Fri, Oct 16, 2015 at 02:31:43PM +0200, Lars-Peter Clausen wrote:
> On 10/16/2015 01:50 PM, Jyri Sarha wrote:
> > After reading the ELCE Audio mini conf minutes [1] I gather that HDMI
> > audio was not discussed after all.
> 
> It was discussed, but rather shortly and only in the context of the HDA.
> (Adding Vinod to Cc, who presented yet another approach to the problem last
> week)

Thanks for adding me :)

Based on the links sent by Jyri, I did look up the series from Jyri and
Arnaud. I have tried to summarize the approach but please do correct me if I
got something wrong

There are similarities but both are trying to add an interface between audio
and display.

Jyri's approach to add generic IEC code makes sense and drives reuse. I kind
of didn't like adding rates and formats for DAIs, if they are placeholders
then it is okay but otherwise we should read and set them from ELD. Also I
have reservations about hdmi_codec_ops and this being set by drm driver, why
not use component interface for these things and let data be shared!

Arnaud's approach to add N,CTS helpers is great. But having calls to drm
from audio side for drm enabling wouldn't have been required if we have
component interface here.

If we have these calls on a component interface and use these as generic ops
for the audio-drm interface rather than i915 which is implemented today we
don't need to export symbols and create a dependency between these two side.

Also I would again like you folks to review the HDA HDMI ASoC driver RFC I
posted recently [1]. We use component interface and have been adding more
callback to interface. David added notification [2] and we plan to add ELD
query as well soonish.

[1]: http://mailman.alsa-project.org/pipermail/alsa-devel/2015-October/098730.html
[2]: http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/097042.html

-- 
~Vinod