Re: [PATCH 01/17] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver

2012-09-11 Thread Ola Lilja
On 09/10/2012 06:46 PM, Lee Jones wrote: > Ola poke. > > On Fri, Aug 24, 2012 at 03:01:37PM +0100, Lee Jones wrote: >> In the initial submission of the MSP driver msp1 and msp3's associated >> pinctrl mechanism was passed back to platform code using a plat_init() >> call-back routine, but it has

Re: [PATCH 01/17] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver

2012-09-10 Thread Lee Jones
Ola poke. On Fri, Aug 24, 2012 at 03:01:37PM +0100, Lee Jones wrote: > In the initial submission of the MSP driver msp1 and msp3's associated > pinctrl mechanism was passed back to platform code using a plat_init() > call-back routine, but it has no place in platform code. The MSP driver > should

Re: [PATCH 01/17] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver

2012-08-30 Thread Linus Walleij
On Fri, Aug 24, 2012 at 7:01 AM, Lee Jones wrote: > In the initial submission of the MSP driver msp1 and msp3's associated > pinctrl mechanism was passed back to platform code using a plat_init() > call-back routine, but it has no place in platform code. The MSP driver > should set this up for th

[PATCH 01/17] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver

2012-08-24 Thread Lee Jones
In the initial submission of the MSP driver msp1 and msp3's associated pinctrl mechanism was passed back to platform code using a plat_init() call-back routine, but it has no place in platform code. The MSP driver should set this up for the appropriate ports. Instead we use a use_pinctrl identifier