RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

bsps/cache: Clarify range functions support

Browse Source
This commit is contained in:
Sebastian Huber
2015-04-27 09:40:16 +02:00
parent 1602bf3973
commit 4bf2a6aa09
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
c/src/lib/libcpu/shared/include/cache.h
View File

@@ -21,9 +21,7 @@
#ifndef __LIBCPU_CACHE_h
#define __LIBCPU_CACHE_h
void _CPU_cache_flush_data_range(const void *d_addr, size_t n_bytes);
void _CPU_cache_flush_1_data_line(const void *d_addr);
void _CPU_cache_invalidate_data_range(const void *d_addr, size_t n_bytes);
void _CPU_cache_invalidate_1_data_line(const void *d_addr);
void _CPU_cache_freeze_data(void);
void _CPU_cache_unfreeze_data(void);

8
c/src/lib/libcpu/shared/src/cache_manager.c
View File

@@ -20,9 +20,13 @@
* rtems/c/src/lib/libcpu/CPU/cache_.h
*
* The cache implementation header file can define
* CPU_CACHE_SUPPORT_PROVIDES_RANGE_FUNCTIONS
*
* #define CPU_CACHE_SUPPORT_PROVIDES_RANGE_FUNCTIONS
*
* if it provides cache maintenance functions which operate on multiple lines.
* Otherwise a generic loop with single line operations will be used.
* Otherwise a generic loop with single line operations will be used. It is
* strongly recommended to provide the implementation in terms of static
* inline functions for performance reasons.
*
* The functions below are implemented with CPU dependent inline routines
* found in the cache.c files for each CPU. In the event that a CPU does