From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Jean Delvare <khali@linux-fr.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Liam Girdwood <lgirdwood@gmail.com>, Wei Ni <wni@nvidia.com>,
linux-kernel@vger.kernel.org,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] lm90 driver no longer working on PCs in 3.13
Date: Mon, 27 Jan 2014 18:33:44 -0800 [thread overview]
Message-ID: <52E71708.7010607@roeck-us.net> (raw)
In-Reply-To: <20140127235815.GA8513@sirena.org.uk>
On 01/27/2014 03:58 PM, Mark Brown wrote:
> On Mon, Jan 27, 2014 at 03:41:35PM -0800, Guenter Roeck wrote:
>
>> I'll test Mark's two patches on my system and let you know the results.
>> After looking some more into it, those _may_ actually fix the problem at least
>> for systems supporting ACPI. No promise, though, and I am not sure if that
>> would be sufficient (it may still not work on non-ACPI PCs). But then who
>
> They should fix ACPI systems, if they don't we need to fix them further
> - that case should just work, it was an oversight not to have a patch
> like the ACPI one in already. I'm not sure how many non-ACPI PCs still
> exist, we're definitely talking about things over 10 years old (even
> before PCs became ACPI only they started to have ACPI present which
> should be sufficient).
>
> Jean, I'm doing a writeup but it's probably not going to be done today.
>
I confirmed that your two patches ("regulator: core: Correct default
return value for full constraints" and "ACPI: Flag use of ACPI and ACPI
idioms for power supplies to regulator API") together fix the problem
with the lm90 driver, at least for ACPI based systems.
Thanks,
Guenter
next prev parent reply other threads:[~2014-01-28 2:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 19:28 lm90 driver no longer working on PCs in 3.13 Guenter Roeck
2014-01-26 20:13 ` Jean Delvare
2014-01-26 20:42 ` Mark Brown
2014-01-26 20:44 ` Guenter Roeck
2014-01-26 20:49 ` Jean Delvare
2014-01-26 21:22 ` Mark Brown
2014-01-26 21:40 ` Guenter Roeck
2014-01-26 21:53 ` Mark Brown
2014-01-26 22:02 ` Guenter Roeck
2014-01-26 23:37 ` Mark Brown
2014-01-26 21:44 ` Jean Delvare
2014-01-26 23:15 ` Mark Brown
2014-01-27 10:10 ` Geert Uytterhoeven
2014-01-27 13:18 ` Mark Brown
2014-01-26 21:50 ` Guenter Roeck
2014-01-26 22:04 ` [lm-sensors] " Guenter Roeck
2014-01-26 23:51 ` Mark Brown
2014-01-27 4:16 ` Guenter Roeck
2014-01-27 10:34 ` Mark Brown
2014-01-27 17:19 ` Stephen Warren
2014-01-27 18:50 ` Guenter Roeck
2014-01-27 22:04 ` Jean Delvare
2014-01-27 23:41 ` Guenter Roeck
2014-01-27 23:58 ` Mark Brown
2014-01-28 2:33 ` Guenter Roeck [this message]
2014-01-28 10:24 ` Mark Brown
2014-01-28 12:34 ` Mark Brown
2014-01-27 22:36 ` Mark Brown
2014-01-26 20:52 ` Mark Brown
2014-01-26 21:47 ` Guenter Roeck
2014-01-26 22:01 ` Mark Brown
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=52E71708.7010607@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=khali@linux-fr.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=swarren@wwwdotorg.org \
--cc=wni@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox