Re: [PATCH] iio: imu: st_lsm6dsx: deselect shub page before reading whoami

[Jonathan Cameron <jic23@kernel.org>]

On Thu, 4 Jun 2026 16:23:27 +0000
Andreas Kempe <andreas.kempe@actia.se> wrote:

> On Thu, Jun 04, 2026 at 06:14:11PM +0200, David Lechner wrote:
> > On Thu, Jun 4, 2026 at 5:29 PM Andreas Kempe <andreas.kempe@actia.se> wrote:  
> > >
> > > On Thu, Jun 04, 2026 at 04:36:40PM +0200, Lorenzo Bianconi wrote:  
> > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> > > >  
> > > > >  
> > > > > > Is it enough, if the shub is available, to just always run
> > > > > > st_lsm6dsx_set_page(, false) before checking the whoami?
> > > > > >  
> > > > >
> > > > > I think that should be fine, yes. I only added the readout to lessen
> > > > > the risk of unnecessary writes to potentially unknown devices.  
> > > >
> > > > I guess you just need to check the shub is supported, then it is fine to
> > > > disable shub register access at that point (it is supposed to be that way).
> > > >  
> > >
> > > You are thinking of gating st_lsm6dsx_set_page() on
> > > shub_settings.page_mux.addr like I do, but without the read? Or do you
> > > want to gate on something else?  
> > 
> > How about setting the SW_RESET bit in the CTRL3_C register during
> > probe too to ensure the rest of the registers are in a known state?
> >   
> 
> While the shub register file is selected, the reset register is
> shadowed so it can't be written without first selecting the normal
> register file. A reset is already called from probe in
> st_lsm6dsx_init_device() after the whoami check has passed.

The fix is fine, but I think it shouldn't be buried in the whoami
check as it's a bit of a weird side effect.  I'd like a top level
function that we can see in probe(). That can do the read + write
if necessary sequence you have in this patch.

This driver currently hard rejects unknown wai values (which it probably
should not given fallback compatibles should work). Lets assume that will
get resolved at somepoint and so the wai gate is advisory only. That
means that the dance to avoid writing to a device that doesn't match will
no be useful anyway.

As such, I'd prefer this 'reset of the register file mux selector' was
part of the reset function and that was simply called before checking
WAI.  It fits more logically there than in the whoami check function
which is just the first place the unexpected setting causes problems.
That is put it in st_lsm6dsx_reset_device() and call that before
st_lsm6dsx_check_whoami().  Maybe with a comment to justify that.

Thanks,

Jonathan



> 
> > >
> > > I'm willing to submit a v2 if you want it.
> > >
> > >
> > > Best regards,
> > > Andreas Kempe
> >