From: Crt Mori <cmo@melexis.com>
To: Jonathan Cameron <jic23@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Crt Mori <cmo@melexis.com>
Subject: [PATCH 0/2] iio: temperature: mlx90635 Driver for MLX90635 IR temperature sensor
Date: Wed, 22 Nov 2023 11:20:39 +0100 [thread overview]
Message-ID: <cover.1700648164.git.cmo@melexis.com> (raw)
Hi everybody,
There is a new contactless sensor in Melexis portfolio. MLX90635 is just
1.8x1.8mm in size, but with factory calibration offers instant usage
in every project. It offers wide refresh rate range that is configurable
between 100ms and 4s.
Driver currently provides temperature calculations, power management and
changes to the refresh rate. Since sensor is aimed towards the consumer
market there is really low number of EEPROM write cycles available, so
driver changes refresh rate only in run time registers to avoid writing
to EEPROM. Reading EEPROM is not available in Sleep Step mode, so I am
using caching at the driver initialization to ensure that measurements
can still be taken in Sleep Step mode.
Crt Mori (2):
iio: temperature: mlx90635 MLX90635 IR Temperature sensor
dt-bindings: iio: temperature: add MLX90635 device bindings
.../iio/temperature/melexis,mlx90635.yaml | 60 +
MAINTAINERS | 7 +
drivers/iio/temperature/Kconfig | 12 +
drivers/iio/temperature/Makefile | 1 +
drivers/iio/temperature/mlx90635.c | 1099 +++++++++++++++++
5 files changed, 1179 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/temperature/melexis,mlx90635.yaml
create mode 100644 drivers/iio/temperature/mlx90635.c
--
2.40.1
next reply other threads:[~2023-11-22 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 10:20 Crt Mori [this message]
2023-11-22 10:27 ` [PATCH 2/2] dt-bindings: iio: temperature: add MLX90635 device bindings Crt Mori
2023-11-22 11:52 ` Krzysztof Kozlowski
2023-11-22 12:28 ` Crt Mori
2023-11-22 12:35 ` Krzysztof Kozlowski
2023-11-25 17:27 ` Jonathan Cameron
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=cover.1700648164.git.cmo@melexis.com \
--to=cmo@melexis.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).