All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>, Jean Delvare <khali@linux-fr.org>
Cc: LM Sensors <lm-sensors@lm-sensors.org>,
	linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	Wei Ni <wni@nvidia.com>
Subject: Re: [lm-sensors] lm90 driver no longer working on PCs in 3.13
Date: Sun, 26 Jan 2014 21:40:30 +0000	[thread overview]
Message-ID: <52E580CE.8080100@roeck-us.net> (raw)
In-Reply-To: <20140126212256.GK11727@sirena.org.uk>

On 01/26/2014 01:22 PM, Mark Brown wrote:
> On Sun, Jan 26, 2014 at 09:49:36PM +0100, Jean Delvare wrote:
>> On Sun, 26 Jan 2014 12:44:38 -0800, Guenter Roeck wrote:
>
>>> Maybe there is some configuration option, or maybe something needs to be
>>> configured from user space. I found neither.
>
>> Neither would be acceptable to my eyes anyway. Things worked out of the
>> box before, they should keep working out of the box.
>
> They only worked with a debug option turned on and generated warnings
> every time they were used...  that kernel config would've been actively
> broken for devices that wanted to do anything at all interesting with
> the regulators and would've been prone to issues with init ordering and
> races in any cases where there are actually regulators.
>
>>> Another possible fix would be to have the regulator core return -ENODEV
>>> instead of -EPROBE_DEFER on non-dt systems. No idea if this would be acceptable
>>> or even feasible.
>
>> Well, either the regulator subsystem gets fixed (or provides a suitable
>> API for drivers like lm90 and we update the lm90 driver to use it), or
>> I'll just revert the problematic commit for now. This is a severe
>> regression, we just can't leave things that way.
>
> It's not an issue in the driver, it's an issue in the combination of the
> platform and the kernel config.  If the regulator API is going to be
> turned on for the platform then either the platform needs to configure
> the supplies or it needs to tell the regulator core that it's safe to
> start using dummy regulators.
>
> What is this platform and why does it have the regulator API enabled in
> the first place?
>

It is a PC running Ubuntu. you'd have to ask the distro maintainers why they
turn on regulators.

config-3.8.0-26-generic:CONFIG_REGULATOR=y
config-3.8.0-35-generic:CONFIG_REGULATOR=y
config-3.11.0-13-generic:CONFIG_REGULATOR=y

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>, Jean Delvare <khali@linux-fr.org>
Cc: LM Sensors <lm-sensors@lm-sensors.org>,
	linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	Wei Ni <wni@nvidia.com>
Subject: Re: lm90 driver no longer working on PCs in 3.13
Date: Sun, 26 Jan 2014 13:40:30 -0800	[thread overview]
Message-ID: <52E580CE.8080100@roeck-us.net> (raw)
In-Reply-To: <20140126212256.GK11727@sirena.org.uk>

On 01/26/2014 01:22 PM, Mark Brown wrote:
> On Sun, Jan 26, 2014 at 09:49:36PM +0100, Jean Delvare wrote:
>> On Sun, 26 Jan 2014 12:44:38 -0800, Guenter Roeck wrote:
>
>>> Maybe there is some configuration option, or maybe something needs to be
>>> configured from user space. I found neither.
>
>> Neither would be acceptable to my eyes anyway. Things worked out of the
>> box before, they should keep working out of the box.
>
> They only worked with a debug option turned on and generated warnings
> every time they were used...  that kernel config would've been actively
> broken for devices that wanted to do anything at all interesting with
> the regulators and would've been prone to issues with init ordering and
> races in any cases where there are actually regulators.
>
>>> Another possible fix would be to have the regulator core return -ENODEV
>>> instead of -EPROBE_DEFER on non-dt systems. No idea if this would be acceptable
>>> or even feasible.
>
>> Well, either the regulator subsystem gets fixed (or provides a suitable
>> API for drivers like lm90 and we update the lm90 driver to use it), or
>> I'll just revert the problematic commit for now. This is a severe
>> regression, we just can't leave things that way.
>
> It's not an issue in the driver, it's an issue in the combination of the
> platform and the kernel config.  If the regulator API is going to be
> turned on for the platform then either the platform needs to configure
> the supplies or it needs to tell the regulator core that it's safe to
> start using dummy regulators.
>
> What is this platform and why does it have the regulator API enabled in
> the first place?
>

