ac100 team mailing list archive

[Andrey Danin <danindrey@xxxxxxx>]

Epic fail :)
cat /sys/kernel/debug/asoc/tegra-paz00/alc5632.0-001e/codec_reg
and read from i2c device give different results. According to dump from i2c device registers state after resume is different to state before suspend. Restoring regs state didn't fix sound after resume.
Additional investigations are needed.


10 октября 2011, 15:10 от Marc Dietrich <marvin24@xxxxxx>:
> Am Montag, 10. Oktober 2011, 12:22:47 schrieb Andrey Danin:
> > 10 октября 2011, 12:08 от Marc Dietrich <marvin24@xxxxxx>:
> > > Am Samstag, 8. Oktober 2011, 11:45:20 schrieb Oliver Grawert:
> > > > hi,
> > > >
> > > > Am Samstag, den 08.10.2011, 11:41 +0200 schrieb Oliver Grawert:
> > > > > works fine for me after setting ...
> > > >
> > > > stops working after resume from suspend, we might need some
> > > > re-initialization here, if that's possible from user space through some
> > > > command we could add the re-init to a gnome-power-manager quirk, though
> > > > i suspect the kernel needs to handle it rather than user space...
> > >
> > > maybe the amplifier just needs to be enabled again. Should be easy to add to
> > > nvec- event.c.
> >
> > Headphones don't work too (if hp are related to nvec, please point how it is done).
> > alc5632 registers state is restored after resume but with no effect.
> > snd_soc_tegra_paz00 and snd_soc_alc5632 must be reloaded to fix this issue: sudo
> > rmmod snd_soc_tegra_paz00
> > sudo rmmod snd_soc_alc5632
> > sudo modprobe snd_soc_alc5632
> > sudo modprobe snd_soc_tegra_paz00
> 
> aha, so it is not related to nvec (would be too easy to blame it for everything), but
> more like a codec init issue. At least this isolates the problem a bit.
> 
> Thanks
> 
> Marc
> 
>