From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] efi_loader: Always flush in cache line size granularity
Date: Mon, 11 Apr 2016 00:31:14 +0200 [thread overview]
Message-ID: <570AD432.9090404@suse.de> (raw)
In-Reply-To: <570AD2BA.609@suse.de>
On 11.04.16 00:24, Andreas F?rber wrote:
> Am 04.04.2016 um 09:32 schrieb Alexander Graf:
>> The cache line flush helpers only work properly when they get aligned
>> start and end addresses. Round our flush range to cache line size. It's
>> safe because we're guaranteed to flush within a single page which has the
>> same cache attributes.
>>
>> Reported-by: Marek Vasut <marex@denx.de>
>> Signed-off-by: Alexander Graf <agraf@suse.de>
>> ---
>> lib/efi_loader/efi_runtime.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/efi_loader/efi_runtime.c b/lib/efi_loader/efi_runtime.c
>> index 22bcd08..40acec0 100644
>> --- a/lib/efi_loader/efi_runtime.c
>> +++ b/lib/efi_loader/efi_runtime.c
>> @@ -194,7 +194,8 @@ void efi_runtime_relocate(ulong offset, struct efi_mem_desc *map)
>> #endif
>>
>> *p = newaddr;
>> - flush_dcache_range((ulong)p, (ulong)&p[1]);
>> + flush_dcache_range((ulong)p & ~(CONFIG_SYS_CACHELINE_SIZE - 1),
>> + ALIGN((ulong)&p[1], CONFIG_SYS_CACHELINE_SIZE));
>
> dragonboard410c_defconfig fails to build with this due to undefined
> CONFIG_SYS_CACHELINE_SIZE. Do we need to #ifdef here or is the
> dragonboard410c at fault for not defining it?
Some USB drivers use it unconditionally, but I guess the dragonboard401c
doesn't enable USB.
Let me come up with a more compatible version.
Alex
next prev parent reply other threads:[~2016-04-10 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 7:32 [U-Boot] [PATCH] efi_loader: Always flush in cache line size granularity Alexander Graf
2016-04-04 7:56 ` Marek Vasut
2016-04-10 22:24 ` Andreas Färber
2016-04-10 22:31 ` Alexander Graf [this message]
2016-04-10 22:36 ` Marek Vasut
2016-04-12 0:39 ` Tom Rini
2016-04-12 0:59 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2016-04-11 21:20 Alexander Graf
2016-04-13 12:53 ` Andreas Färber
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=570AD432.9090404@suse.de \
--to=agraf@suse.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