[PATCH 0/2] Add support for Infineon Digital eFuse XDP730

[PATCH 0/2] Add support for Infineon Digital eFuse XDP730

[ASHISH YADAV]

From: Ashish Yadav <ashish.yadav@infineon.com>

Hi,

These patches add support for Infineon Digital eFuse XDP730.
XDP730 provides accurate system telemetry (V, I, P, T) and
reports analog current at the IMON pin for post-processing.

The Current and Power measurement depends on the RIMON and GIMON values.
Please look into data sheet sections 4.4.2 and 4.4.4 for more details:
https://www.infineon.com/assets/row/public/documents/24/49/infineon-xdp730-001-datasheet-en.pdf

With Best Regards,
 Ashish Yadav

Ashish Yadav (2):
  dt-bindings: hwmon/pmbus: Add Infineon XDP730
  hwmon:(pmbus/xdp730) Add support for efuse xdp730

 .../bindings/hwmon/pmbus/infineon,xdp730.yaml |  59 ++++++++
 drivers/hwmon/pmbus/Kconfig                   |   9 ++
 drivers/hwmon/pmbus/Makefile                  |   1 +
 drivers/hwmon/pmbus/xdp730.c                  | 128 ++++++++++++++++++
 4 files changed, 197 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
 create mode 100644 drivers/hwmon/pmbus/xdp730.c

-- 
2.39.5

[PATCH 1/2] dt-bindings: hwmon/pmbus: Add Infineon XDP730

[ASHISH YADAV]

From: Ashish Yadav <ashish.yadav@infineon.com>

Add documentation for the device tree binding of the XDP730 eFuse.

Signed-off-by: Ashish Yadav <ashish.yadav@infineon.com>
---
 .../bindings/hwmon/pmbus/infineon,xdp730.yaml | 59 +++++++++++++++++++
 1 file changed, 59 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml

diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
new file mode 100644
index 000000000000..a7361a07891c
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
@@ -0,0 +1,59 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+
+$id: http://devicetree.org/schemas/hwmon/pmbus/infineon,xdp730.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Infineon XDP730 Digital eFuse Controller
+
+maintainers:
+  - Ashish Yadav <ashish.yadav@infineon.com>
+
+description: |
+  The XDP730 is an eFuse with integrated current sensor and digital
+  controller. It provides accurate system telemetry (V, I, P, T) and
+  reports analog current at the IMON pin for post-processing.
+
+  Datasheet:
+     https://www.infineon.com/assets/row/public/documents/24/49/infineon-xdp730-001-datasheet-en.pdf
+
+properties:
+  compatible:
+    enum:
+      - infineon,xdp730
+
+  reg:
+    maxItems: 1
+
+  infineon,rimon-micro-ohms:
+    description:
+      The value of the RIMON resistor, in micro ohms, required to enable
+      the system overcurrent protection.
+
+  vdd-vin-supply:
+    description:
+      Supply for the VDD_VIN pin (pin 20), the IC controller power supply.
+      Typically connected to the input bus (VIN) through a 100 ohm / 100 nF
+      RC filter.
+
+required:
+  - compatible
+  - reg
+  - vdd-vin-supply
+
+additionalProperties: false
+
+examples:
+  - |
+    i2c {
+        #address-cells = <1>;
+        #size-cells = <0>;
+
+        hwmon@11 {
+            compatible = "infineon,xdp730";
+            reg = <0x11>;
+            vdd-vin-supply = <&vdd_vin>;
+            infineon,rimon-micro-ohms = <1098000000>;  /* 1.098k ohm */
+        };
+    };
-- 
2.39.5

Re: [PATCH 1/2] dt-bindings: hwmon/pmbus: Add Infineon XDP730

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The device tree example node is named `hwmon@11`, which uses a Linux-specific subsystem name instead of a generic hardware function name.
- [Low] The new device tree binding `infineon,xdp730.yaml` unnecessarily duplicates the schema of the existing `infineon,xdp720.yaml`.
--

commit e021e1d189da7e8470a3c273fdd6ec12f7ed6280
Author: Ashish Yadav <ashish.yadav@infineon.com>

