From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] ARM: DRA7: emif: Enable interleaving for higher address space
Date: Mon, 7 Mar 2016 18:36:01 -0500 [thread overview]
Message-ID: <20160307233601.GS23166@bill-the-cat> (raw)
In-Reply-To: <1457179351-971-5-git-send-email-lokeshvutla@ti.com>
On Sat, Mar 05, 2016 at 05:32:31PM +0530, Lokesh Vutla wrote:
> Given that DRA7/OMAP5 SoCs can support more than 2GB of memory,
> enable interleaving for this higher memory to increase performance.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.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/20160307/691c4333/attachment.sig>
next prev parent reply other threads:[~2016-03-07 23:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 12:02 [U-Boot] [PATCH 0/4] ARM: DRA7: emif: Miscellaneous bug fixes Lokesh Vutla
2016-03-05 12:02 ` [U-Boot] [PATCH 1/4] ARM: DRA7: emif: Fix updating of refresh ctrl shadow Lokesh Vutla
2016-03-07 23:35 ` Tom Rini
2016-03-15 11:59 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-05 12:02 ` [U-Boot] [PATCH 2/4] ARM: DRA7: emif: Fix DDR init sequence during warm reset Lokesh Vutla
2016-03-07 23:35 ` Tom Rini
2016-03-15 11:59 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-05 12:02 ` [U-Boot] [PATCH 3/4] ARM: DRA7: emif: Check for enable bits before updating leveling output Lokesh Vutla
2016-03-07 23:35 ` Tom Rini
2016-03-15 11:59 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-05 12:02 ` [U-Boot] [PATCH 4/4] ARM: DRA7: emif: Enable interleaving for higher address space Lokesh Vutla
2016-03-07 23:36 ` Tom Rini [this message]
2016-03-15 11:59 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-07 23:36 ` [U-Boot] [PATCH 0/4] ARM: DRA7: emif: Miscellaneous bug fixes Tom Rini
2016-03-08 3:37 ` Lokesh Vutla
2016-03-08 11:58 ` 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=20160307233601.GS23166@bill-the-cat \
--to=trini@konsulko.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