From: sashiko-bot@kernel.org
To: "Carlos Jones" <carlosjr.jones@analog.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/2] hwmon: (pmbus/max20830) Add support for MAX20810, MAX20815, LTM4739, LTM4740
Date: Tue, 03 Nov 2026 08:59:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-194910@kernel.org> (raw)
In-Reply-To: <20261103084331.449-3-carlosjr.jones@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] hwmon: (pmbus/max20830) Kconfig help text not updated for new chips
--
commit a48cd701bd54f337809702615b2dcd55ba0b47a3
Author: Carlos Jones Jr <carlosjr.jones@analog.com>
hwmon: (pmbus/max20830) Add support for MAX20810, MAX20815, LTM4739, LTM4740
This commit adds support for the MAX20810, MAX20815, LTM4739, and LTM4740
step-down switching regulators to the max20830 PMBus driver by matching
their IC_DEVICE_ID strings ("MAX20810B" and "MAX20815B") and updating
Documentation/hwmon/max20830.rst.
> diff --git a/drivers/hwmon/pmbus/max20830.c b/drivers/hwmon/pmbus/max20830.c
> index 4d25a084af096..39cce250beca4 100644
> --- a/drivers/hwmon/pmbus/max20830.c
> +++ b/drivers/hwmon/pmbus/max20830.c
> @@ -20,7 +20,15 @@ struct max20830_data {
> u32 vout_rfb2;
> };
>
> +/*
> + * IC_DEVICE_ID strings matched at probe. The LTM4739/LTM4740 uModules
> + * report their MAX die ID with a "B" suffix, not the "LTM47xx" names in
> + * their datasheets (being corrected); the plain datasheet IDs are not
> + * matched, as no such part has been observed.
> + */
> static const char * const supported_chip_ids[] = {
> + "MAX20810B", /* LTM4739 */
> + "MAX20815B", /* LTM4740 */
> "MAX20830",
> "MAX20830C",
> "MAX20840C",
[Severity: Low]
This isn't a bug, but when adding support for MAX20810, MAX20815, LTM4739,
and LTM4740 in supported_chip_ids[] and Documentation/hwmon/max20830.rst,
should the SENSORS_MAX20830 entry in drivers/hwmon/pmbus/Kconfig also be
updated?
Currently drivers/hwmon/pmbus/Kconfig only lists the previously supported
models:
config SENSORS_MAX20830
tristate "Analog Devices MAX20830 and compatibles"
help
If you say yes here you get hardware monitoring support for Analog
Devices MAX20830, MAX20830C, and MAX20840C.
Documentation/hwmon/submitting-patches.rst asks that Kconfig information be
kept up to date when adding functionality to existing drivers, similar to
commit 4cdcd4789fb6 ("hwmon: (max20830) Add support for MAX20830C and
MAX20840C").
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103084331.449-1-carlosjr.jones@analog.com?part=2
prev parent reply other threads:[~2026-11-03 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:43 [PATCH v2 0/2] hwmon: (pmbus/max20830) add MAX20810/15 and LTM4739/40 Carlos Jones
2026-11-03 8:43 ` [PATCH v2 1/2] dt-bindings: hwmon: max20830: Add MAX20810, MAX20815, LTM4739, LTM4740 Carlos Jones
2026-11-03 8:50 ` sashiko-bot
2026-11-03 8:43 ` [PATCH v2 2/2] hwmon: (pmbus/max20830) Add support for " Carlos Jones
2026-11-03 8:59 ` sashiko-bot [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=sashiko-outbox-194910@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=carlosjr.jones@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.