From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: linux@roeck-us.net, krzk@kernel.org, robh@kernel.org,
christophe.jaillet@wanadoo.fr, jdelvare@suse.com
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org,
andrey.lalaev@gmail.com
Subject: [PATCH RESEND v3 0/2] Add driver for HTU31
Date: Mon, 17 Feb 2025 06:10:54 +0100 [thread overview]
Message-ID: <20250217051110.46827-1-andrey.lalaev@gmail.com> (raw)
This patch series adds support for HTU31 humidity and temperature
sensor.
Changes in v3:
- move serial number attribute to debugfs
- fix the position of entry in Makefile to keep alphabetical order
- fix the patch versioning
Changes in v2:
- replace DIV_ROUND_CLOSEST with DIV_ROUND_CLOSEST_ULL to prevent
possible overflow
- drop mutex locking from htu31_read_serial_number, as the function is
only called from probe
- add description of the private data structure
- fix the issues pointed by Christophe
- add an entry to MAINTAINERS file
- add Krzysztof's ACK to dt-bindings patch
v1: https://lore.kernel.org/all/20250123202528.223966-1-andrey.lalaev@gmail.com/#t
Andrei Lalaev (2):
hwmon: add driver for HTU31
dt-bindings: hwmon: Add description for sensor HTU31
.../devicetree/bindings/trivial-devices.yaml | 2 +
Documentation/hwmon/htu31.rst | 37 ++
Documentation/hwmon/index.rst | 1 +
MAINTAINERS | 6 +
drivers/hwmon/Kconfig | 11 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/htu31.c | 351 ++++++++++++++++++
7 files changed, 409 insertions(+)
create mode 100644 Documentation/hwmon/htu31.rst
create mode 100644 drivers/hwmon/htu31.c
--
2.48.1
next reply other threads:[~2025-02-17 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 5:10 Andrei Lalaev [this message]
2025-02-17 5:10 ` [PATCH RESEND v3 1/2] hwmon: add driver for HTU31 Andrei Lalaev
2025-03-17 18:23 ` Guenter Roeck
2025-02-17 5:10 ` [PATCH RESEND v3 2/2] dt-bindings: hwmon: Add description for sensor HTU31 Andrei Lalaev
2025-03-17 18:21 ` Guenter Roeck
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=20250217051110.46827-1-andrey.lalaev@gmail.com \
--to=andrey.lalaev@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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