mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Jones <carlosjr.jones@analog.com>
To: <linux@roeck-us.net>
Cc: <alexisczezar.torreno@analog.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-hwmon@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Carlos Jones Jr <carlosjr.jones@analog.com>
Subject: [PATCH v2 0/2] hwmon: (pmbus/max20830) add MAX20810/15 and LTM4739/40
Date: Tue, 3 Nov 2026 16:43:29 +0800	[thread overview]
Message-ID: <20261103084331.449-1-carlosjr.jones@analog.com> (raw)

From: Carlos Jones Jr <carlosjr.jones@analog.com>

This series adds support for four additional members of the MAX20830
PMBus regulator family to the existing max20830 driver:

  - MAX20810 (10A) and MAX20815 (15A)
  - LTM4739 and LTM4740, the LTM-series module equivalents of the
    MAX20810 and MAX20815 respectively

All four share the MAX20830 PMBus command set and telemetry, so support
amounts to accepting their IC_DEVICE_ID and documenting the parts; no new
register handling is required. The LTM4739/LTM4740 modules are built around
the MAX20810/MAX20815 dies and report the die's IC_DEVICE_ID ("MAX20810B" /
"MAX20815B"), which the driver matches at probe. Device-tree matching uses
the existing adi,max20830 fallback compatible, so no new of_match entries
are needed.

Patch 1 adds the device-tree binding compatibles; patch 2 adds the driver
support and documentation.

Changes since v1:
- Document the IC_DEVICE_ID vs datasheet discrepancy in-tree, per Guenter's
  review: a code comment above supported_chip_ids[] and an expanded commit
  message, including why the plain datasheet IDs ("MAX20810"/"MAX20815"/
  "LTM4739"/"LTM4740") are not matched (no hardware reporting them observed).
- Rebased on current hwmon-next; no functional change.
- Patch 1 (dt-bindings) is unchanged and carries Conor Dooley's Acked-by
  from v1.

v1: https://lore.kernel.org/all/20261026050241.100428-1-carlosjr.jones@analog.com/

Carlos Jones Jr (2):
  dt-bindings: hwmon: max20830: Add MAX20810, MAX20815, LTM4739, LTM4740
  hwmon: (pmbus/max20830) Add support for MAX20810, MAX20815, LTM4739,
    LTM4740

 .../bindings/hwmon/pmbus/adi,max20830.yaml    |  4 ++
 Documentation/hwmon/max20830.rst              | 51 ++++++++++++++++---
 drivers/hwmon/pmbus/max20830.c                | 10 +++-
 3 files changed, 58 insertions(+), 7 deletions(-)


base-commit: 0dd96d0d34d183866ca6daf5af41341abdfc982a
-- 
2.43.0


             reply	other threads:[~2026-11-03  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  8:43 Carlos Jones [this message]
2026-11-03  8:43 ` [PATCH v2 1/2] dt-bindings: hwmon: max20830: Add MAX20810, MAX20815, LTM4739, LTM4740 Carlos Jones
2026-11-03  8:43 ` [PATCH v2 2/2] hwmon: (pmbus/max20830) Add support for " Carlos 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=20261103084331.449-1-carlosjr.jones@analog.com \
    --to=carlosjr.jones@analog.com \
    --cc=alexisczezar.torreno@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@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

all inboxes | Powered by JetHome®