linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexis Czezar Torreno <alexisczezar.torreno@analog.com>
To: Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>
Cc: <linux-hwmon@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	"Alexis Czezar Torreno" <alexisczezar.torreno@analog.com>
Subject: [PATCH v2 0/2] Add support for ADPM12160 a DC/DC Power Module
Date: Thu, 3 Apr 2025 13:16:17 +0800	[thread overview]
Message-ID: <20250403-dev_adpm12160-v2-0-bbf40faae988@analog.com> (raw)

Before adding the support for ADPM12160, this series includes a commit
to fix the issue with max34451. The family of max344** contains switched
PMBUS addresses 0x46 and 0x4A. For max34451, the version MAX34451ETNA6+
and later fixed this issue and this first commit supports this. The
MFR_REVISION is used to differentiate the different max34451 chips.

The second commit adds the actual driver for adpm12160. ASPM12160 is a
quarter brick DC/DC Power Module. It is a high power non-isolated
converter capable of delivering a fully regulated 12V, with continuous
power level of 1600W with peak power at 2400W for a limited time.
Uses PMBus Configuration.

Signed-off-by: Alexis Czezar Torreno <alexisczezar.torreno@analog.com>
---
Changes in v2:
- Commit 1: MAX34451 Fix
-   Added a flag to denote if the device has correct pmbus address
-   Stored the pmbus address of concern inside max34440_data
-   Removed separate chip ID for max344451etna6+, detects this version
    via MFR_REVISION
-   Reverted max34440.rst to original. No edit deemed necessary
-   Supported READ_VIN, READ_IIN, and STATUS_INPUT for max34451etna6+
- Commit 2: Add ADPM12160
-   Adjusted code to base it on the new max34440.c
- Link to v1: https://lore.kernel.org/r/20250320-dev_adpm12160-v1-0-8f7b975eac75@analog.com

---
Alexis Czezar Torreno (2):
      hwmon: (pmbus/max34440): Fix support for max34451
      hwmon: (pmbus/max3440): add support adpm12160

 Documentation/hwmon/max34440.rst |  30 ++++++++---
 drivers/hwmon/pmbus/max34440.c   | 109 ++++++++++++++++++++++++++++++++++++---
 2 files changed, 124 insertions(+), 15 deletions(-)
---
base-commit: c812cc42f92d3d0b17c01b5db9a1dee5793a1491
change-id: 20250320-dev_adpm12160-5960e77a79be

Best regards,
-- 
Alexis Czezar Torreno <alexisczezar.torreno@analog.com>


             reply	other threads:[~2025-04-03  5:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  5:16 Alexis Czezar Torreno [this message]
2025-04-03  5:16 ` [PATCH v2 1/2] hwmon: (pmbus/max34440): Fix support for max34451 Alexis Czezar Torreno
2025-04-03 16:32   ` Guenter Roeck
2025-04-04  0:28     ` Torreno, Alexis Czezar
2025-04-03  5:16 ` [PATCH v2 2/2] hwmon: (pmbus/max3440): add support adpm12160 Alexis Czezar Torreno

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=20250403-dev_adpm12160-v2-0-bbf40faae988@analog.com \
    --to=alexisczezar.torreno@analog.com \
    --cc=Delphine_CC_Chiu@Wiwynn.com \
    --cc=corbet@lwn.net \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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;
as well as URLs for NNTP newsgroup(s).