From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
robert.marklund@stericsson.com, netdev@vger.kernel.org,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: Regulator support for smsc911x
Date: Tue, 7 Feb 2012 19:39:14 +0000 [thread overview]
Message-ID: <20120207193914.GA31557@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOMZO5B2_yq=m8Mer=iV-HsXvF-MZJ-BV2=LTg1CZN+O=yepSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Tue, Feb 07, 2012 at 05:25:48PM -0200, Fabio Estevam wrote:
> On Fri, Feb 3, 2012 at 9:11 AM, Mark Brown
> > 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.
> Option c would require that we change every single board.
Well, yes.
> The patch below does option d.
> What do you think?
Absolutely not. Putting conditional code like this in drivers is nuts,
you would have to do the same thing in every single driver which is not
a useful use of anyone's time. This is *clearly* a generic thing and
should therefore be handled in generic code for the same reason we don't
have driver specific platform data for actual usage of the API.
Really, anyone who wants this sort of thing should just enable dummy
regulators - it's exactly what you're implementing. I'm pretty sure
your board does actually have power supplies for the chip, you've just
not told software about them.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-07 19:39 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
2012-02-07 19:25 ` Fabio Estevam
2012-02-07 19:39 ` Mark Brown [this message]
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=20120207193914.GA31557@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 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.