Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 0bc42d7f authored by David Howells's avatar David Howells
Browse files

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: default avatarDavid Howells <dhowells@redhat.com>
parent 86c0f935

arch/mn10300/Kconfig

+1 −28
Original line number Original line Diff line number Diff line
@@ -136,34 +136,7 @@ config FPU 
	default y

	default y

	depends on MN10300_PROC_MN103E010

	depends on MN10300_PROC_MN103E010





choice

source "arch/mn10300/mm/Kconfig.cache"

	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





menu "Memory layout options"

menu "Memory layout options"

arch/mn10300/mm/Kconfig.cache

0 → 100644
+32 −0
Original line number Original line Diff line number Diff line 
#

# 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