From: Guenter Roeck <linux@roeck-us.net>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Marcello Sylvester Bauer <sylv@sylv.io>,
Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v2 1/1] hwmon: (pmbus) Add regulator supply into macro
Date: Fri, 4 Nov 2022 16:42:50 -0700 [thread overview]
Message-ID: <20221104234250.GB2443898@roeck-us.net> (raw)
In-Reply-To: <Y2WShmSmnEjpgVEE@hatter.bewilderbeest.net>
On Fri, Nov 04, 2022 at 03:30:30PM -0700, Zev Weiss wrote:
> On Tue, Feb 22, 2022 at 08:51:04AM PST, Guenter Roeck wrote:
> > On Mon, Feb 21, 2022 at 12:09:56PM +0100, Marcello Sylvester Bauer wrote:
> > > Add regulator supply into PWBUS_REGULATOR macro. This makes it optional
> > > to define a vin-supply in DT. Not defining a supply will add a dummy
> > > regulator supply instead and only cause the following debug output:
> > >
> > > ```
> > > Looking up vin-supply property in node [...] failed
> > > ```
> > >
> > > Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io>
> >
> > Applied to hwmon-next. That should give it some time to mature,
> > and we can pull or modify it if it causes any problems.
> >
>
> Wish I'd caught this sooner, but unfortunately I've just discovered that
> this does in fact cause breakage on my systems -- having regulator-dummy set
> as a supply on my PMBus regulators (instead of having them as their own
> top-level regulators without an upstream supply) leads to enable-count
> underflow errors when disabling them:
>
> # echo 0 > /sys/bus/platform/devices/efuse01/state
> [ 906.094477] regulator-dummy: Underflow of regulator enable count
> [ 906.100563] Failed to disable vout: -EINVAL
> [ 136.992676] reg-userspace-consumer efuse01: Failed to configure state: -22
>
> A simple revert solves the problem for me, but since I'm honestly a little
> unclear on the intent of the patch itself I'm not sure what a revert might
> break and hence I don't know if that's necessarily the right fix. Marcello
> (or others), any thoughts?
Revert now, ask questions later. I'll send a patch.
Guenter
>
>
> Thanks,
> Zev
>
next prev parent reply other threads:[~2022-11-04 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 11:09 [PATCH v2 0/1] Add supply into PWBUS_REGULATOR macro Marcello Sylvester Bauer
2022-02-21 11:09 ` [PATCH v2 1/1] hwmon: (pmbus) Add regulator supply into macro Marcello Sylvester Bauer
2022-02-22 16:51 ` Guenter Roeck
2022-11-04 22:30 ` Zev Weiss
2022-11-04 23:42 ` Guenter Roeck [this message]
2022-11-05 1:43 ` Marcello Sylverster Bauer
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=20221104234250.GB2443898@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.rudolph@9elements.com \
--cc=sylv@sylv.io \
--cc=zev@bewilderbeest.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
all inboxes | Powered by JetHome®