From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>,
robert.marklund@stericsson.com, netdev@vger.kernel.org,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: Regulator support for smsc911x
Date: Fri, 3 Feb 2012 11:11:34 +0000 [thread overview]
Message-ID: <20120203111133.GD3151@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120203074408.GD1990@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Fri, Feb 03, 2012 at 08:44:08AM +0100, Sascha Hauer wrote:
> On Fri, Feb 03, 2012 at 01:17:23AM -0200, Fabio Estevam wrote:
> > Please advise if I should fix it in Kconfig or defconfig, so that I
> > can submit a patch.
> If you enable it every device will get a regulator when it requests one.
> If for some reason for example the initialization order of your devices
> changes and a device gets probed before the corresponding (real)
> regulator is registered, then this device will continue with the dummy
> regulator and probably won't work.
Hrm, yeah - the dummy regulator support will be totally broken by the
stuff Grant is working on for fixing the general issues with probe
ordering.
> We could a) live with this problem and default enable the dummy
> regulator. We could also b) apply (a fixed version of) the following
> patch which simplifies registration of a dummy regulator. Still it's a
There's also options c) set up the regulators for the board and d) don't
enable the regulator API if the board doesn't use regulators.
> bit annoying to have to fix all users once someone adds regulator
> support for a driver.
Yeah, it's a shame. I really can't see anything else useful we can do
though.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-03 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 1:02 Regulator support for smsc911x Fabio Estevam
2012-02-03 3:17 ` Fabio Estevam
2012-02-03 7:44 ` Sascha Hauer
2012-02-03 11:11 ` Mark Brown [this message]
2012-02-07 19:25 ` Fabio Estevam
2012-02-07 19:39 ` Mark Brown
2012-02-07 20:29 ` Fabio Estevam
2012-02-08 8:31 ` Sascha Hauer
2012-02-08 11:35 ` 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=20120203111133.GD3151@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robert.marklund@stericsson.com \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).