From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] arm: cache: always flush cache line size for page table
Date: Sun, 07 Aug 2016 10:34:00 -0700 [thread overview]
Message-ID: <092cad150ec7aa05aaa322df57bb5e73@agner.ch> (raw)
In-Reply-To: <01e2a6d2-ce85-e7c9-2deb-cc8efb264dda@suse.de>
On 2016-08-07 10:29, Andreas F?rber wrote:
> Am 07.08.2016 um 19:17 schrieb Stefan Agner:
>> From: Stefan Agner <stefan.agner@toradex.com>
>>
>> The page table is maintained by the CPU, hence it is safe to always
>> align cache flush to a whole cache line size. This allows to use
>> mmu_page_table_flush for a single page table, e.g. when configure
>> only small regions through mmu_set_region_dcache_behaviour.
>>
>> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
>> Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
>> Reviewed-by: Simon Glass <sjg@chromium.org>
>> ---
>> Changes since v2:
>> - Fixed spelling misstake
>> Changes since v1:
>> - Move cache line alignment from mmu_page_table_flush to
>> mmu_set_region_dcache_behaviour
>>
>> arch/arm/lib/cache-cp15.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/lib/cache-cp15.c b/arch/arm/lib/cache-cp15.c
>> index 1121dc3..bf79edd 100644
>> --- a/arch/arm/lib/cache-cp15.c
>> +++ b/arch/arm/lib/cache-cp15.c
>> @@ -62,6 +62,7 @@ void mmu_set_region_dcache_behaviour(phys_addr_t start, size_t size,
>> enum dcache_option option)
>> {
>> u32 *page_table = (u32 *)gd->arch.tlb_addr;
>> + phys_addr_t startpt, stoppt;
>> unsigned long upto, end;
>>
>> end = ALIGN(start + size, MMU_SECTION_SIZE) >> MMU_SECTION_SHIFT;
>> @@ -70,7 +71,17 @@ void mmu_set_region_dcache_behaviour(phys_addr_t start, size_t size,
>> option);
>> for (upto = start; upto < end; upto++)
>> set_section_dcache(upto, option);
>> - mmu_page_table_flush((u32)&page_table[start], (u32)&page_table[end]);
>> +
>> + /*
>> + * Make sure range is cache line aligned
>> + * Only CPU maintains page tables, hence it is save to always
>
> "safe"
>
Ugh, I thought I just fixed that spelling misstake. I think I need
another coffee.
--
Stefan
>> + * flush complete cache lines...
>> + */
>> + startpt = (phys_addr_t)&page_table[start];
>> + startpt &= ~(CONFIG_SYS_CACHELINE_SIZE - 1);
>> + stoppt = (phys_addr_t)&page_table[end];
>> + stoppt = ALIGN(stoppt, CONFIG_SYS_CACHELINE_SIZE);
>> + mmu_page_table_flush(startpt, stoppt);
>> }
>>
>> __weak void dram_bank_mmu_setup(int bank)
>
> Regards,
> Andreas
prev parent reply other threads:[~2016-08-07 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 17:17 [U-Boot] [PATCH v3] arm: cache: always flush cache line size for page table Stefan Agner
2016-08-07 17:29 ` Andreas Färber
2016-08-07 17:34 ` Stefan Agner [this message]
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=092cad150ec7aa05aaa322df57bb5e73@agner.ch \
--to=stefan@agner.ch \
--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