On Thu, Feb 02, 2012 at 09:09:03PM +0800, Shawn Guo wrote: > On Thu, Feb 02, 2012 at 05:24:28PM +0800, Richard Zhao wrote: > > On Thu, Feb 02, 2012 at 05:11:34PM +0800, Shawn Guo wrote: ... > > > Or we can simply > > > make the it a audmux-self call with 3 parameters it needs retrieved > > > from platform_data or device tree, so that machine driver does not > > > even bother with the call. Makes sense? > > audux configuration may change after initial set. For example, it may use > > one configuration for audio playback, but use another when you connect a > > BT audio device. > > Right. I forgot this point. > With a second thought on this, we can still do this as long as we have mxc_audmux_v2_configure_port() exported. For init-time setup, we can just do it in audmux driver probe function. -- Regards, Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
