From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] nios2: convert cache flush to use dm cpu data
Date: Sat, 17 Oct 2015 01:00:05 +0200 [thread overview]
Message-ID: <201510170100.05843.marex@denx.de> (raw)
In-Reply-To: <1444786719-31736-1-git-send-email-thomas@wytron.com.tw>
On Wednesday, October 14, 2015 at 03:38:39 AM, Thomas Chou wrote:
> Convert cache flush to use dm cpu data.
>
> The original cache flush functions are written in assembly
> and use CONFIG_SYS_{I,D}CACHE_SIZE... macros. It is difficult
> to convert to use cache configuration in dm cpu data which is
> extracted from device tree.
>
> The cacheflush.c of Linux nios2 arch uses cpuinfo structure,
> which is very close to our dm cpu data. So we copy and modify
> it to arch/nios2/lib/cache.c to replace the old cache.S.
>
> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
Hi!
[...]
> +static void __flush_dcache(unsigned long start, unsigned long end)
> +{
> + unsigned long addr;
> +
> + start &= ~(gd->arch.dcache_line_size - 1);
> + end += (gd->arch.dcache_line_size - 1);
> + end &= ~(gd->arch.dcache_line_size - 1);
I really don't think we should do this alignment here :-(
> + for (addr = start; addr < end; addr += gd->arch.dcache_line_size) {
> + __asm__ __volatile__ (" flushda 0(%0)\n"
> + : /* Outputs */
> + : /* Inputs */ "r"(addr)
> + /* : No clobber */);
> + }
> +}
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-10-16 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444119600-31999-1-git-send-email-thomas@wytron.com.t>
2015-10-14 1:38 ` [U-Boot] [PATCH v3] nios2: convert cache flush to use dm cpu data Thomas Chou
2015-10-16 23:00 ` Marek Vasut [this message]
2015-10-17 6:54 ` Thomas Chou
2015-10-17 11:52 ` Marek Vasut
2015-10-18 23:48 ` Thomas Chou
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=201510170100.05843.marex@denx.de \
--to=marex@denx.de \
--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