On Mon, Dec 01, 2014 at 09:15:36AM +0200, Jyri Sarha wrote: > The only reason is that I have not encountered any other audio capable HDMI > device falling in this category (cpu-dai integrated within HDMI device > block). Without at least two devices utilizing this code it remains > questionable whether the code is really generic. At least the dss_version > should be replaced with some explicit data to fill struct > snd_soc_dai_driver. Also struct omap_dss_audio is coming directly from omap > dss code, its contents is generic but I am not sure if the information > within struct snd_aes_iec958 and struct snd_cea_861_aud_if is enough to > configure the HDMI IP in all possible cases. It should be no big deal to add extra information if required. Given how poor the upstreaming state is for HDMI I expect we'd get people coming out of the woodwork if there were infrastructure, some of the Exynos stuff looked similar to your situation for example. > I can work on making this API look more generic, but before there is another > candidate to use this API it is questionable if the code will ever be used > by any other device. Unless there is something obviously terrible about the hardware design that I'm missing which means nobody else would ever have implemented something like it I'd expect there will be at least one other system that can make use of the code.
Attachment:
signature.asc
Description: Digital signature
