From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vexpress_defconfig: Enable voltage regulators
Date: Mon, 01 Jul 2013 16:34:22 +0100 [thread overview]
Message-ID: <1372692862.3716.57.camel@linaro1.home> (raw)
In-Reply-To: <1370901015-4159-1-git-send-email-christoffer.dall@linaro.org>
On Mon, 2013-06-10 at 14:50 -0700, Christoffer Dall wrote:
> Enable the Versatile Express voltage regulators by default.
>
> This should work on all verstatile express platforms and not enabling it
> prevents a defconfig'ed kernel from using the SD card controller on the
> qemu emulated platform, which is unfortunate for first-time casual
> users.
>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
> arch/arm/configs/vexpress_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm/configs/vexpress_defconfig b/arch/arm/configs/vexpress_defconfig
> index f2de51f..17104d9 100644
> --- a/arch/arm/configs/vexpress_defconfig
> +++ b/arch/arm/configs/vexpress_defconfig
> @@ -138,3 +138,6 @@ CONFIG_DEBUG_LL=y
> CONFIG_EARLY_PRINTK=y
> # CONFIG_CRYPTO_ANSI_CPRNG is not set
> # CONFIG_CRYPTO_HW is not set
> +CONFIG_REGULATOR=y
> +CONFIG_REGULATOR_FIXED_VOLTAGE=y
> +CONFIG_REGULATOR_VEXPRESS=y
>From my testing, only the CONFIG_REGULATOR=y is required to get MMC
working on real hardware with Linux 3.10. Is CONFIG_REGULATOR_VEXPRESS
actually required to get QEMU working properly?
We definitely don't need CONFIG_REGULATOR_FIXED_VOLTAGE because config
ARCH_VEXPRESS has "select REGULATOR_FIXED_VOLTAGE if REGULATOR".
--
Tixy
prev parent reply other threads:[~2013-07-01 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 21:50 [PATCH] ARM: vexpress_defconfig: Enable voltage regulators Christoffer Dall
2013-07-01 15:34 ` Jon Medhurst (Tixy) [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=1372692862.3716.57.camel@linaro1.home \
--to=tixy@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).