It is a PC running Ubuntu. you'd have to ask the distro maintainers why they
turn on regulators.

config-3.8.0-26-generic:CONFIG_REGULATOR=y
config-3.8.0-35-generic:CONFIG_REGULATOR=y
config-3.11.0-13-generic:CONFIG_REGULATOR=y

Guenter


  reply	other threads:[~2014-01-26 21:40 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 19:28 [lm-sensors] lm90 driver no longer working on PCs in 3.13 Guenter Roeck
2014-01-26 19:28 ` Guenter Roeck
2014-01-26 20:13 ` [lm-sensors] " Jean Delvare
2014-01-26 20:13   ` Jean Delvare
2014-01-26 20:42   ` [lm-sensors] " Mark Brown
2014-01-26 20:42     ` Mark Brown
2014-01-26 20:44   ` [lm-sensors] " Guenter Roeck
2014-01-26 20:44     ` Guenter Roeck
2014-01-26 20:49     ` [lm-sensors] " Jean Delvare
2014-01-26 20:49       ` Jean Delvare
2014-01-26 21:22       ` [lm-sensors] " Mark Brown
2014-01-26 21:22         ` Mark Brown
2014-01-26 21:40         ` Guenter Roeck [this message]
2014-01-26 21:40           ` Guenter Roeck
2014-01-26 21:53           ` [lm-sensors] " Mark Brown
2014-01-26 21:53             ` Mark Brown
2014-01-26 22:02             ` [lm-sensors] " Guenter Roeck
2014-01-26 22:02               ` Guenter Roeck
2014-01-26 23:37               ` [lm-sensors] " Mark Brown
2014-01-26 23:37                 ` Mark Brown
2014-01-26 21:44         ` [lm-sensors] " Jean Delvare
2014-01-26 21:44           ` Jean Delvare
2014-01-26 23:15           ` [lm-sensors] " Mark Brown
2014-01-26 23:15             ` Mark Brown
2014-01-27 10:10             ` [lm-sensors] " Geert Uytterhoeven
2014-01-27 10:10               ` Geert Uytterhoeven
2014-01-27 13:18               ` [lm-sensors] " Mark Brown
2014-01-27 13:18                 ` Mark Brown
2014-01-26 21:50       ` [lm-sensors] " Guenter Roeck
2014-01-26 21:50         ` Guenter Roeck
2014-01-26 22:04         ` [lm-sensors] " Guenter Roeck
2014-01-26 22:04           ` Guenter Roeck
2014-01-26 23:51           ` Mark Brown
2014-01-26 23:51             ` Mark Brown
2014-01-27  4:16             ` Guenter Roeck
2014-01-27  4:16               ` Guenter Roeck
2014-01-27 10:34               ` Mark Brown
2014-01-27 10:34                 ` Mark Brown
2014-01-27 17:19             ` Stephen Warren
2014-01-27 17:19               ` Stephen Warren
2014-01-27 18:50               ` Guenter Roeck
2014-01-27 18:50                 ` Guenter Roeck
2014-01-27 22:04                 ` Jean Delvare
2014-01-27 22:04                   ` Jean Delvare
2014-01-27 23:41                   ` Guenter Roeck
2014-01-27 23:41                     ` Guenter Roeck
2014-01-27 23:58                     ` Mark Brown
2014-01-27 23:58                       ` Mark Brown
2014-01-28  2:33                       ` Guenter Roeck
2014-01-28  2:33                         ` Guenter Roeck
2014-01-28 10:24                         ` Mark Brown
2014-01-28 10:24                           ` Mark Brown
2014-01-28 12:34                   ` Mark Brown
2014-01-28 12:34                     ` Mark Brown
2014-01-27 22:36                 ` Mark Brown
2014-01-27 22:36                   ` Mark Brown
2014-01-26 20:52     ` Mark Brown
2014-01-26 20:52       ` Mark Brown
2014-01-26 21:47       ` [lm-sensors] " Guenter Roeck
2014-01-26 21:47         ` Guenter Roeck
2014-01-26 22:01         ` [lm-sensors] " Mark Brown
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=52E580CE.8080100@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=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 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.