From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] am33xx: Enable D-CACHE on !CONFIG_SYS_DCACHE_OFF
Date: Mon, 2 Sep 2013 09:22:34 +0530 [thread overview]
Message-ID: <52240B82.9090001@ti.com> (raw)
In-Reply-To: <20130830211358.GW17898@bill-the-cat>
Hi Tom,
On Saturday 31 August 2013 02:43 AM, Tom Rini wrote:
> On Fri, Aug 30, 2013 at 05:07:17PM -0400, Tom Rini wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/30/2013 12:50 AM, Sricharan R wrote:
>>> Hi Tom,
>>>
>>> On Friday 23 August 2013 09:56 PM, Tom Rini wrote:
>>>> Test on Beaglebone white over cpsw, usb ether and SD card (read and
>>>> write), performance increased, crc32 of data matches.
>>>>
>>>> Signed-off-by: Tom Rini <trini@ti.com>
>>>> ---
>>>> arch/arm/cpu/armv7/am33xx/board.c | 8 ++++++++
>>>> 1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/arch/arm/cpu/armv7/am33xx/board.c b/arch/arm/cpu/armv7/am33xx/board.c
>>>> index 2ea3d69..c261af5 100644
>>>> --- a/arch/arm/cpu/armv7/am33xx/board.c
>>>> +++ b/arch/arm/cpu/armv7/am33xx/board.c
>>>> @@ -225,3 +225,11 @@ void s_init(void)
>>>> sdram_init();
>>>> #endif
>>>> }
>>>> +
>>>> +#ifndef CONFIG_SYS_DCACHE_OFF
>>>> +void enable_caches(void)
>>>> +{
>>>> + /* Enable D-cache. I-cache is already enabled in start.S */
>>>> + dcache_enable();
>>>> +}
>>>> +#endif /* !CONFIG_SYS_DCACHE_OFF */
>>> This is fine. Do we have secure devices here ?
>>>
>>> If so, we should take care of setting the domains permissions for
>>> avoiding prefetch aborts. As it was done for OMAP using
>>> arm_init_domains. So that function and the above should be executed on
>>> am33xx as well.
>>>
>>> Thanks to Lokesh for reminding this.
>>
>> Yes, but I can't easily test them. I'll see if arm_init_domains just
>> works on non-HS devices (I know I had a failure pulling all the OMAP4
>> code over, but didn't try hard, just looked again at the "easy" path).
>
> Yeah, that code as-is hangs the boards. So if the HS devices need
> something, it'll go with the rest of their patches until we're moving it
> upstream. But good to note a potential problem area!
I added the following diff and I am able to boot my BBB over cpsw.
diff --git a/arch/arm/cpu/armv7/am33xx/board.c b/arch/arm/cpu/armv7/am33xx/board.c
index 2ea3d69..8a1a29a 100644
--- a/arch/arm/cpu/armv7/am33xx/board.c
+++ b/arch/arm/cpu/armv7/am33xx/board.c
@@ -31,6 +31,11 @@
#include <linux/usb/gadget.h>
#include <linux/usb/musb.h>
#include <asm/omap_musb.h>
+#include <asm/cache.h>
+
+#define ARMV7_DCACHE_WRITEBACK 0xe
+#define ARMV7_DOMAIN_CLIENT 1
+#define ARMV7_DOMAIN_MASK (0x3 << 0)
DECLARE_GLOBAL_DATA_PTR;
@@ -225,3 +230,40 @@ void s_init(void)
sdram_init();
#endif
}
+
+#ifndef CONFIG_SYS_DCACHE_OFF
+void enable_caches(void)
+{
+ /* Enable D-cache. I-cache is already enabled in start.S */
+ dcache_enable();
+}
+
+void dram_bank_mmu_setup(int bank)
+{
+ bd_t *bd = gd->bd;
+ int i;
+
+ u32 start = bd->bi_dram[bank].start >> 20;
+ u32 size = bd->bi_dram[bank].size >> 20;
+ u32 end = start + size;
+
+ debug("%s: bank: %d\n", __func__, bank);
+ for (i = start; i < end; i++)
+ set_section_dcache(i, ARMV7_DCACHE_WRITEBACK);
+
+}
+
+void arm_init_domains(void)
+{
+ u32 reg;
+
+ reg = get_dacr();
+ /*
+ * Set DOMAIN to client access so that all permissions
+ * set in pagetables are validated by the mmu.
+ */
+ reg &= ~ARMV7_DOMAIN_MASK;
+ reg |= ARMV7_DOMAIN_CLIENT;
+ set_dacr(reg);
+}
+#endif
AM I missing something here ?
Thanks and regards,
Lokesh
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2013-09-02 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 16:26 [U-Boot] [PATCH] am33xx: Enable D-CACHE on !CONFIG_SYS_DCACHE_OFF Tom Rini
2013-08-30 4:50 ` Sricharan R
2013-08-30 21:07 ` Tom Rini
2013-08-30 21:13 ` Tom Rini
2013-09-02 3:52 ` Lokesh Vutla [this message]
2013-09-06 18:01 ` Tom Rini
2013-12-13 12:46 ` [U-Boot] " 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=52240B82.9090001@ti.com \
--to=lokeshvutla@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