dt-bindings: hwmon/pmbus: Add Infineon XDP730

Add documentation for the device tree binding of the XDP730 eFuse.

> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
> new file mode 100644
> index 0000000000000..a7361a07891c2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +
> +$id: http://devicetree.org/schemas/hwmon/pmbus/infineon,xdp730.yaml#

Does this file needlessly duplicate the existing infineon,xdp720.yaml schema?

The properties, required fields, and constraints here appear identical
to infineon,xdp720.yaml. Creating duplicate YAML schema files for
devices in the same hardware family with identical constraints can
fragment the schemas.

Could the infineon,xdp730 compatible string be added to the enum in the
existing schema file instead?

[ ... ]

> +examples:
> +  - |
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        hwmon@11 {

This isn't a bug, but does this node name follow the Devicetree
specification for generic names?

The spec requires node names to reflect the hardware function
(like efuse@11 or sensor@11), rather than pointing to a specific
OS subsystem like hwmon.

> +            compatible = "infineon,xdp730";
> +            reg = <0x11>;
> +            vdd-vin-supply = <&vdd_vin>;
> +            infineon,rimon-micro-ohms = <1098000000>;  /* 1.098k ohm */
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519075558.91466-1-Ashish.Yadav@infineon.com?part=1

[PATCH 2/2] hwmon:(pmbus/xdp730) Add support for efuse xdp730

[ASHISH YADAV]

From: Ashish Yadav <ashish.yadav@infineon.com>

Add the pmbus driver for Infineon XDP730 Digital eFuse Controller.

Signed-off-by: Ashish Yadav <ashish.yadav@infineon.com>
---
XDP730 Digital eFuse Controller provides accurate system telemetry
(V, I, P, T) and reports analog current at the IMON pin for post-processing.

The Current and Power measurement depends on the RIMON and GIMON values.
Please look into data sheet sections 4.4.2 and 4.4.4 for more details:
https://www.infineon.com/assets/row/public/documents/24/49/infineon-xdp730-001-datasheet-en.pdf

The GIMON (microA/A) depends on the 10th bit of TELEMETRY_AVG PMBUS Register.
The value of RIMON (kohm) can be provided by the user through device tree using
infineon,rimon-micro-ohms  property.
---
 drivers/hwmon/pmbus/Kconfig  |   9 +++
 drivers/hwmon/pmbus/Makefile |   1 +
 drivers/hwmon/pmbus/xdp730.c | 128 +++++++++++++++++++++++++++++++++++
 3 files changed, 138 insertions(+)
 create mode 100644 drivers/hwmon/pmbus/xdp730.c

diff --git a/drivers/hwmon/pmbus/Kconfig b/drivers/hwmon/pmbus/Kconfig
index 8f4bff375ecb..11c26a495e31 100644
--- a/drivers/hwmon/pmbus/Kconfig
+++ b/drivers/hwmon/pmbus/Kconfig
@@ -720,6 +720,15 @@ config SENSORS_XDP720
 	  This driver can also be built as a module. If so, the module will
 	  be called xdp720.
 
+config SENSORS_XDP730
+	tristate "Infineon XDP730 family"
+	help
+	  If you say yes here you get hardware monitoring support for Infineon
+	  XDP730.
+
+	  This driver can also be built as a module. If so, the module will
+	  be called xdp730.
+
 config SENSORS_XDPE152
 	tristate "Infineon XDPE152 family"
 	help
diff --git a/drivers/hwmon/pmbus/Makefile b/drivers/hwmon/pmbus/Makefile
index 7129b62bc00f..32061c2ed29c 100644
--- a/drivers/hwmon/pmbus/Makefile
+++ b/drivers/hwmon/pmbus/Makefile
@@ -70,6 +70,7 @@ obj-$(CONFIG_SENSORS_UCD9000)	+= ucd9000.o
 obj-$(CONFIG_SENSORS_UCD9200)	+= ucd9200.o
 obj-$(CONFIG_SENSORS_XDP710)	+= xdp710.o
 obj-$(CONFIG_SENSORS_XDP720)	+= xdp720.o
+obj-$(CONFIG_SENSORS_XDP730)	+= xdp730.o
 obj-$(CONFIG_SENSORS_XDPE122)	+= xdpe12284.o
 obj-$(CONFIG_SENSORS_XDPE152)	+= xdpe152c4.o
 obj-$(CONFIG_SENSORS_XDPE1A2G7B)	+= xdpe1a2g7b.o
diff --git a/drivers/hwmon/pmbus/xdp730.c b/drivers/hwmon/pmbus/xdp730.c
new file mode 100644
index 000000000000..ea8968de9f26
--- /dev/null
+++ b/drivers/hwmon/pmbus/xdp730.c
@@ -0,0 +1,128 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Hardware monitoring driver for Infineon XDP730 Digital eFuse Controller
+ *
+ * Copyright (c) 2026 Infineon Technologies. All rights reserved.
+ */
+
+#include <linux/i2c.h>
+#include <linux/module.h>
+#include <linux/init.h>
+#include <linux/kernel.h>
+#include <linux/of_device.h>
+#include <linux/bitops.h>
+#include <linux/math64.h>
+#include "pmbus.h"
+
+/*
+ * The IMON resistor required to generate the system overcurrent protection.
+ * Arbitrary default Rimon value: 2k Ohm
+ */
+#define XDP730_DEFAULT_RIMON 2000000000 /* 2k ohm */
+#define XDP730_TELEMETRY_AVG 0xE9
+
+static struct pmbus_driver_info xdp730_info = {
+	.pages = 1,
+	.format[PSC_VOLTAGE_IN] = direct,
+	.format[PSC_VOLTAGE_OUT] = direct,
+	.format[PSC_CURRENT_OUT] = direct,
+	.format[PSC_POWER] = direct,
+	.format[PSC_TEMPERATURE] = direct,
+
+	.m[PSC_VOLTAGE_IN] = 4653,
+	.b[PSC_VOLTAGE_IN] = 0,
+	.R[PSC_VOLTAGE_IN] = -2,
+	.m[PSC_VOLTAGE_OUT] = 4653,
+	.b[PSC_VOLTAGE_OUT] = 0,
+	.R[PSC_VOLTAGE_OUT] = -2,
+	/*
+	 * Current and Power measurement depends on the RIMON (kOhm) and
+	 * GIMON(microA/A) values.
+	 */
+	.m[PSC_CURRENT_OUT] = 24668,
+	.b[PSC_CURRENT_OUT] = 0,
+	.R[PSC_CURRENT_OUT] = -4,
+	.m[PSC_POWER] = 4486,
+	.b[PSC_POWER] = 0,
+	.R[PSC_POWER] = -1,
+	.m[PSC_TEMPERATURE] = 54,
+	.b[PSC_TEMPERATURE] = 22521,
+	.R[PSC_TEMPERATURE] = -1,
+
+	.func[0] = PMBUS_HAVE_VIN | PMBUS_HAVE_VOUT | PMBUS_HAVE_PIN |
+		   PMBUS_HAVE_TEMP | PMBUS_HAVE_IOUT | PMBUS_HAVE_STATUS_INPUT |
+		   PMBUS_HAVE_STATUS_TEMP,
+};
+
+static int xdp730_probe(struct i2c_client *client)
+{
+	struct pmbus_driver_info *info;
+	int ret;
+	u32 rimon;
+	int gimon;
+
+	info = devm_kmemdup(&client->dev, &xdp730_info, sizeof(*info),
+			    GFP_KERNEL);
+	if (!info)
+		return -ENOMEM;
+
+	ret = devm_regulator_get_enable(&client->dev, "vdd-vin");
+	if (ret)
+		return dev_err_probe(&client->dev, ret,
+			"failed to enable vdd-vin supply\n");
+
+	ret = i2c_smbus_read_word_data(client, XDP730_TELEMETRY_AVG);
+	if (ret < 0) {
+		dev_err(&client->dev, "Can't get TELEMETRY_AVG\n");
+		return ret;
+	}
+
+	ret >>= 10; /* 10th bit of TELEMETRY_AVG REG for GIMON Value */
+	ret &= GENMASK(0, 0);
+	if (ret == 1)
+		gimon = 20000; /* output gain 20 microA/A */
+	else
+		gimon = 10000; /* output gain 10 microA/A */
+
+	if (of_property_read_u32(client->dev.of_node,
+				 "infineon,rimon-micro-ohms", &rimon))
+		rimon = XDP730_DEFAULT_RIMON; /* Default if not set via DT */
+	if (rimon == 0)
+		return -EINVAL;
+
+	/* Adapt the current and power scale for each instance */
+	info->m[PSC_CURRENT_OUT] = DIV64_U64_ROUND_CLOSEST((u64)
+		info->m[PSC_CURRENT_OUT] * rimon * gimon, 1000000000000ULL);
+	info->m[PSC_POWER] = DIV64_U64_ROUND_CLOSEST((u64)
+		info->m[PSC_POWER] * rimon * gimon, 1000000000000000ULL);
+
+	return pmbus_do_probe(client, info);
+}
+
+static const struct of_device_id xdp730_of_match[] = {
+	{ .compatible = "infineon,xdp730" },
+	{}
+};
+MODULE_DEVICE_TABLE(of, xdp730_of_match);
+
+static const struct i2c_device_id xdp730_id[] = {
+	{ "xdp730" },
+	{}
+};
+MODULE_DEVICE_TABLE(i2c, xdp730_id);
+
+static struct i2c_driver xdp730_driver = {
+	.driver = {
+		   .name = "xdp730",
+		   .of_match_table = xdp730_of_match,
+	},
+	.probe = xdp730_probe,
+	.id_table = xdp730_id,
+};
+
+module_i2c_driver(xdp730_driver);
+
+MODULE_AUTHOR("Ashish Yadav <ashish.yadav@infineon.com>");
+MODULE_DESCRIPTION("PMBus driver for Infineon XDP730 Digital eFuse Controller");
+MODULE_LICENSE("GPL");
+MODULE_IMPORT_NS("PMBUS");
-- 
2.39.5

Re: [PATCH 2/2] hwmon:(pmbus/xdp730) Add support for efuse xdp730

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] Usage of firmware-specific `of_property_read_u32` instead of firmware-agnostic `device_property_read_u32`.
- [Low] The `xdp730_info` template structure is not marked as `const`.
- [Low] Missing explicit `#include <linux/regulator/consumer.h>` for `devm_regulator_get_enable()`.
--

