From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Anson Huang <b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] arm: dts: imx6dl: correct cpufreq volt/freq table
Date: Fri, 05 Dec 2014 10:39:15 +0100 [thread overview]
Message-ID: <1417772355.3227.3.camel@pengutronix.de> (raw)
In-Reply-To: <1417767829-11314-2-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Am Freitag, den 05.12.2014, 16:23 +0800 schrieb Anson Huang:
> Currently the cpufreq volt/freq table we used is
> for LDO enable mode, according to latest datasheet
> Rev. 3, 03/2014, the volt/freq table is as below:
>
> LDO enabled(min value):
> 996MHz: VDDARM: 1.225V, VDDSOC: 1.150V;
> 792MHz: VDDARM: 1.150V, VDDSOC: 1.150V;
> 396MHz: VDDARM: 1.050V, VDDSOC: 1.150V;
>From which datasheet is this? I find it unlikely that the LDO enabled
values are not larger than the LDO bypassed ones. I just had a look at
the "i.MXSolo/6DualLite Automotive and Infotainment Applications
Processors" Datasheet (IMX6SDLAEC) Rev. 3, 03/2014 and the "i.MX
6Solo/6DualLite Applications Processors for Consumer Products" Datasheet
(IMX6SDLCEC) Rev. 3, 03/2014, and they both have different values in
Table 9 (Operating Ranges) for the LDO enabled case:
LDO enabled(min value):
996MHz: VDDARM: 1.350V, VDDSOC: 1.275V;
792MHz: VDDARM: 1.275V, VDDSOC: 1.275V;
396MHz: VDDARM: 1.175V, VDDSOC: 1.275V;
> LDO bypassed(min value):
> 996MHz: VDDARM: 1.250V, VDDSOC: 1.150V;
> 792MHz: VDDARM: 1.150V, VDDSOC: 1.150V;
> 396MHz: VDDARM: 1.050V, VDDSOC: 1.150V;
>
> Adding 25mV to cover board IR drop, for LDO enabled
> mode of 996MHz, VDDARM should be 1.250V, so this
> patch updates it.
>
> Signed-off-by: Anson Huang <b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
regards
Philipp
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-05 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 8:23 [PATCH 1/2] arm: dts: imx6q: update cpufreq volt/freq table Anson Huang
[not found] ` <1417767829-11314-1-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-12-05 8:23 ` [PATCH 2/2] arm: dts: imx6dl: correct " Anson Huang
[not found] ` <1417767829-11314-2-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-12-05 9:39 ` Philipp Zabel [this message]
[not found] ` <1417772355.3227.3.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-12-05 9:58 ` Anson.Huang-KZfg59tc24xl57MIdRCFDg
[not found] ` <BN1PR0301MB06282A4A937E613A778CF6A5FF790-RQSpjbwlmjRcEY/EnGXkZZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2014-12-07 10:59 ` Philipp Zabel
2014-12-16 6:35 ` [PATCH 1/2] arm: dts: imx6q: update " Shawn Guo
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=1417772355.3227.3.camel@pengutronix.de \
--to=p.zabel-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).