On 08/13/2014 02:04 PM, Mark Brown wrote:
On Fri, Aug 08, 2014 at 04:23:41PM +0300, Jyri Sarha wrote:
Question to ASoC maintainers:
Do feel it is Ok to put ASoC code outside sound/soc the way I do
in these patches (in patch 0006 particularly)?
I'm not thrilled about the idea, it's going to result in breakage during
API updates and more cross tree coordination needs.
I guess then the least bad alternative would be cutting the cpu-dai
driver away from drivers/video/fbdev/omap2/dss/hdmi_audio.c and placing
it under sound/soc/omap and registering it from hdmi_audio.c the same
way as hdmi-audio-codec and asoc-simple-card is now registered.
There would be two devices for a single ip, but at least the ASoC side
driver would receive its resources directly from the HDMI video driver
with necessary tools to synchronize the access.
This approach would work for other HDMI audio situation too, where there
would usually (for tda998x and SiI9022 at least) be a need to register
an i2s codec driver associated with the HDMI encoder. It would probably
be possible to make a single codec driver to work with multiple HDMI
encoders if the API between the codec and endcoder drivers is designed
that in mind.
How does this sound?
Best regards,
Jyri
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
