On Tue, 6 Oct 2015 11:23:03 +0200 Arnaud Pouliquen arnaud.pouliquen@st.com wrote: [snip]
As API is defined in DRM, it seems more logical to match it with the one defined for video. From my windows, i didn't see any blocking point to connect codec callback with this API. But anyway, this API is not freezed, it could be improved with your help.
Arnaud, your implementation seems more heavy than Jyri's, and I don't feel the DRM bridge.
For HDMI, the exchanges between DRM and ALSA are only: - DRM -> ALSA - device connection with the audio constraints - device disconnection - ALSA -> DRM - start audio with the chosen audio parameters - stop audio
and, in the system, the HDMI devices are seen as DRM connectors (video view) and as ASoC CODECs (audio view).
We just need a link between these entities. I don't think that the bridge offers this.
(going further, it seems natural to me that both entities would be supported by the same kernel device and that the exchange functions and values could be defined both ways from a common structure - audio constraints, playback parameters, connector2codec functions, codec2connector functions - but this is an other story...)