From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: mach-shmobile: mackerel: enable REGULATOR in defconfig
Date: Wed, 13 Feb 2013 14:10:21 +0000 [thread overview]
Message-ID: <20130213141021.GC30293@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.1302131418350.18535@axis700.grange>
On Wed, Feb 13, 2013 at 02:21:53PM +0100, Guennadi Liakhovetski wrote:
> Hi Simon
>
> On Wed, 13 Feb 2013, Simon Horman wrote:
>
> > As well as being a generally sane thing to do this
> > is required for MMCIF to function in conjunction with
> > " ARM: shmobile: streamline mackerel SD and MMC devices".
> >
> > Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >
> > ---
> >
> > v2
> > * Don't enable REGULATOR_DUMMY, it is only intended for development / testing.
> > ---
> > arch/arm/configs/mackerel_defconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/configs/mackerel_defconfig b/arch/arm/configs/mackerel_defconfig
> > index ec8e605..9fb1189 100644
> > --- a/arch/arm/configs/mackerel_defconfig
> > +++ b/arch/arm/configs/mackerel_defconfig
> > @@ -75,6 +75,7 @@ CONFIG_I2C=y
> > CONFIG_I2C_SH_MOBILE=y
> > # CONFIG_HWMON is not set
> > # CONFIG_MFD_SUPPORT is not set
> > +CONFIG_REGULATOR=y
>
> We really don't have to enable CONFIG_REGULATOR_GPIO and
> CONFIG_REGULATOR_FIXED_VOLTAGE? IIRC, CONFIG_REGULATOR_GPIO is so far only
> used on armadillo800eva, but the fixed regulator is required for other
> boards too?
The Kconfig for MACH_ARMADILLO800EVA selects REGULATOR_FIXED_VOLTAGE is
REGULATOR is enabled.
Likewise for kzm9g, mackerel and a bunch of other boards.
next prev parent reply other threads:[~2013-02-13 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 13:11 [PATCH 0/3 v2] ARM: mach-shmobile: defconfig REGULATOR settings Simon Horman
2013-02-13 13:11 ` [PATCH 1/3] ARM: mach-shmobile: mackerel: enable REGULATOR in defconfig Simon Horman
2013-02-13 13:21 ` Guennadi Liakhovetski
2013-02-13 14:10 ` Simon Horman [this message]
2013-02-13 13:11 ` [PATCH 2/3] ARM: mach-shmobile: armadillo800eva: " Simon Horman
2013-02-14 2:48 ` Simon Horman
2013-02-14 7:49 ` Guennadi Liakhovetski
2013-02-14 8:36 ` Simon Horman
2013-02-13 13:11 ` [PATCH 3/3] ARM: mach-shmobile: kzm9g: do not enable REGULATOR_DUMMY " Simon Horman
2013-02-14 8:36 ` Simon Horman
2013-02-14 8:45 ` Guennadi Liakhovetski
2013-02-15 13:13 ` Simon Horman
2013-02-15 13:23 ` Guennadi Liakhovetski
2013-02-15 13:39 ` Simon Horman
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=20130213141021.GC30293@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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