From: Nikhil Gautam <nikhilgtr@gmail.com>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-kernel@vger.kernel.org,
Nikhil Gautam <nikhilgtr@gmail.com>
Subject: Re: [RFC] iio: magnetometer: mlx90393 - regmap vs command-based access
Date: Thu, 23 Apr 2026 17:55:35 +0530 [thread overview]
Message-ID: <20260423122535.4334-1-nikhilgtr@gmail.com> (raw)
In-Reply-To: <20260423121834.4244-1-nikhilgtr@gmail.com>
Hi,
Apologies for missing a few details in the previous mail.
The MLX90393 supports both I2C and SPI interfaces.
Commands include, for example:
- SM (Start Measurement)
- RM (Read Measurement)
- RR (Read Register)
Given this command-oriented interface over both I2C and SPI,
I wanted to confirm whether a custom command abstraction layer
would still be the preferred approach instead of regmap.
Thanks,
Nikhil Gautam
next prev parent reply other threads:[~2026-04-23 12:25 UTC|newest]
Thread overview: 3+ 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 [this message]
2026-04-23 17:43 ` Andy Shevchenko
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=20260423122535.4334-1-nikhilgtr@gmail.com \
--to=nikhilgtr@gmail.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