From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/3] twl4030: device-index-specific MMC power initializations, common ramp-up delay
Date: Mon, 10 Nov 2014 13:46:32 -0500 [thread overview]
Message-ID: <20141110184632.GA24724@bill-the-cat> (raw)
In-Reply-To: <1415476547-17896-3-git-send-email-contact@paulk.fr>
On Sat, Nov 08, 2014 at 08:55:46PM +0100, Paul Kocialkowski wrote:
> Not every device has multiple MMC slots available, so it makes sense to enable
> only the required LDOs for the available slots. Generic code in omap_hsmmc will
> enable both VMMC1 and VMMC2, in doubt.
>
> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
Reviewed-by: Tom Rini <trini@ti.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141110/2dd13d93/attachment.pgp>
next prev parent reply other threads:[~2014-11-10 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 19:55 [U-Boot] [PATCH v4 0/3] mmc: Board-specific MMC power initializations Paul Kocialkowski
2014-11-08 19:55 ` [U-Boot] [PATCH v4 1/3] " Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini
2014-12-05 14:52 ` [U-Boot] [U-Boot, v4, " Tom Rini
2014-11-08 19:55 ` [U-Boot] [PATCH v4 2/3] twl4030: device-index-specific MMC power initializations, common ramp-up delay Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini [this message]
2014-12-05 14:52 ` [U-Boot] [U-Boot, v4, " Tom Rini
2014-11-08 19:55 ` [U-Boot] [PATCH v4 3/3] omap_hsmmc: Board-specific TWL4030 MMC power initializations Paul Kocialkowski
2014-11-08 21:29 ` Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini
2014-11-11 11:57 ` Paul Kocialkowski
2014-11-11 12:33 ` Tom Rini
2014-11-11 13:13 ` Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini
2014-12-05 14:52 ` [U-Boot] [U-Boot, v4, " Tom Rini
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=20141110184632.GA24724@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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