wm8962: error at soc_component_read_no_lock

[Mark Brown]

On Fri, Jul 17, 2020 at 08:26:33AM +0900, Kuninori Morimoto wrote:
> > wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16
> > wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16
> >  input: WM8962 Beep Generator as
> > /devices/platform/soc/2100000.bus/21a0000.i2c/i2c-0/0-001a/input/input3
> > wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16
> > wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16

> > Despite these errors, the codec probes fine.

> > What is the correct way to avoid such errors?

> New component function indicates above when error.
> It seems yours couldn't read because of busy.
> I think it had been happened, but didn't indicate it before.

Right, IIRC the wm8962 had some registers that weren't accessible all
the time and possibly also some volatile bits - the driver will need
updates to handle things better for these widgets.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20200717/e3e5dfe9/attachment.sig>