From: Tomasz Figa <tomasz.figa@gmail.com>
To: Tushar Behera <tushar.behera@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
patches@linaro.org, broonie@kernel.org, swarren@wwwdotorg.org,
grant.likely@linaro.org, rob.herring@calxeda.com,
l.majewski@samsung.com, s.nawrocki@samsung.com,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] ARM: dts: Update vdd_arm regulator
Date: Sat, 08 Jun 2013 13:52:04 +0200 [thread overview]
Message-ID: <1975506.ECnduUFuut@flatron> (raw)
In-Reply-To: <1370516572-313-1-git-send-email-tushar.behera@linaro.org>
Hi Tushar,
On Thursday 06 of June 2013 16:32:52 Tushar Behera wrote:
> Cpufreq driver for EXYNOS4210 is not a platform driver, hence it is not
> possible to provide the regulator supply name through DT bindings.
> Since the cpufreq driver requires the regulator to be named as
> 'vdd_arm', the related regulator name should be kept same.
>
> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
> ---
> arch/arm/boot/dts/exynos4210-origen.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/exynos4210-origen.dts
> b/arch/arm/boot/dts/exynos4210-origen.dts index bcf8079..bd5f589 100644
> --- a/arch/arm/boot/dts/exynos4210-origen.dts
> +++ b/arch/arm/boot/dts/exynos4210-origen.dts
> @@ -192,7 +192,7 @@
> };
>
> buck1_reg: BUCK1 {
> - regulator-name = "VDD_ARM_1.2V";
> + regulator-name = "vdd_arm";
Yes, this is the hack I mentioned in my review of
[PATCH 0/2] Clock update for EXYNOS4210-CPUFREQ driver
Best regards,
Tomasz
> regulator-min-microvolt =
<950000>;
> regulator-max-microvolt =
<1350000>;
> regulator-always-on;
next parent reply other threads:[~2013-06-08 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370516572-313-1-git-send-email-tushar.behera@linaro.org>
2013-06-08 11:52 ` Tomasz Figa [this message]
2013-06-10 3:44 ` [PATCH] ARM: dts: Update vdd_arm regulator Tushar Behera
2013-06-20 11:10 ` Tushar Behera
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=1975506.ECnduUFuut@flatron \
--to=tomasz.figa@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=tushar.behera@linaro.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).