From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: select the fixed regulator driver on several boards
Date: Fri, 06 Jul 2012 07:08:53 +0000 [thread overview]
Message-ID: <20120706070853.GA9317@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1207051517430.30191@axis700.grange>
On Fri, Jul 06, 2012 at 08:36:59AM +0200, Guennadi Liakhovetski wrote:
> (added Rafael to CC, because this equally applies to the ARM Kconfig
> patch)
>
> On Fri, 6 Jul 2012, Paul Mundt wrote:
>
> > On Thu, Jul 05, 2012 at 03:18:50PM +0200, Guennadi Liakhovetski wrote:
> > > On systems, using regulators to supply power to devices, if the REGULATOR
> > > Kconfig option is disabled, regulator API stubs will be used, which often
> > > suffices to bring a default configuration up. If REGULATOR is enabled but
> > > respective regulator drivers are inactive, the real regulator API calls
> > > will be used, which in the absence of drivers will fail to provide
> > > services. This patch prevents such a problem on sh-mobile boards by
> > > forcing REGULATOR_FIXED_VOLTAGE on if REGULATOR is selected.
> > >
> > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> >
> > I suppose this just applies on top of your existing changes on the
> > sh/regulator topic branch?
>
> It should be safe to apply to any state - before or after my patches. My
> previous patches did not touch Kconfig, and this patch just selects the
> fixed regulator, which certainly should cause no problems if no regulators
> are used either.
>
Ok, I wasn't sure if the symbol was provided there or not, but seems that
it's already upstream, so we don't have to worry about select causing
build noise regarding undefined symbols. I'll roll it on top of the
sh/regulator topic branch regardless, though.
prev parent reply other threads:[~2012-07-06 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 13:18 [PATCH] sh: select the fixed regulator driver on several boards Guennadi Liakhovetski
2012-07-06 0:36 ` Paul Mundt
2012-07-06 6:36 ` Guennadi Liakhovetski
2012-07-06 7:08 ` Paul Mundt [this message]
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=20120706070853.GA9317@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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 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).