From: Philipp Zabel <pza-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: "Anson.Huang-KZfg59tc24xl57MIdRCFDg@public.gmane.org"
<Anson.Huang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
<kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] arm: dts: imx6dl: correct cpufreq volt/freq table
Date: Sun, 7 Dec 2014 11:59:25 +0100 [thread overview]
Message-ID: <20141207105925.GA11699@pengutronix.de> (raw)
In-Reply-To: <BN1PR0301MB06282A4A937E613A778CF6A5FF790-RQSpjbwlmjRcEY/EnGXkZZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
On Fri, Dec 05, 2014 at 09:58:15AM +0000, Anson.Huang-KZfg59tc24xl57MIdRCFDg@public.gmane.org wrote:
> Hi, Philipp
> The table you listed is VDDARM_IN and VDDSOC_IN which is for external PMIC and we normally do NOT adjust them when cpufreq change, we only adjust the internel LDO output, my table is for VDDARM_CAP and VDDSOC_CAP which are in the comment column, for LDO output.
>
> For LDO enabled mode, VDDARM/SOC_CAP is the output of LDO, we pass this table to kernel opp.
> For LDO bypassed mode, VDDARM/SOC_IN = VDDARM/SOC_CAP.
Now I feel stupid. Obviously the operating-points' CPU voltages are at the
LDO output and shouldn't change if the LDO is bypassed. Thank you for the
clarification, and sorry for not thinking this through at first. After
looking at the correct column, feel free to consider this change
Reviewed-by: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@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-07 10:59 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
[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 [this message]
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=20141207105925.GA11699@pengutronix.de \
--to=pza-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=Anson.Huang-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=p.zabel-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).