From: Fabio Estevam <festevam@gmail.com>
To: Anson Huang <b20788@freescale.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
rjw@rjwysocki.net, Viresh Kumar <viresh.kumar@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH V3 1/2] ARM: imx: add vddsoc/pu setpoint info into dts
Date: Wed, 18 Dec 2013 09:08:12 -0200 [thread overview]
Message-ID: <CAOMZO5DCGOkUtWmEok-uEFsUpGLF+93Vhm9XFs02yH9Z+eV0uQ@mail.gmail.com> (raw)
In-Reply-To: <1387402010-31749-1-git-send-email-b20788@freescale.com>
Hi Anson,
On Wed, Dec 18, 2013 at 7:26 PM, Anson Huang <b20788@freescale.com> wrote:
> + Documentation/devicetree/bindings/regulator/regulator.txt for details.
> + arm-supply: vddarm input.
> + pu-supply: vddpu input.
> + soc-supply: vddsoc input.
I found these messages confusing, as someone may think that you are
referring to the VDD_ARM_IN/VDD_ARM23_IN and VDD_SOC_IN, which are
really inputs.
What about doing this instead?
arm-supply: VDDARM LDO output
pu-supply: VDDPU LDO output
soc-supply: VDDSOC LDO output
Regards,
Fabio Estevam
next prev parent reply other threads:[~2013-12-18 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 21:26 [PATCH V3 1/2] ARM: imx: add vddsoc/pu setpoint info into dts Anson Huang
2013-12-18 11:08 ` Fabio Estevam [this message]
2013-12-18 12:01 ` Anson.Huang
2013-12-19 2:13 ` Anson.Huang
2013-12-19 2:30 ` Fabio Estevam
2013-12-18 14:21 ` Shawn Guo
2013-12-18 23:31 ` Anson.Huang
2013-12-18 21:26 ` [PATCH V3 2/2] cpufreq: imx6q: correct VDDSOC/PU voltage scaling when cpufreq is changed Anson Huang
2013-12-18 14:25 ` Shawn Guo
2014-01-03 9:52 ` Anson.Huang
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=CAOMZO5DCGOkUtWmEok-uEFsUpGLF+93Vhm9XFs02yH9Z+eV0uQ@mail.gmail.com \
--to=festevam@gmail.com \
--cc=b20788@freescale.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shawn.guo@linaro.org \
--cc=viresh.kumar@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).