[alsa-devel] Fwd: [PATCH 1/1] SPI : spi-pxa2xx : fix spi init of WM510205 codec via ACPI (resend)

[Charles Keepax]

On Tue, Jul 07, 2015 at 09:06:25AM +0200, Christian Hartmann wrote:
> 2015-06-30 12:34 GMT+02:00 Charles Keepax <ckeepax at opensource.wolfsonmicro.com>:
> > On Tue, Jun 30, 2015 at 09:14:37AM +0200, Christian Hartmann wrote:
> >> Hi,
> >>
> >>
> >> 2015-06-29 11:48 GMT+02:00 Mark Brown <broonie at kernel.org>:
> >> > On Mon, Jun 29, 2015 at 09:27:17AM +0200, Christian Hartmann wrote:
> >> >> [    5.927801] spi-WM510205:00 supply DCVDD not found, using dummy regulator
> >> >> [    5.928958] arizona spi-WM510205:00: Unknown device ID: ffff
> >> >> [    5.929098] pxa2xx-spi 80860F0E:00: registered child spi-WM510205:00
> >> >
> >> > The above is saying that SPI I/O to the device isn't working - the
> >> > device ID is not being read back successfully.
> >>
> >> Ok that is the next problem that must be solved.
> >> I have yesterday made a patchset where I have added
> >> the enum type 5, but as you said already,
> >> that was not needed.
> >> All what I see the same: : Unknown device ID: ffff
> >>
> >> So where I have to look now or what can I do to let this device id
> >> register correctly?
> >> I hope the baytrail machine driver is easy peasy to add, but here I
> >> stuck at the moment.
> >
> > As I said in my other emails the next step is to work out what
> > the reset and ldoena gpio's are. You won't be able to read the
> > device ID until you have those setup. Unfortunately, finding the
> > right GPIOs is likely to be a bit of a chore, I will see if I can
> > find anything out from the Windows guys at this end.
> >
> > Also can you check that the arizona-ldo1 regulator is built in I
> > am surprised that is falling back to the dummy regulator.
> >
> > Thanks,
> > Charles
> 
> Hi,
> 
> I just want to ask, if the windows guys have such infos about the
> gpios in question (reset,ldoena) and of course the irq details.

Still chasing them up on this.

> 
> I am thinking actually to get a second device with Win installed, so
> that I can get more infos which I really need here.
> Anyway  I can also provide more infos here (if its not against valid laws :) )
> But indeeed I can need some hints where to put the pdata structure.

I think in this case we need to hard code the pdata into the
driver. Probably in arizona-core.c would be the best place.

> 
> I have some more questions that I want to ask/discuss later on irc -
> if its possible

Yeah I shall jump on and you can give me a shout.

Thanks,
Charles