From: Stephen Warren <swarren@wwwdotorg.org>
To: Stefan Agner <stefan@agner.ch>,
thierry.reding@gmail.com, dev@lynxeye.de, lee.jones@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org
Cc: kai.poggensee@avionic-design.de, sameo@linux.intel.com,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] ARM: tegra: correct Colibri T20 regulator settings
Date: Thu, 05 Dec 2013 10:12:43 -0700 [thread overview]
Message-ID: <52A0B40B.7040903@wwwdotorg.org> (raw)
In-Reply-To: <fc7440a2f4bf9ab95e47a911c0e0b3b6a2250356.1386108712.git.stefan@agner.ch>
On 12/03/2013 03:18 PM, Stefan Agner wrote:
> Set the parent of the regulators LDO2 to LDO9 according to the
> schematic. Set the base voltage to 3.3V, there is only 3.3V on the
> module itself.
>
> Set the Core and CPU voltage to the specified voltages of 1.2V and
> 1.0V respectivly.
>
> LDO6 should deliver 2.85V. The attached peripherals were not in
> use so far.
Does this depend on patch 1/3 or 2/3, or can I apply it to the Tegra
tree which doesn't include those patches?
If this does depend on patch 1/3 or 2/3... this patch feels a bit big to
apply to the MFD tree. Perhaps patch 1/3 and 2/3 could be applied alone
to a topic branch in the MFD tree so I can merge that into the Tegra
tree in order to apply this?
next prev parent reply other threads:[~2013-12-05 17:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 22:18 [PATCH v4 0/3] regulator: tps6586x: add version detection and voltage tables Stefan Agner
2013-12-03 22:18 ` [PATCH v4 1/3] mfd: tps6586x: add version detection Stefan Agner
2013-12-04 8:10 ` Lee Jones
2013-12-04 8:40 ` Stefan Agner
2013-12-04 10:07 ` Lee Jones
2013-12-04 11:38 ` Stefan Agner
2013-12-04 11:48 ` Lee Jones
2013-12-04 11:49 ` Mark Brown
2013-12-04 11:58 ` Lee Jones
2013-12-05 17:06 ` Stephen Warren
2013-12-05 17:43 ` Stefan Agner
2013-12-05 17:40 ` Stephen Warren
2013-12-05 22:56 ` Stefan Agner
2013-12-06 8:44 ` Lee Jones
2013-12-03 22:18 ` [PATCH v4 2/3] regulator: tps6586x: add and use correct voltage table Stefan Agner
2013-12-04 9:48 ` Thierry Reding
2013-12-04 12:14 ` Mark Brown
2013-12-04 14:17 ` Stefan Agner
2013-12-04 14:29 ` Mark Brown
2013-12-04 14:40 ` Lee Jones
2013-12-05 17:10 ` Stephen Warren
2013-12-03 22:18 ` [PATCH v4 3/3] ARM: tegra: correct Colibri T20 regulator settings Stefan Agner
2013-12-04 11:52 ` Lucas Stach
2013-12-05 17:12 ` Stephen Warren [this message]
2013-12-05 17:33 ` Stefan Agner
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=52A0B40B.7040903@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=dev@lynxeye.de \
--cc=kai.poggensee@avionic-design.de \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=stefan@agner.ch \
--cc=thierry.reding@gmail.com \
/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