From: Thomas Richard <thomas.richard@bootlin.com>
To: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>, Lee Jones <lee@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
thomas.petazzoni@bootlin.com, blake.vermeer@keysight.com,
linux-doc@vger.kernel.org,
Thomas Richard <thomas.richard@bootlin.com>
Subject: [PATCH v4 0/2] Enable sensors support for the Congatec Board Controller
Date: Mon, 03 Feb 2025 12:01:04 +0100 [thread overview]
Message-ID: <20250203-congatec-board-controller-hwmon-v4-0-ff6c76a4662c@bootlin.com> (raw)
This is the fourth iteration of this series which enables sensors support
for the Congatec Board Controller.
The series was rebased on v6.14-rc1.
A typo was fixed in the Kconfig, and the description improved.
The documentation file Documentation/hwmon/cgbc-hwmon.rst was added.
Regards,
Thomas
Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
---
Changes in v4:
- Rebased on v6.14-rc1.
- Add the documentation for this driver.
- In Kconfig, fix a typo and improve the description
- Link to v3: https://lore.kernel.org/r/20241115-congatec-board-controller-hwmon-v3-0-1c45637c8266@bootlin.com
Changes in v3:
- remove the cgbc_hwmon_compute_curr_channel() macro.
- Link to v2: https://lore.kernel.org/r/20241108-congatec-board-controller-hwmon-v2-0-16e337398527@bootlin.com
Changes in v2:
- hwmon: use unsigned int type instead of u8 in struct cgbc_hwmon_sensor
and struct cgbc_hwmon_data.
- hwmon: in cgbc_hwmon_probe_sensors() no need to request data for the
first sensor as the Board Controller returns data of the first sensors
with the number of sensors.
- hwmon: fix typos in comments and improve them.
- hwmon: remove dead code in cgbc_hwmon_read() and in
cgbc_hwmon_read_string() (deadcode was the 'return -ENODEV').
- hwmon: remove useless platform_set_drvdata().
- hwmon: channel id always refers to the same sensor.
- hwmon: add a enum cgbc_sensor_types.
- Link to v1: https://lore.kernel.org/r/20241104-congatec-board-controller-hwmon-v1-0-871e4cd59d8e@bootlin.com
---
Thomas Richard (2):
hwmon: Add Congatec Board Controller monitoring driver
mfd: cgbc: add a hwmon cell
Documentation/hwmon/cgbc-hwmon.rst | 63 ++++++++
Documentation/hwmon/index.rst | 1 +
MAINTAINERS | 1 +
drivers/hwmon/Kconfig | 10 ++
drivers/hwmon/Makefile | 1 +
drivers/hwmon/cgbc-hwmon.c | 304 +++++++++++++++++++++++++++++++++++++
drivers/mfd/cgbc-core.c | 1 +
7 files changed, 381 insertions(+)
---
base-commit: 379487e17ca406b47392e7ab6cf35d1c3bacb371
change-id: 20240809-congatec-board-controller-hwmon-e9e63d957d33
Best regards,
--
Thomas Richard <thomas.richard@bootlin.com>
next reply other threads:[~2025-02-03 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:01 Thomas Richard [this message]
2025-02-03 11:01 ` [PATCH v4 1/2] hwmon: Add Congatec Board Controller monitoring driver Thomas Richard
2025-03-17 18:16 ` Guenter Roeck
2025-02-03 11:01 ` [PATCH v4 2/2] mfd: cgbc: add a hwmon cell Thomas Richard
2025-02-11 13:39 ` Lee Jones
2025-03-21 11:27 ` (subset) " Lee Jones
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=20250203-congatec-board-controller-hwmon-v4-0-ff6c76a4662c@bootlin.com \
--to=thomas.richard@bootlin.com \
--cc=blake.vermeer@keysight.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=thomas.petazzoni@bootlin.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