HDMI codec, way forward?
Jyri Sarha
jsarha at ti.com
Mon Oct 19 13:14:53 PDT 2015
On 10/18/15 18:02, Vinod Koul wrote:
> 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
The idea is to provide all possible formats and rates to the ASoC core
at the DAI registration phase. Then at the stream startup the currently
valid ELD is scanned and and ALSA constraints are set according to it
(with snd_pcm_hw_constraint_eld()).
> 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!
Russell already listed why the component interface is not good for
registering optional subsystems. Any particular reason why passing
function pointers over pdata should be considered bad? Can you suggest
an alternative?
Best regards,
Jyri
More information about the dri-devel
mailing list