From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: kzm9g: add REGULATOR settings to kzm9g_defconfig
Date: Wed, 04 Jul 2012 10:46:29 +0000 [thread overview]
Message-ID: <20120704104629.GC15679@linux-sh.org> (raw)
In-Reply-To: <4FF2C282.5030000@kmckk.co.jp>
On Wed, Jul 04, 2012 at 07:41:09PM +0900, Magnus Damm wrote:
> On Wed, Jul 4, 2012 at 7:38 PM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Wed, Jul 04, 2012 at 12:40:56PM +0200, Rafael J. Wysocki wrote:
> >
> >> Well, if arch-wide, then perhaps we don't need REGULATOR_FIXED_VOLTAGE at all
> >> and we can just make things depending on it depend on REGULATOR directly?
> >
> >> The meaning of what you're proposing above is pretty much
> >> "REGULATOR_FIXED_VOLTAGE should be set whenever REGULATOR is" and I guess
> >> REGULATOR_FIXED_VOLTAGE depends on REGULATOR, so they appear to be equivalent.
> >
> >> How much code does really depend on REGULATOR_FIXED_VOLTAGE which is not build
> >> when REGULATOR is set?
> >
> > No, that won't help - the problem is that we want a specific regulator
> > driver to be built in order to ensure that the services it provides are
> > available.
>
> Right, so what's wrong with having a "select REGULATOR_FIXED_VOLTAGE"
> on boards that make use of them? That seems to be the most
> straightforward way to me.
>
Yes, agreed. This is not very different from the gpiolib have/want case,
either, and going that on a board-specific level worked out fine.
next prev parent reply other threads:[~2012-07-04 10:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 9:59 [PATCH] ARM: shmobile: kzm9g: add REGULATOR settings to kzm9g_defconfig Tetsuyuki Kobayashi
2012-07-03 10:06 ` Mark Brown
2012-07-03 10:12 ` Guennadi Liakhovetski
2012-07-03 10:31 ` Tetsuyuki Kobayashi
2012-07-03 11:15 ` Tetsuyuki Kobayashi
2012-07-03 12:44 ` Guennadi Liakhovetski
2012-07-03 13:22 ` Mark Brown
2012-07-03 13:44 ` Guennadi Liakhovetski
2012-07-03 14:45 ` Mark Brown
2012-07-03 15:05 ` Guennadi Liakhovetski
2012-07-03 15:06 ` Mark Brown
2012-07-03 15:35 ` Guennadi Liakhovetski
2012-07-03 19:33 ` Mark Brown
2012-07-04 6:39 ` Guennadi Liakhovetski
2012-07-04 10:38 ` Mark Brown
2012-07-04 10:40 ` Rafael J. Wysocki
2012-07-04 10:41 ` Magnus Damm
2012-07-04 10:46 ` Paul Mundt [this message]
2012-07-04 10:48 ` Mark Brown
2012-07-04 10:51 ` Guennadi Liakhovetski
2012-07-04 10:53 ` Guennadi Liakhovetski
2012-07-04 10:55 ` Rafael J. Wysocki
2012-07-04 10:58 ` Magnus Damm
2012-07-04 11:00 ` Magnus Damm
2012-07-04 11:05 ` Guennadi Liakhovetski
2012-07-04 11:08 ` Guennadi Liakhovetski
2012-07-04 11:22 ` Rafael J. Wysocki
2012-07-04 13:31 ` Magnus Damm
2012-07-04 14:29 ` 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=20120704104629.GC15679@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 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.