HI Mark, On Thu, 2012-01-12 at 02:59 +0000, Mark Brown wrote: > On Tue, Jan 10, 2012 at 08:44:41PM -0600, Ricardo Neri wrote: > > > The approach that I am planning to follow is to move the ASOC HDMI OMAP4 > > codec to the sound directory and leave all the IP-specific functions > > (e.g., to set registers) in the video directory. The audio code should > > be generic in the sense that it does not change an IP register directly. > > This is to follow a similar approach as that followed by DSS in which > > all IP-specific code is separated from DSS code. Also, it makes more > > sense to me to have the ASoC codec under sound/soc/codecs. > > Depending on how abstract that interface is it may be better to make it > into something more cross platform than just an OMAP thing - if you're > talking about not having any knowledge of the registers or anything then > it seems like that should be possible. It would preclude the use of > something OMAP specific like DSS though. Maybe what I am trying to do is something similar to what is done for the TWL6040 drivers: the power part goes to drivers/mfd and and the audio part goes to sound. In my case, the video part goes to DSS and the audio part goes to sound plus taking advantage of the the register abstraction and functionality that DSS is trying to provide. As you mention, this ties me to OMAP atm. I am an audio person :) and I am not sure all the functionality I require for audio is exported to more generic layers to allow not using DSS. I could try go take a look. Ricardo -- 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
