Skip to content

hwmon: (pmbus/ltc2978) Add support for LT7170L and LT7171L - #3666

Open
cdeguzm4 wants to merge 9 commits into
analogdevicesinc:mainfrom
cdeguzm4:fce1023-lt7171l
Open

cdeguzm4 wants to merge 9 commits into
analogdevicesinc:mainfrom
cdeguzm4:fce1023-lt7171l

Conversation

@cdeguzm4

@cdeguzm4 cdeguzm4 commented Nov 16, 2026 •

Copy link
Copy Markdown

PR Description

Depends on #3596 (LT7175/LT7176P/LTM4681/LTM4682). This branch is stacked on it, so until #3596 merges, only the last 3 commits belong to this PR:

  • dt-bindings: hwmon: ltc2978: Add LT7170L and LT7171L
  • hwmon: (pmbus/ltc2978) Add support for LT7170L and LT7171L
  • hwmon: ltc2978: Document LT7170L and LT7171L support

Adds the LT7170L / LT7171L (and their -1 variants) to the ltc2978 PMBus driver. The L parts are pin compatible with LT7170/LT7171 and add a pulse-skipping mode for better light-load efficiency.

The L parts report the same IDs as the non-L parts: MFR_SPECIAL_ID 0x1C1D and IC_DEVICE_ID "LT7170"/"LT7171" (or the -1 strings). Their telemetry registers are identical, and pulse-skipping is only a configuration bit (MFR_PWM_MODE) that hwmon doesn't use. So the driver can't tell L from non-L parts at runtime, and doesn't need to. This PR adds names only:

  • ltc2978.c: i2c IDs lt7170l and lt7171l, and OF compatibles lltc,lt7170l and lltc,lt7171l, mapped to the existing lt7170/lt7171 chip types. There's no new chip enum and no change to detection.
    • The i2c IDs are required, not optional: for DT devices the client name comes from the first compatible. Without them, i2c_client_get_device_id() would return NULL for a "lltc,lt7171l", "lltc,lt7171" node, and probe would dereference it.
  • DT binding: compatible is now a oneOf. Each L part must be listed together with its base part as the fallback ("lltc,lt7171l", "lltc,lt7171").
  • Kconfig: the regulator help text lists the L parts.
  • ltc2978.rst: the supported chips list, the description, and the vout/temp1/iout attribute lists.

Testing

On a Raspberry Pi (6.12.41-v7+) with an LT7171-1 board at i2c-1, address 0x41:

Test hwmon name VIN VOUT dmesg
new_device lt7171l 0x41 lt7171l 3296 mV 999 mV clean, no "Device mismatch"
new_device lt7171 0x41 (regression) lt7171 3298 mV 999 mV clean
DT overlay "lltc,lt7171l", "lltc,lt7171", bound at boot lt7171l 3291 mV 999 mV clean, no oops
  • dt_binding_check: both fallback pairs pass. A lone L compatible, or an L part paired with the wrong fallback, is rejected.
  • checkpatch --strict: clean.
  • LT7170L was not tested on hardware (no board). It goes through the same code path as LT7171L.

PR Type

  • Bug fix (a change that fixes an issue)
  • New feature (a change that adds new functionality)
  • Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

  • I have conducted a self-review of my own code changes
  • I have compiled my changes, including the documentation
  • I have tested the changes on the relevant hardware
  • I have updated the documentation outside this repo accordingly
  • I have provided links for the relevant upstream lore

Add LTM4681 and LTM4682 to the supported devices of LTC2978. Both are
quad-output µModule regulators. Each I2C address exposes two PMBus
pages, so the regulators are vout0 - vout1.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Add support for LTM4681 and LTM4682. The LTM4681 and LTM4682 are quad
31.25A and single 125A, switching mode DC/DC step-down µModule regulators
integrated with 4-channel power system manager.

This adds the chip IDs, the checks for the manufacturer special ID, the
switch case for pmbus_driver_info population, and the relevant attributes.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Document support for the LTM4681 and LTM4682 PMBus µModule regulators
added in the previous commit.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Document the compatible strings for the LT7175/LT7175-1 and
LT7176P/LT7176P-1 PMBus buck regulators newly supported by the
ltc2978 driver.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Add support for LT7175/LT7175-1 and LT7176P/LT7176P-1 PMBus buck
regulators. These parts share the LT7170 family MFR_SPECIAL_ID
(0x1C1D masked to 0x1C10) and use the same PMBus register layout,
so they reuse the existing lt7170/lt7171 probe path. Variants are
distinguished by reading the PMBUS_IC_DEVICE_ID ASCII string.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Document support for the LT7175/LT7175-1 and LT7176P/LT7176P-1 PMBus
buck regulators added in the previous commit.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
LT7170L and LT7171L are pin compatible with LT7170 and LT7171 and add
a pulse-skipping mode for improved light-load efficiency. They report
the same MFR_SPECIAL_ID and IC_DEVICE_ID as LT7170 and LT7171 and have
an identical telemetry register set, so document them with a fallback
to the compatible base part.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
LT7170L and LT7171L are pin compatible with LT7170 and LT7171 and add
a pulse-skipping mode for improved light-load efficiency. The
pulse-skipping mode is a configuration setting only; telemetry is
identical.

The L parts report the same MFR_SPECIAL_ID (0x1C1D) and IC_DEVICE_ID
strings ("LT7170", "LT7171", and their -1 variants) as the base parts,
so they cannot be told apart at runtime and are detected as LT7170
and LT7171. Add i2c device IDs and OF compatibles that map them to the
existing chip types.

The i2c device IDs are also required for DT instantiation: the client
name is derived from the first compatible string, so a node using
"lltc,lt7171l", "lltc,lt7171" would otherwise have no matching
i2c_device_id.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>
Document support for the LT7170L and LT7171L PMBus buck regulators.

Signed-off-by: Christopher de Guzman <christopher.deguzman@analog.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant