Re: [PATCH v2 3/5] regcache: Move HW readback after cache initialisation

[Andy Shevchenko]

On Thu, Feb 26, 2026 at 03:27:28PM +0200, Andy Shevchenko wrote:
> On Thu, Feb 26, 2026 at 12:20:44PM +0000, Mark Brown wrote:
> > On Wed, Feb 25, 2026 at 05:15:57PM +0100, Andy Shevchenko wrote:
> > > Make sure that cache is initialised before calling any IO
> > > using regmap, this makes sure that we won't access NULL or
> > > invalid pointers in the cache which hasn't been initialised.
> > 
> > Either this (I suspect it's this) or the subsequent patch is introducing
> > regressions in the ASoC tests on several of my systems in the form:
> > 
> > # ok 1 get_value.AT91SAMG20EK.13
> > # # AT91SAMG20EK.13 Inpwm8731 1-001b: ASoC error (-5): at soc_component_read_no_lock() on wm8731.1-001b for register: [0x00000004]
> > ut Mux
> > 
> >   https://lava.sirena.org.uk/scheduler/job/2498613#L1549
> > 
> > It's not absolutely everything but it's multiple systems (several with
> > Wolfson devices, plus the Pine64 Plus which has an integrated Allwinner
> > CODEC).  I didn't check beyond seeing the failures yet.
> 
> Thanks!
> 
> I also run kunit test cases and it seems like half-failing. I'm about to check
> deeper what's the cause. (Obviously it works in my case on real HW, but...)

At least one small amendment fixed all kunit failures for me. I will send a new
version soon with also fixed patch 5.

-- 
With Best Regards,
Andy Shevchenko