From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] exynos4: universal: Use the correct regulator names
Date: Thu, 11 Aug 2011 16:47:15 +0900 [thread overview]
Message-ID: <015a01cc57fa$e4d5a930$ae80fb90$%kim@samsung.com> (raw)
In-Reply-To: <20110808095126.GA767@july>
Kyungmin Park wrote:
>
> From: Kyungmin Park <kyungmin.park@samsung.com>
>
> Use the correct regulator names for cpufreq
>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> diff --git a/arch/arm/mach-exynos4/mach-universal_c210.c b/arch/arm/mach-
> exynos4/mach-universal_c210.c
> index 0e280d1..79f0a6f 100644
> --- a/arch/arm/mach-exynos4/mach-universal_c210.c
> +++ b/arch/arm/mach-exynos4/mach-universal_c210.c
> @@ -79,7 +80,7 @@ static struct s3c2410_uartcfg universal_uartcfgs[]
__initdata
> = {
> };
>
> static struct regulator_consumer_supply max8952_consumer =
> - REGULATOR_SUPPLY("vddarm", NULL);
> + REGULATOR_SUPPLY("vdd_arm", NULL);
>
> static struct max8952_platform_data universal_max8952_pdata __initdata =
{
> .gpio_vid0 = EXYNOS4_GPX0(3),
> @@ -105,7 +106,7 @@ static struct max8952_platform_data
> universal_max8952_pdata __initdata = {
> };
>
> static struct regulator_consumer_supply lp3974_buck1_consumer =
> - REGULATOR_SUPPLY("vddint", NULL);
> + REGULATOR_SUPPLY("vdd_int", NULL);
>
> static struct regulator_consumer_supply lp3974_buck2_consumer =
> REGULATOR_SUPPLY("vddg3d", NULL);
OK, applied.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-08-11 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 9:51 [PATCH] exynos4: universal: Use the correct regulator names Kyungmin Park
2011-08-11 7:47 ` Kukjin Kim [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='015a01cc57fa$e4d5a930$ae80fb90$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--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 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.