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@xxxxxxxxxxx> --- 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@xxxxxxxxxxx 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@xxxxxxxxxxx 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@xxxxxxxxxxx --- 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@xxxxxxxxxxx>