Re: [PATCH v3 0/2] McBSP changes for OMAP4 platform

Re: [PATCH v3 0/2] McBSP changes for OMAP4 platform

[Liam Girdwood]

On Thu, 2010-05-13 at 09:19 +0100, Mark Brown wrote:
> On Wed, May 12, 2010 at 12:18:38PM -0500, Jorge Eduardo Candelaria wrote:
> > The following patches enable McBSP driver to be used along with the
> > audio driver in SDP4430 and other OMAP4 based boards.
> 
> Both
> 
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

Tony, do we have you ack/sob to upstream via ASoC ?

We do have a lot pending with mcbsp dependencies for ASoC atm and this
would simplify upstreaming.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

Re: [PATCH v3 0/2] McBSP changes for OMAP4 platform

[Tony Lindgren]

* Liam Girdwood <lrg@slimlogic.co.uk> [100513 02:24]:
> On Thu, 2010-05-13 at 09:19 +0100, Mark Brown wrote:
> > On Wed, May 12, 2010 at 12:18:38PM -0500, Jorge Eduardo Candelaria wrote:
> > > The following patches enable McBSP driver to be used along with the
> > > audio driver in SDP4430 and other OMAP4 based boards.
> > 
> > Both
> > 
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> 
> Tony, do we have you ack/sob to upstream via ASoC ?

No problem with me, both of them:

Acked-by: Tony Lindgren <tony@atomide.com>
 
> We do have a lot pending with mcbsp dependencies for ASoC atm and this
> would simplify upstreaming.

Sure, I agree. It's best to keep the patchsets toghether.

One request I have for the long run is to set some features
flag during init and only use the cpu_is_omapxxxx tests once
during init. That way the driver is more future proof and
should not require adding cpu_is_omapxxxx all over the place.

Regards,

Tony