From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: tegra: define Jetson TK1 regulators
Date: Tue, 15 Apr 2014 14:47:51 -0600 [thread overview]
Message-ID: <534D9AF7.6030903@wwwdotorg.org> (raw)
In-Reply-To: <1397516120-18220-1-git-send-email-swarren@wwwdotorg.org>
On 04/14/2014 04:55 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia•com>
>
> These are mostly identical to the Venice2 regulator definitions, since
> the board designs are very similar. Differences are:
>
> - Jetson TK1 doesn't have a built-in LCD panel, so on-board regulators
> are not present for the backlight, touchscreen, or panel.
> - +3.3V_RUN needs to be boot-on/always-on, since it's widely used. This
> change should likely be propagated to Venice2 for completeness,
> although it will have no practical effect there since various other
> regulators use +3.3V_RUN as their supply and are always-on.
> - +3.3V_LP0 needs to be boot-on as well as always-on. One reason
> is because it's used to driver the UART level-shifter; without this, I
> see a brief period of UART corruption during cold boots.I suspect this
> change needs to be propagated to Venice2, and we simply haven't noticed
> the need since there's no UART level-shifter on Venice2.
> - A few rails have different names in the schematics.
I have applied this to Tegra's for-3.16/dt branch.
next prev parent reply other threads:[~2014-04-15 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 22:55 [PATCH] ARM: tegra: define Jetson TK1 regulators Stephen Warren
2014-04-15 20:47 ` Stephen Warren [this message]
2014-04-16 0:24 ` Andrew Bresticker
2014-04-16 8:18 ` Peter De Schrijver
2014-04-16 16:33 ` Stephen Warren
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=534D9AF7.6030903@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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