mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kanak Shilledar <Kanak.Shilledar@axis.com>
To: "andriy.shevchenko@intel.com" <andriy.shevchenko@intel.com>
Cc: "krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"andy@kernel.org" <andy@kernel.org>, Kernel <Kernel@axis.com>,
	"macromorgan@hotmail.com" <macromorgan@hotmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"joshua.crofts1@gmail.com" <joshua.crofts1@gmail.com>,
	"jean-baptiste.maneyrol@tdk.com" <jean-baptiste.maneyrol@tdk.com>,
	"dlechner@baylibre.com" <dlechner@baylibre.com>,
	"nuno.sa@analog.com" <nuno.sa@analog.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"marcelo.schmitt1@gmail.com" <marcelo.schmitt1@gmail.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Henrik Grimler <Henrik.Grimler@axis.com>
Subject: Re: [PATCH v5 5/6] iio: imu: inv_icm42607: Implement MREGx register access
Date: Mon, 5 Oct 2026 15:02:53 +0000	[thread overview]
Message-ID: <b9f2af54922a988483a6188f0119ec5622cf4f6d.camel@axis.com> (raw)
In-Reply-To: <asEY9DHDisqVcQ5D@ashevche-desk.local>

[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]


Hi Andy,
On Sat, 2026-10-03 at 18:02 +0300, andriy.shevchenko@intel.com wrote:
> On Fri, Oct 02, 2026 at 02:25:48PM +0000, Kanak Shilledar wrote:
> 
> > On Fri, 2026-10-02 at 16:12 +0300, Andy Shevchenko wrote:
> > > On Fri, Oct 02, 2026 at 01:54:29PM +0200, Kanak Shilledar wrote:
> 
> ...
> 
> > > > +static int inv_icm42607_mreg_read(struct regmap *map, unsigned
> > > > int
> > > > reg,
> > > > +				  u8 *data, size_t count)
> > > > +{
> > > > +	unsigned int val;
> > > > +	bool idle_set;
> > > > 
...
> > > > +
> > > > +	return ret;
> > > >  }
> 
> ...
> 
> > > > +static const struct regmap_config inv_icm42607_regmap_config =
> > > > {
> > > > +	.reg_bits = 8,
> > > > +	.val_bits = 8,
> > > 
> > > No cache? Why?
> > As the virtual regmap config has some caching for USER BANK 0
> > registers
> > only. The indirect banks doesn't support caching [1].
> 
> This is strange. You mean they are volatile by definition (HW)?
> Otherwise if it's just a software issue, it can still be done,
> for regcache there is no difference if the offset is real or paged.

Sorry, I was not very clear in the explanation about caches. Only some
specific MREGx registers are volatile and I am not using those yet. I
have removed the MREGx registers from the _is_volatile_reg function.

In this 8-bit transport regmap I am not using any caching because the
16-bit virtual regmap (in _core.c) already knows all the registers
(readable/writeable/volatile) and also contains a cache. Everything
which reaches the transport regmap is either a write or read which was
missed in the virtual cache or an access to the bank switching
registers which should always reach the hardware. I tried adding
REGCACHE_MAPLE in the transport regmap, but accessing registers in
MREG1 then timed out due to stale cached values.

> > > 
> > [1] Datasheet: https://www.lcsc.com/product-detail/C5129967.html

Thanks and Regards,
Kanak Shilledar

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-10-05 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 11:54 [PATCH v5 0/6] Add support for InvenSense ICM-42370-P accelerometer Kanak Shilledar
2026-10-02 11:54 ` [PATCH v5 1/6] dt-bindings: iio: imu: icm42600: Add ICM-42670-P Kanak Shilledar
2026-10-02 17:11   ` Conor Dooley
2026-10-02 17:11     ` Conor Dooley
2026-10-02 11:54 ` [PATCH v5 2/6] iio: imu: inv_icm42607: Simplify IIO channel macros Kanak Shilledar
2026-10-05  0:25   ` Marcelo Schmitt
2026-10-02 11:54 ` [PATCH v5 3/6] iio: imu: inv_icm42607: Initialize gyro based on chip_info Kanak Shilledar
2026-10-02 13:03   ` Andy Shevchenko
2026-10-05  0:39   ` Marcelo Schmitt
2026-10-02 11:54 ` [PATCH v5 4/6] iio: imu: inv_icm42607: Add support for ICM-42370-P Kanak Shilledar
2026-10-02 13:04   ` Andy Shevchenko
2026-10-05  0:43   ` Marcelo Schmitt
2026-10-02 11:54 ` [PATCH v5 5/6] iio: imu: inv_icm42607: Implement MREGx register access Kanak Shilledar
2026-10-02 13:12   ` Andy Shevchenko
2026-10-02 14:25     ` Kanak Shilledar
2026-10-03 15:02       ` andriy.shevchenko
2026-10-05 15:02         ` Kanak Shilledar [this message]
2026-10-02 11:54 ` [PATCH v5 6/6] iio: imu: inv_icm42607: Add accelerometer calibbias support Kanak Shilledar
2026-10-02 13:18   ` Andy Shevchenko
2026-10-02 14:03     ` Kanak Shilledar
2026-10-03 14:57       ` andriy.shevchenko
2026-10-05  0:51   ` Marcelo Schmitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b9f2af54922a988483a6188f0119ec5622cf4f6d.camel@axis.com \
    --to=kanak.shilledar@axis.com \
    --cc=Henrik.Grimler@axis.com \
    --cc=Kernel@axis.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jean-baptiste.maneyrol@tdk.com \
    --cc=jic23@kernel.org \
    --cc=joshua.crofts1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®