From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Vladislav Kulikov <vlad.kulikov.c@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: magnetometer: add MEMSIC MMC5983MA driver
Date: Fri, 8 May 2026 12:19:29 +0300 [thread overview]
Message-ID: <af2qoVNumFdxlXkS@ashevche-desk.local> (raw)
In-Reply-To: <20260507124724.813043-1-vlad.kulikov.c@gmail.com>
On Thu, May 07, 2026 at 12:47:21PM +0000, Vladislav Kulikov wrote:
> Add an IIO driver for the MEMSIC MMC5983MA 3-axis magnetometer over
> I2C. The driver provides raw magnetic field readings with per-measurement
> SET/RESET offset cancellation, giving 18-bit output with a full-scale
> range of +/-8 Gauss.
>
> Tested on a Raspberry Pi 2B with the sensor on I2C-1 at 0x30.
>
> The following chip features are intentionally left out of the initial
> driver because the public datasheet does not provide enough detail to
> expose them confidently through stable IIO ABI, or because they still
> need more validation:
>
> - SPI transport: deferred because SET/RESET polarity behavior has been
> reported to differ between I2C and SPI, especially around SET/RESET
> timing and/or SPI mode.
> - Temperature channel: deferred until the temperature output behavior is
> better validated.
> - Continuous measurement mode and Auto SET/RESET: deferred because the
> datasheet does not clearly define the interaction between CMM, TM_M,
> Meas_M_Done, and SET/RESET sequencing.
> - Saturation/self-test bits: deferred because the applied test field
> strength and bit lifetime are not specified.
> - BW/decimation filter tuning: only the documented measurement timing is
> used; no filter response is exposed because the filter topology and
> coefficients are not documented.
>
> The driver uses a conservative 500 us post-SET/RESET delay before
> starting the following measurement. The datasheet describes a 500 ns
> SET/RESET coil pulse, but existing sample code and practical testing
> indicate that a longer software delay is needed before taking the next
> measurement.
Missed section for a new driver. Id est answer the question "Why a new brand
driver? Do we have something similar in IIO already to be expanded to cover
this HW part?"
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-08 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 12:47 [PATCH 0/3] iio: magnetometer: add MEMSIC MMC5983MA driver Vladislav Kulikov
2026-05-07 12:47 ` [PATCH 1/3] dt-bindings: iio: magnetometer: add MEMSIC MMC5983MA Vladislav Kulikov
2026-05-07 16:46 ` Jonathan Cameron
2026-05-07 12:47 ` [PATCH 2/3] iio: magnetometer: add driver for " Vladislav Kulikov
2026-05-07 17:00 ` Jonathan Cameron
2026-05-07 12:47 ` [PATCH 3/3] MAINTAINERS: add entry for MEMSIC MMC5983MA magnetometer driver Vladislav Kulikov
2026-05-07 16:47 ` Jonathan Cameron
2026-05-08 9:19 ` Andy Shevchenko [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=af2qoVNumFdxlXkS@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=vlad.kulikov.c@gmail.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