From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
netdev@vger.kernel.org,
Steve Glendinning <steve.glendinning@smsc.com>,
Mathieu Poirer <mathieu.poirier@linaro.org>,
Robert Marklund <robert.marklund@stericsson.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/2 v3] net/smsc911x: Add regulator support
Date: Thu, 27 Oct 2011 23:42:41 +0200 [thread overview]
Message-ID: <20111027214241.GA11534@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJaTeTpzFOdgqGH3vDWY8Mdx7zra8R9nUQYHgsEBfy_yGkEWOw@mail.gmail.com>
On Thu, Oct 27, 2011 at 10:59:14PM +0200, Mike Frysinger wrote:
> i saw that !CONFIG_REGULATOR works great. my concern is that these
> boards don't define any regulators for smsc resources, so if
> CONFIG_REGULATOR is enabled to test out unrelated daughter cards, i
> don't want the network driver suddenly failing. Linus' comments
> suggest that this is what would happen unless each board file has its
> smsc platform resources extended. maybe i misunderstood what he was saying ?
That's the case that's handled by CONFIG_REGULATOR_DUMMY - if the lookup
fails the core will provide a virtual regulator to the consumer. If
you're running a setup like that you probably want to enable dummy
regulators anyway.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
netdev@vger.kernel.org,
Steve Glendinning <steve.glendinning@smsc.com>,
Mathieu Poirer <mathieu.poirier@linaro.org>,
Robert Marklund <robert.marklund@stericsson.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/2 v3] net/smsc911x: Add regulator support
Date: Thu, 27 Oct 2011 21:42:41 +0000 [thread overview]
Message-ID: <20111027214241.GA11534@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJaTeTpzFOdgqGH3vDWY8Mdx7zra8R9nUQYHgsEBfy_yGkEWOw@mail.gmail.com>
On Thu, Oct 27, 2011 at 10:59:14PM +0200, Mike Frysinger wrote:
> i saw that !CONFIG_REGULATOR works great. my concern is that these
> boards don't define any regulators for smsc resources, so if
> CONFIG_REGULATOR is enabled to test out unrelated daughter cards, i
> don't want the network driver suddenly failing. Linus' comments
> suggest that this is what would happen unless each board file has its
> smsc platform resources extended. maybe i misunderstood what he was saying ?
That's the case that's handled by CONFIG_REGULATOR_DUMMY - if the lookup
fails the core will provide a virtual regulator to the consumer. If
you're running a setup like that you probably want to enable dummy
regulators anyway.
next prev parent reply other threads:[~2011-10-27 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 12:48 [PATCH 2/2 v3] net/smsc911x: Add regulator support Linus Walleij
2011-10-27 12:48 ` Linus Walleij
2011-10-27 12:48 ` Linus Walleij
2011-10-27 13:21 ` Mike Frysinger
2011-10-27 13:21 ` Mike Frysinger
2011-10-27 15:46 ` Mark Brown
2011-10-27 15:46 ` Mark Brown
2011-10-27 20:59 ` Mike Frysinger
2011-10-27 20:59 ` Mike Frysinger
2011-10-27 21:42 ` Mark Brown [this message]
2011-10-27 21:42 ` Mark Brown
2011-10-27 22:43 ` Mike Frysinger
2011-10-27 22:43 ` Mike Frysinger
2011-10-28 20:33 ` Sascha Hauer
2011-10-28 20:33 ` Sascha Hauer
2011-10-28 23:33 ` Mike Frysinger
2011-10-28 23:33 ` Mike Frysinger
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=20111027214241.GA11534@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=lethal@linux-sh.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=robert.marklund@stericsson.com \
--cc=s.hauer@pengutronix.de \
--cc=steve.glendinning@smsc.com \
--cc=tony@atomide.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/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.