On Fri, Jul 17, 2020 at 8:23 AM Mark Brown <broonie@xxxxxxxxxx> wrote: > 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. Thanks, Mark. I instrumented the code to print the register names so we can see where soc_component_read_no_lock fails: [ 6.010526] ************ register is 512 (WM8962_GPIO_BASE) [ 6.014540] wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16 [ 6.030852] ************ register is 515 (This register does not exist) [ 6.034806] wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16 [ 6.162651] ************ register is 48 (WM8962_ADDITIONAL_CONTROL_4) [ 6.166524] wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16 [ 6.174911] ************ register is 48 (WM8962_ADDITIONAL_CONTROL_4) [ 6.178779] wm8962 0-001a: ASoC: error at soc_component_read_no_lock on wm8962.0-001a: -16 Charles, Shengjiu, any suggestions, please? Thanks
