From: Tony Lindgren <tony@atomide.com>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
Nishanth Menon <nm@ti.com>,
bcousson@baylibre.com, Sekhar Nori <nsekhar@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH] ARM: dts: am437x-gp-evm: Boot fixes
Date: Tue, 22 Apr 2014 12:01:32 -0700 [thread overview]
Message-ID: <20140422190132.GA12204@atomide.com> (raw)
In-Reply-To: <1398192739-8901-1-git-send-email-d-gerlach@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [140422 11:52]:
> This patch, along with patch here [1], fixes boot for am437x-gp-evm. The
> bootloader configures gpio5_7 to control the DDR3 termination regulator,
> the linked patch prevents that gpio bank from being reset and losing
> the previously configured state, and this patch binds the gpio to a
> regulator so the kernel is aware of the state of the gpio.
>
> [1] https://www.mail-archive.com/linux-omap@vger.kernel.org/msg102941.html
Setting up the GPIO regulator makes sense to me. But the hack in the
link above is potentially a nasty time bomb for anybody trying to
use GPIO bank 5 on that board.
What tests have been done that the GPIO bank behaves properly when
it's not reset?
Regards,
Tony
next prev parent reply other threads:[~2014-04-22 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 18:52 [PATCH] ARM: dts: am437x-gp-evm: Boot fixes Dave Gerlach
2014-04-22 18:52 ` [PATCH] ARM: dts: am437x-gp-evm: Add vtt_fixed regulator Dave Gerlach
2014-04-22 18:58 ` Nishanth Menon
2014-04-22 19:53 ` Dave Gerlach
2014-04-22 19:01 ` Tony Lindgren [this message]
2014-04-22 19:53 ` [PATCH] ARM: dts: am437x-gp-evm: Boot fixes Dave Gerlach
2014-04-23 14:59 ` Tony Lindgren
2014-04-23 17:25 ` Dave Gerlach
2014-04-25 16:41 ` Tony Lindgren
2014-04-29 14:47 ` Dave Gerlach
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=20140422190132.GA12204@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=rnayak@ti.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;
as well as URLs for NNTP newsgroup(s).