From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX5/6 U-Boot: Cache enabling
Date: Thu, 9 Feb 2012 08:06:51 +0100 [thread overview]
Message-ID: <201202090806.51520.marek.vasut@gmail.com> (raw)
In-Reply-To: <4F327A9B.6010005@de.bosch.com>
> On 04.02.2012 11:18, Marek Vasut wrote:
> >> Let's discuss how to enable the i.MX5/6 caches in U-Boot:
> >>
> >> On 03.02.2012 12:00, Stefano Babic wrote:
> >>> On 03/02/2012 11:18, Dirk Behme wrote:
> >> ...
> >>
> >>>>> As your concerns are surely related to speed up the boot process,
> >>>>> IMHO we can focus efforts to add cache support for MX5 / MX6.
> >>>>
> >>>> Ok, sounds good. Any idea what has to be done for this? Or what would
> >>>> be the steps for this?
> >>>
> >>> As armv7 architecture, the MX can profit of the work already done for
> >>> other SOCs. Functions for enabling / disabling / invalidate caches are
> >>> already provided, in arch/arm/lib and arch/arm/cpu/armv7/cache_v7.c. So
> >>> at least for MX5/MX6.
> >>>
> >>> But we should change MXC drivers to be cache-aware. At least the FEC
> >>> driver and MMC driver are known to not work when dcache is on.
> >>
> >> Marek, Troy, Fabio: What do you think is needed to make the i.MX5/6
> >> FEC driver cache-aware?
> >
> > I already have a partly finished implementation of FEC ethernet with
> > cache support somewhere on my drive.
>
> Do you like to share this?
>
> Many thanks and best regards
Try the attached stuff, it's likely crap and needs rebasing. It might give you
some pointers as of how to handle this.
>
> Dirk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0045-FEC-Fix-to-work-with-data-cache-enabled.patch
Type: text/x-patch
Size: 14678 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120209/55443b2f/attachment.bin>
next prev parent reply other threads:[~2012-02-09 7:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 7:25 [U-Boot] Skipping relocation RAM to RAM, esp. on i.MX6? Dirk Behme
2012-02-03 8:51 ` Stefano Babic
2012-02-03 10:18 ` Dirk Behme
2012-02-03 11:00 ` Stefano Babic
2012-02-03 11:19 ` Mike Frysinger
2012-02-04 8:38 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling (was: Re: Skipping relocation RAM to RAM, esp. on i.MX6?) Dirk Behme
2012-02-04 9:18 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling Aneesh V
2012-02-04 10:18 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling (was: Re: Skipping relocation RAM to RAM, esp. on i.MX6?) Marek Vasut
2012-02-08 13:37 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling Dirk Behme
2012-02-09 7:06 ` Marek Vasut [this message]
2012-02-04 9:15 ` [U-Boot] Skipping relocation RAM to RAM, esp. on i.MX6? Aneesh V
2012-02-04 11:00 ` Albert ARIBAUD
2012-02-04 11:14 ` Aneesh V
2012-02-04 11:37 ` Albert ARIBAUD
2012-02-06 14:34 ` Tom Rini
2012-02-06 21:21 ` Albert ARIBAUD
2012-02-06 22:27 ` Wolfgang Denk
2012-02-06 22:41 ` Graeme Russ
2012-02-07 7:19 ` Aneesh V
2012-02-07 23:26 ` Wolfgang Denk
2012-02-08 6:43 ` Aneesh V
2012-02-08 13:58 ` Wolfgang Denk
2012-02-08 14:48 ` Aneesh V
2012-02-08 16:23 ` Wolfgang Denk
2012-02-09 6:01 ` Aneesh V
2012-02-09 11:44 ` Wolfgang Denk
2012-02-09 13:43 ` Aneesh V
2012-02-05 6:19 ` Simon Glass
2012-02-06 14:19 ` Aneesh V
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=201202090806.51520.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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