From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/3] spl: Add support for enabling dcache
Date: Mon, 28 Nov 2016 11:57:37 -0500 [thread overview]
Message-ID: <20161128165737.GK2546@bill-the-cat> (raw)
In-Reply-To: <20161128093445.15300-4-lokeshvutla@ti.com>
On Mon, Nov 28, 2016 at 03:04:45PM +0530, Lokesh Vutla wrote:
> Add support for enabling d-cache in SPL. The sequence in SPL tries to
> replicate the sequence done in U-Boot except that MMU entries were added
> for SRAM.
>
> 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: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161128/d61d7417/attachment.sig>
next prev parent reply other threads:[~2016-11-28 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 9:34 [U-Boot] [RFC PATCH 0/3] spl: Add D-cache support Lokesh Vutla
2016-11-28 9:34 ` [U-Boot] [RFC PATCH 1/3] arch: arm: omap: Declare size of ddr very early Lokesh Vutla
2016-11-28 16:56 ` Tom Rini
2016-11-28 9:34 ` [U-Boot] [RFC PATCH 2/3] spl: reorder the assignment of board info to global data Lokesh Vutla
2016-11-28 16:57 ` Tom Rini
2016-11-30 0:34 ` Simon Glass
2016-11-28 9:34 ` [U-Boot] [RFC PATCH 3/3] spl: Add support for enabling dcache Lokesh Vutla
2016-11-28 16:57 ` Tom Rini [this message]
2016-11-30 0:34 ` Simon Glass
2016-11-28 16:40 ` [U-Boot] [RFC PATCH 0/3] spl: Add D-cache support Tom Rini
2016-11-29 5:41 ` Lokesh Vutla
2016-12-12 9:52 ` Lokesh Vutla
2016-12-12 14:32 ` Tom Rini
2016-12-13 12:14 ` Tom Rini
2016-12-13 15:18 ` Lokesh Vutla
2016-12-13 15:26 ` 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=20161128165737.GK2546@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.