commit c84eadae1a13e6d451b4eb98ba41bc9f1c1c537c
Author: Ashish Yadav <ashish.yadav@infineon.com>

hwmon:(pmbus/xdp730) Add support for efuse xdp730

Add the pmbus driver for Infineon XDP730 Digital eFuse Controller.

> diff --git a/drivers/hwmon/pmbus/xdp730.c b/drivers/hwmon/pmbus/xdp730.c
> new file mode 100644
> index 0000000000000..ea8968de9f267
> --- /dev/null
> +++ b/drivers/hwmon/pmbus/xdp730.c
> @@ -0,0 +1,128 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Hardware monitoring driver for Infineon XDP730 Digital eFuse Controller
> + *
> + * Copyright (c) 2026 Infineon Technologies. All rights reserved.
> + */
> +
> +#include <linux/i2c.h>
> +#include <linux/module.h>
> +#include <linux/init.h>
> +#include <linux/kernel.h>
> +#include <linux/of_device.h>
> +#include <linux/bitops.h>
> +#include <linux/math64.h>

Is it possible to explicitly include <linux/regulator/consumer.h>?

The driver invokes devm_regulator_get_enable() below but relies on indirect
inclusion, which might break if subsystem headers are refactored in the
future.

> +#include "pmbus.h"
> +
> +/*
> + * The IMON resistor required to generate the system overcurrent protection.
> + * Arbitrary default Rimon value: 2k Ohm
> + */
> +#define XDP730_DEFAULT_RIMON 2000000000 /* 2k ohm */
> +#define XDP730_TELEMETRY_AVG 0xE9
> +
> +static struct pmbus_driver_info xdp730_info = {

Could this template structure be marked as const?

It is copied per-instance during probe via devm_kmemdup(), so declaring it
const would move it to the read-only .rodata section and prevent accidental
modifications.

> +	.pages = 1,
> +	.format[PSC_VOLTAGE_IN] = direct,
> +	.format[PSC_VOLTAGE_OUT] = direct,

[ ... ]

> +	ret >>= 10; /* 10th bit of TELEMETRY_AVG REG for GIMON Value */
> +	ret &= GENMASK(0, 0);
> +	if (ret == 1)
> +		gimon = 20000; /* output gain 20 microA/A */
> +	else
> +		gimon = 10000; /* output gain 10 microA/A */
> +
> +	if (of_property_read_u32(client->dev.of_node,
> +				 "infineon,rimon-micro-ohms", &rimon))

Should this use device_property_read_u32(&client->dev, ...) instead?

Using of_property_read_u32() restricts the driver to Device Tree-based
systems. If the driver is instantiated via ACPI, client->dev.of_node will
be NULL, causing the read to silently fail and fall back to the default value.

device_property_read_u32() from <linux/property.h> would seamlessly support
DT, ACPI, and software nodes.

> +		rimon = XDP730_DEFAULT_RIMON; /* Default if not set via DT */
> +	if (rimon == 0)
> +		return -EINVAL;
> +

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519075558.91466-1-Ashish.Yadav@infineon.com?part=2

Re: [PATCH 0/2] Add support for Infineon Digital eFuse XDP730

[Guenter Roeck]

On 5/19/26 00:55, ASHISH YADAV wrote:
> From: Ashish Yadav <ashish.yadav@infineon.com>
> 
> Hi,
> 
> These patches add support for Infineon Digital eFuse XDP730.
> XDP730 provides accurate system telemetry (V, I, P, T) and
> reports analog current at the IMON pin for post-processing.
> 
> The Current and Power measurement depends on the RIMON and GIMON values.
> Please look into data sheet sections 4.4.2 and 4.4.4 for more details:
> https://www.infineon.com/assets/row/public/documents/24/49/infineon-xdp730-001-datasheet-en.pdf
> 

This driver is 99% identical to the xdp720 driver, except for the gimon
constants. Please add support for this chip to that driver.

Thanks,
Guenter

Re: [PATCH 0/2] Add support for Infineon Digital eFuse XDP730

[ashish yadav]

Hi Guenter,

Thanks for your time and response.
You are entirely correct that the XDP720 and XDP730 drivers are 99% identical.
The only functional difference between the two variants lies within
their GIMON values.

To programmatically identify whether the current target device is an
XDP720 or an XDP730, the system must query the MFR_MODEL register.
Because this register is 8 bytes long, it requires an I2C Block Read
operation to retrieve the model identifier string.
However, some embedded I2C controllers do not natively support I2C Block Reads.
It is precisely due to this hardware controller limitation that we
proposed developing two separate drivers, ensuring reliable
compatibility across different system architectures.

As a better alternative, an elegant solution to consolidate this into
a single driver is to utilize the i2c_transfer() API to read the
MFR_MODEL register.
Please let me know if you have any questions regarding this approach.

With Best Regards,
   Ashish Yadav


On Tue, May 19, 2026 at 8:59 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On 5/19/26 00:55, ASHISH YADAV wrote:
> > From: Ashish Yadav <ashish.yadav@infineon.com>
> >
> > Hi,
> >
> > These patches add support for Infineon Digital eFuse XDP730.
> > XDP730 provides accurate system telemetry (V, I, P, T) and
> > reports analog current at the IMON pin for post-processing.
> >
> > The Current and Power measurement depends on the RIMON and GIMON values.
> > Please look into data sheet sections 4.4.2 and 4.4.4 for more details:
> > https://www.infineon.com/assets/row/public/documents/24/49/infineon-xdp730-001-datasheet-en.pdf
> >
>
> This driver is 99% identical to the xdp720 driver, except for the gimon
> constants. Please add support for this chip to that driver.
>
> Thanks,
> Guenter
>