From: Aleksander Mazur <deweloper@wp.pl>
To: Guenter Roeck <linux@roeck-us.net>,
Matti Vaittinen <mazziesaccount@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: Regression in lm90 driver regarding GMT g781
Date: Sat, 20 Apr 2024 22:38:24 +0200 [thread overview]
Message-ID: <20240420223824.624e725b@mocarz> (raw)
In-Reply-To: <abc624f1-e1cf-4933-b2e8-a6f3d46d38ef@roeck-us.net>
Dnia 2024-04-20, o godz. 11:14:06
Guenter Roeck <linux@roeck-us.net> napisał(a):
> On Sat, Apr 20, 2024 at 06:34:27PM +0200, Aleksander Mazur wrote:
> > Hello,
> >
> > I have a Wyse C00X thin client which is apparently equipped with GMT g781.
> > It is (or used to be) supported by lm90 driver. (I have a log from 2020
> > where it was simply working fine; it was kernel version 5.6.0 then.)
> > Now, with 6.8.7, I get following error:
> >
> > > lm90 0-004c: Failed to enable regulator: -ENODEV
> >
> > However, when I just turned this message into a warning and let the driver
> > continue, it seems to work fine, providing temp1 and temp2 as previously.
> >
> > Do you have an idea what could cause such a regression, and if this change
> > (I mean: simply not returning error from devm_regulator_get_enable) is safe?
> >
>
> Do you have CONFIG_REGULATOR enabled in your system ?
>
> Guenter
No, it's disabled (and it was disabled in 5.6.0 as well).
Shouldn't devm_regulator_get_enable*() stubs return success instead of -ENODEV?
--
Aleksander Mazur
next prev parent reply other threads:[~2024-04-20 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 16:34 Regression in lm90 driver regarding GMT g781 Aleksander Mazur
2024-04-20 18:14 ` Guenter Roeck
2024-04-20 20:38 ` Aleksander Mazur [this message]
2024-04-20 21:20 ` Guenter Roeck
2024-04-22 5:52 ` Matti Vaittinen
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=20240420223824.624e725b@mocarz \
--to=deweloper@wp.pl \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mazziesaccount@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.