diff options
author | David Howells <dhowells@redhat.com> | 2010-10-27 18:28:41 +0200 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2010-10-27 18:28:41 +0200 |
commit | 0bc42d7fcb0acaab4202db97ff2de475424bf9b4 (patch) | |
tree | 4ca3bbe604cda0f578de150b90aa4032ad22943d /arch/mn10300/mm | |
parent | MN10300: Remove monitor/JTAG functions (diff) | |
download | linux-0bc42d7fcb0acaab4202db97ff2de475424bf9b4.tar.xz linux-0bc42d7fcb0acaab4202db97ff2de475424bf9b4.zip |
MN10300: Cache: Split cache bits out of arch Kconfig
Split the cache bits out of arch/mn10300/Kconfig as they're quite complex.
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'arch/mn10300/mm')
-rw-r--r-- | arch/mn10300/mm/Kconfig.cache | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/arch/mn10300/mm/Kconfig.cache b/arch/mn10300/mm/Kconfig.cache new file mode 100644 index 000000000000..f5599f47ec15 --- /dev/null +++ b/arch/mn10300/mm/Kconfig.cache @@ -0,0 +1,32 @@ +# +# MN10300 CPU cache options +# + +choice + prompt "CPU Caching mode" + default MN10300_CACHE_WBACK + help + This option determines the caching mode for the kernel. + + Write-Back caching mode involves the all reads and writes causing + the affected cacheline to be read into the cache first before being + operated upon. Memory is not then updated by a write until the cache + is filled and a cacheline needs to be displaced from the cache to + make room. Only at that point is it written back. + + Write-Through caching only fetches cachelines from memory on a + read. Writes always get written directly to memory. If the affected + cacheline is also in cache, it will be updated too. + + The final option is to turn of caching entirely. + +config MN10300_CACHE_WBACK + bool "Write-Back" + +config MN10300_CACHE_WTHRU + bool "Write-Through" + +config MN10300_CACHE_DISABLED + bool "Disabled" + +endchoice |