public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikhil Gautam <nikhilgtr@gmail.com>
To: jic23@kernel.org, linux-iio@vger.kernel.org
Cc: andriy.shevchenko@intel.com, linux-kernel@vger.kernel.org,
	Nikhil Gautam <nikhilgtr@gmail.com>,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org
Subject: Re: [RFC] iio: magnetometer: mlx90393 - regmap vs command-based access
Date: Fri, 24 Apr 2026 18:27:39 +0530	[thread overview]
Message-ID: <20260424125739.4685-1-nikhilgtr@gmail.com> (raw)
In-Reply-To: <20260424114818.1290b029@jic23-huawei>

Hi Andy, Jonathan,

Thanks for taking a look and for the guidance.

The MLX90393 does indeed expose a mix of command-based operations
(SM, RM, etc.) along with limited register access (RR/WR), so it
does not map cleanly to a purely register-based model.

Based on your feedback, I will proceed with a custom command
abstraction layer instead of using regmap. The idea is to keep a
clean separation between command handling, register access, and
bus transport (I2C/SPI), while keeping the structure somewhat
regmap-like where it makes sense.

I will put together an RFC patch with the initial implementation
(I2C support first) and share it shortly for review.

Thanks again for the feedback.

Best regards,
Nikhil Gautam

      reply	other threads:[~2026-04-24 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 12:18 [RFC] iio: magnetometer: mlx90393 - regmap vs command-based access Nikhil Gautam
2026-04-23 12:25 ` Nikhil Gautam
2026-04-23 17:43   ` Andy Shevchenko
2026-04-24 10:48     ` Jonathan Cameron
2026-04-24 12:57       ` Nikhil Gautam [this message]

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=20260424125739.4685-1-nikhilgtr@gmail.com \
    --to=nikhilgtr@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /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