From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unaligned flush_dcache_range in axs101.c
Date: Mon, 11 Apr 2016 19:54:32 +0200 [thread overview]
Message-ID: <570BE4D8.9050303@denx.de> (raw)
In-Reply-To: <1460396935.5119.57.camel@synopsys.com>
On 04/11/2016 07:48 PM, Alexey Brodkin wrote:
> Hi Alex,
>
> On Mon, 2016-04-04 at 09:38 +0200, Alexander Graf wrote:
>> Hi Alexey,
>>
>> Marek just pointed out to me the fact that flush_dcache_range on arm
>> expects cache line aligned arguments. However, it seems like in axs101.c
>> we have an unaligned cache flush:
>>
>> flush_dcache_range(RESET_VECTOR_ADDR, RESET_VECTOR_ADDR + sizeof(int));
>>
>> Could you please verify whether this is correct and if not just send a
>> quick patch to fix it?
>
> First this code is for support of Synopsys DesignWare AXS10x boards.
> And AFAIK there's no such board that may sport ARM CPU instead or ARC.
> So I'm wondering how did you bumped into that [issue?]?
>
> Then I'm not really sure if there's a common requirement for arguments of
> flush_dcache_range(). At least in "include/common.h" there's no comment about
> that.
Such comment should then be added. Sub-cacheline flush/invalidate calls
can corrupt surrounding data.
> Personally I'd say this is up to each arch or SoC to implement flush_dcache_range()
> so it works properly on that particular hardware. I wouldn't like to
> overcomplicate high-level stuff with low-level details such as cache lines etc
> if that is not really necessary.
>
> Please correct me if I'm missing something here.
>
> -Alexey
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-11 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 7:38 [U-Boot] Unaligned flush_dcache_range in axs101.c Alexander Graf
2016-04-11 17:48 ` Alexey Brodkin
2016-04-11 17:54 ` Marek Vasut [this message]
2016-04-11 18:13 ` Alexey Brodkin
2016-04-11 18:48 ` Marek Vasut
2016-04-15 13:00 ` Alexey Brodkin
2016-04-15 13:49 ` Marek Vasut
2016-05-26 11:39 ` Alexey Brodkin
2016-05-26 12:07 ` Vineet Gupta
2016-05-27 13:21 ` Marek Vasut
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=570BE4D8.9050303@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