Linux Documentation
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Fred Chen <fredchen.openbmc@gmail.com>,
	"Torreno, Alexis Czezar" <AlexisCzezar.Torreno@analog.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Wensheng Wang <wenswang@yeah.net>, Frank Li <Frank.Li@nxp.com>,
	Brian Chiang <chiang.brian@inventec.com>,
	Cosmo Chou <chou.cosmo@gmail.com>,
	Dixit Parmar <dixitparmar19@gmail.com>,
	Eddie James <eajames@linux.ibm.com>,
	Antoni Pokusinski <apokusinski01@gmail.com>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	Ashish Yadav <ashish.yadav@infineon.com>,
	Syed Arif <arif.syed@hpe.com>,
	ChiShih Tsai <tomtsai764@gmail.com>,
	Abdurrahman Hussain <abdurrahman@nexthop.ai>,
	"Paller, Kim Seer" <KimSeer.Paller@analog.com>,
	Colin Huang <u8813345@gmail.com>,
	Yuxi Wang <Yuxi.Wang@monolithicpower.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 2/2] hwmon: (pmbus) Add driver for Analog Devices MAX20912 and MAX20916
Date: Thu, 9 Jul 2026 08:54:09 -0700	[thread overview]
Message-ID: <5b865eed-ae58-47fc-8d80-e14a76a93050@roeck-us.net> (raw)
In-Reply-To: <ak9gFKkfEgkU_q1G@nsa>

On Thu, Jul 09, 2026 at 09:54:22AM +0100, Nuno Sá wrote:
> > 
> > Based on the MAX20912/16 specs on my hand, these chips do not support
> > PMBUS_PHASE (0x04). Furthermore, the spec only indicates support for VID mode
> > and does not provide m/b/r. Therefore, some of the features you mentioned might
> > be specific to the MAX20826 series.
> 
> I see, phases are not supported using standard PMBUS.
> 

As mentioned in my other e-mail, it can still be supported by the driver.
That is what the chip drivers are for, after all.

> > 
> > Regarding enabling VOUT via GPIO, our platform handles this via the CPLD as
> > part of the hardware power sequencing. Managing this pin through the driver is
> > not a requirement for our system.
> 
> But we cannot assume all systems will behave like the above. But now i
> do wonder about controlling the GPIOs in the driver. In your system you
> clearly did not need to do it. In mine (testing with a rpi) I had to
> use a GPIO (well I could have used hogs or pinctrl). But if you control the pin
> you do gain the ability to turn off the regulator. If you don't it's always on
> (which might be indeed the bulk of the real usecases for these systems).
> 
Agreed. I don't really like it, but if the chip and some specific hardware
mandate it, it should be supported. However, that code also needs to be
tested - an untested implementation would be worse than no implementation.

Note to anyone from Analog listening: It is really unfortunate that I,
as subsystem maintainer, do not have access to datasheets. That means I have
to rely on assumptions and can not really provide actionable feedback other
than guesswork based on the PMBus standard. That feedback may and likely
will miss essential details.

Thanks,
Guenter

  reply	other threads:[~2026-07-09 15:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 12:26 [PATCH 0/2] hwmon: Add support for Analog Devices MAX20912 and MAX20916 Fred Chen
2026-07-07 12:26 ` [PATCH 1/2] dt-bindings: trivial-devices: Add adi max20912 and max20916 Fred Chen
2026-07-07 12:26 ` [PATCH 2/2] hwmon: (pmbus) Add driver for Analog Devices MAX20912 and MAX20916 Fred Chen
2026-07-07 12:33   ` Krzysztof Kozlowski
2026-07-07 13:52   ` Guenter Roeck
2026-07-08  9:19     ` Nuno Sá
2026-07-08 10:50       ` Krzysztof Kozlowski
2026-07-08 11:32         ` Nuno Sá
2026-07-08 18:32           ` Guenter Roeck
2026-07-09  0:58             ` Torreno, Alexis Czezar
2026-07-09  7:23               ` Fred Chen
2026-07-09  8:54                 ` Nuno Sá
2026-07-09 15:54                   ` Guenter Roeck [this message]
2026-07-09 16:09                     ` Nuno Sá
2026-07-09 23:39                       ` Guenter Roeck
2026-07-09 16:12                     ` Nuno Sá
2026-07-09 15:42                 ` Guenter Roeck
2026-07-09 15:35               ` Guenter Roeck

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=5b865eed-ae58-47fc-8d80-e14a76a93050@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=AlexisCzezar.Torreno@analog.com \
    --cc=Frank.Li@nxp.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=KimSeer.Paller@analog.com \
    --cc=Yuxi.Wang@monolithicpower.com \
    --cc=abdurrahman@nexthop.ai \
    --cc=apokusinski01@gmail.com \
    --cc=arif.syed@hpe.com \
    --cc=ashish.yadav@infineon.com \
    --cc=chiang.brian@inventec.com \
    --cc=chou.cosmo@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dixitparmar19@gmail.com \
    --cc=eajames@linux.ibm.com \
    --cc=fredchen.openbmc@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=thorsten.blum@linux.dev \
    --cc=tomtsai764@gmail.com \
    --cc=u8813345@gmail.com \
    --cc=wenswang@yeah.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