mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-25 13:43:55 +08:00
f12d0d7c77
All the current CP15 access codes in ARM arch can be categorized and
conditioned by the defines as follows:
Related operation Safe condition
a. any CP15 access !CPU_CP15
b. alignment trap CPU_CP15_MMU
c. D-cache(C-bit) CPU_CP15
d. I-cache CPU_CP15 && !( CPU_ARM610 || CPU_ARM710 ||
CPU_ARM720 || CPU_ARM740 ||
CPU_XSCALE || CPU_XSC3 )
e. alternate vector CPU_CP15 && !CPU_ARM740
f. TTB CPU_CP15_MMU
g. Domain CPU_CP15_MMU
h. FSR/FAR CPU_CP15_MMU
For example, alternate vector is supported if and only if
"CPU_CP15 && !CPU_ARM740" is satisfied.
Signed-off-by: Hyok S. Choi <hyok.choi@samsung.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
53 lines
1.5 KiB
Plaintext
53 lines
1.5 KiB
Plaintext
#
|
|
# Kconfig for uClinux(non-paged MM) depend configurations
|
|
# Hyok S. Choi <hyok.choi@samsung.com>
|
|
#
|
|
|
|
config SET_MEM_PARAM
|
|
bool "Set flash/sdram size and base addr"
|
|
help
|
|
Say Y to manually set the base addresses and sizes.
|
|
otherwise, the default values are assigned.
|
|
|
|
config DRAM_BASE
|
|
hex '(S)DRAM Base Address' if SET_MEM_PARAM
|
|
default 0x00800000
|
|
|
|
config DRAM_SIZE
|
|
hex '(S)DRAM SIZE' if SET_MEM_PARAM
|
|
default 0x00800000
|
|
|
|
config FLASH_MEM_BASE
|
|
hex 'FLASH Base Address' if SET_MEM_PARAM
|
|
default 0x00400000
|
|
|
|
config FLASH_SIZE
|
|
hex 'FLASH Size' if SET_MEM_PARAM
|
|
default 0x00400000
|
|
|
|
config PROCESSOR_ID
|
|
hex
|
|
default 0x00007700
|
|
depends on !CPU_CP15
|
|
help
|
|
If processor has no CP15 register, this processor ID is
|
|
used instead of the auto-probing which utilizes the register.
|
|
|
|
config REMAP_VECTORS_TO_RAM
|
|
bool 'Install vectors to the begining of RAM' if DRAM_BASE
|
|
depends on DRAM_BASE
|
|
help
|
|
The kernel needs to change the hardware exception vectors.
|
|
In nommu mode, the hardware exception vectors are normally
|
|
placed at address 0x00000000. However, this region may be
|
|
occupied by read-only memory depending on H/W design.
|
|
|
|
If the region contains read-write memory, say 'n' here.
|
|
|
|
If your CPU provides a remap facility which allows the exception
|
|
vectors to be mapped to writable memory, say 'n' here.
|
|
|
|
Otherwise, say 'y' here. In this case, the kernel will require
|
|
external support to redirect the hardware exception vectors to
|
|
the writable versions located at DRAM_BASE.
|