From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH 0/2] Add VTT regulators for DDR3 AMx3xx Boards
Date: Tue, 6 May 2014 09:50:55 -0700 [thread overview]
Message-ID: <20140506165055.GM18474@atomide.com> (raw)
In-Reply-To: <1399319909-53795-1-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
* Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org> [140505 12:59]:
> The am335x-evmsk and am437x-gp-evm both have a gpio controlled regulator
> for DDR3 VTT voltage. This is configured by boot loader and previously
> just left at that but it is better to define a fixed regulator to control
> the gpio so that the kernel is aware of it.
>
> Previous discussion here [1].
>
> Original am437x-gp-evm patch has been updated to reflect actual voltage
> supplied by VTT regulator.
Thanks applying both into omap-for-v3.16/dt.
Tony
--
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
prev parent reply other threads:[~2014-05-06 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 19:58 [PATCH 0/2] Add VTT regulators for DDR3 AMx3xx Boards Dave Gerlach
[not found] ` <1399319909-53795-1-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2014-05-05 19:58 ` [PATCH 1/2] ARM: dts: am437x-gp-evm: Add vtt_fixed regulator Dave Gerlach
2014-05-05 19:58 ` [PATCH 2/2] ARM: dts: am335x-evmsk: " Dave Gerlach
2014-05-06 16:50 ` Tony Lindgren [this message]
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=20140506165055.GM18474@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=d-gerlach-l0cyMroinI0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@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).