arch/frv/Kconfig

   1 config FRV
   2         bool
   3         default y
   4         select HAVE_IDE
   5         select HAVE_ARCH_TRACEHOOK
   6         select HAVE_IRQ_WORK
   7         select HAVE_PERF_EVENTS
   8         select HAVE_UID16
   9         select HAVE_GENERIC_HARDIRQS
  10         select GENERIC_IRQ_SHOW
  11         select HAVE_DEBUG_BUGVERBOSE
  12         select ARCH_HAVE_NMI_SAFE_CMPXCHG
  13         select GENERIC_CPU_DEVICES
  14         select ARCH_WANT_IPC_PARSE_VERSION
  15
  16 config ZONE_DMA
  17         bool
  18         default y
  19
  20 config RWSEM_GENERIC_SPINLOCK
  21         bool
  22         default y
  23
  24 config RWSEM_XCHGADD_ALGORITHM
  25         bool
  26
  27 config GENERIC_HWEIGHT
  28         bool
  29         default y
  30
  31 config GENERIC_CALIBRATE_DELAY
  32         bool
  33         default n
  34
  35 config TIME_LOW_RES
  36         bool
  37         default y
  38
  39 config QUICKLIST
  40         bool
  41         default y
  42
  43 config ARCH_HAS_ILOG2_U32
  44         bool
  45         default y
  46
  47 config ARCH_HAS_ILOG2_U64
  48         bool
  49         default y
  50
  51 config HZ
  52         int
  53         default 1000
  54
  55 source "init/Kconfig"
  56
  57 source "kernel/Kconfig.freezer"
  58
  59
  60 menu "Fujitsu FR-V system setup"
  61
  62 config MMU
  63         bool "MMU support"
  64         help
  65           This options switches on and off support for the FR-V MMU
  66           (effectively switching between vmlinux and uClinux). Not all FR-V
  67           CPUs support this. Currently only the FR451 has a sufficiently
  68           featured MMU.
  69
  70 config FRV_OUTOFLINE_ATOMIC_OPS
  71         bool "Out-of-line the FRV atomic operations"
  72         default n
  73         help
  74           Setting this option causes the FR-V atomic operations to be mostly
  75           implemented out-of-line.
  76
  77           See Documentation/frv/atomic-ops.txt for more information.
  78
  79 config HIGHMEM
  80         bool "High memory support"
  81         depends on MMU
  82         default y
  83         help
  84           If you wish to use more than 256MB of memory with your MMU based
  85           system, you will need to select this option. The kernel can only see
  86           the memory between 0xC0000000 and 0xD0000000 directly... everything
  87           else must be kmapped.
  88
  89           The arch is, however, capable of supporting up to 3GB of SDRAM.
  90
  91 config HIGHPTE
  92         bool "Allocate page tables in highmem"
  93         depends on HIGHMEM
  94         default y
  95         help
  96           The VM uses one page of memory for each page table.  For systems
  97           with a lot of RAM, this can be wasteful of precious low memory.
  98           Setting this option will put user-space page tables in high memory.
  99
 100 source "mm/Kconfig"
 101
 102 choice
 103         prompt "uClinux kernel load address"
 104         depends on !MMU
 105         default UCPAGE_OFFSET_C0000000
 106         help
 107           This option sets the base address for the uClinux kernel. The kernel
 108           will rearrange the SDRAM layout to start at this address, and move
 109           itself to start there. It must be greater than 0, and it must be
 110           sufficiently less than 0xE0000000 that the SDRAM does not intersect
 111           the I/O region.
 112
 113           The base address must also be aligned such that the SDRAM controller
 114           can decode it. For instance, a 512MB SDRAM bank must be 512MB aligned.
 115
 116 config UCPAGE_OFFSET_20000000
 117        bool "0x20000000"
 118
 119 config UCPAGE_OFFSET_40000000
 120        bool "0x40000000"
 121
 122 config UCPAGE_OFFSET_60000000
 123        bool "0x60000000"
 124
 125 config UCPAGE_OFFSET_80000000
 126        bool "0x80000000"
 127
 128 config UCPAGE_OFFSET_A0000000
 129        bool "0xA0000000"
 130
 131 config UCPAGE_OFFSET_C0000000
 132        bool "0xC0000000 (Recommended)"
 133
 134 endchoice
 135
 136 config PAGE_OFFSET
 137         hex
 138         default 0x20000000 if UCPAGE_OFFSET_20000000
 139         default 0x40000000 if UCPAGE_OFFSET_40000000
 140         default 0x60000000 if UCPAGE_OFFSET_60000000
 141         default 0x80000000 if UCPAGE_OFFSET_80000000
 142         default 0xA0000000 if UCPAGE_OFFSET_A0000000
 143         default 0xC0000000
 144
 145 config PROTECT_KERNEL
 146         bool "Protect core kernel against userspace"
 147         depends on !MMU
 148         default y
 149         help
 150           Selecting this option causes the uClinux kernel to change the
 151           permittivity of DAMPR register covering the core kernel image to
 152           prevent userspace accessing the underlying memory directly.
 153
 154 choice
 155         prompt "CPU Caching mode"
 156         default FRV_DEFL_CACHE_WBACK
 157         help
 158           This option determines the default caching mode for the kernel.
 159
 160           Write-Back caching mode involves the all reads and writes causing
 161           the affected cacheline to be read into the cache first before being
 162           operated upon. Memory is not then updated by a write until the cache
 163           is filled and a cacheline needs to be displaced from the cache to
 164           make room. Only at that point is it written back.
 165
 166           Write-Behind caching is similar to Write-Back caching, except that a
 167           write won't fetch a cacheline into the cache if there isn't already
 168           one there; it will write directly to memory instead.
 169
 170           Write-Through caching only fetches cachelines from memory on a
 171           read. Writes always get written directly to memory. If the affected
 172           cacheline is also in cache, it will be updated too.
 173
 174           The final option is to turn of caching entirely.
 175
 176           Note that not all CPUs support Write-Behind caching. If the CPU on
 177           which the kernel is running doesn't, it'll fall back to Write-Back
 178           caching.
 179
 180 config FRV_DEFL_CACHE_WBACK
 181         bool "Write-Back"
 182
 183 config FRV_DEFL_CACHE_WBEHIND
 184         bool "Write-Behind"
 185
 186 config FRV_DEFL_CACHE_WTHRU
 187         bool "Write-Through"
 188
 189 config FRV_DEFL_CACHE_DISABLED
 190         bool "Disabled"
 191
 192 endchoice
 193
 194 menu "CPU core support"
 195
 196 config CPU_FR401
 197         bool "Include FR401 core support"
 198         depends on !MMU
 199         default y
 200         help
 201           This enables support for the FR401, FR401A and FR403 CPUs
 202
 203 config CPU_FR405
 204         bool "Include FR405 core support"
 205         depends on !MMU
 206         default y
 207         help
 208           This enables support for the FR405 CPU
 209
 210 config CPU_FR451
 211         bool "Include FR451 core support"
 212         default y
 213         help
 214           This enables support for the FR451 CPU
 215
 216 config CPU_FR451_COMPILE
 217         bool "Specifically compile for FR451 core"
 218         depends on CPU_FR451 && !CPU_FR401 && !CPU_FR405 && !CPU_FR551
 219         default y
 220         help
 221           This causes appropriate flags to be passed to the compiler to
 222           optimise for the FR451 CPU
 223
 224 config CPU_FR551
 225         bool "Include FR551 core support"
 226         depends on !MMU
 227         default y
 228         help
 229           This enables support for the FR555 CPU
 230
 231 config CPU_FR551_COMPILE
 232         bool "Specifically compile for FR551 core"
 233         depends on CPU_FR551 && !CPU_FR401 && !CPU_FR405 && !CPU_FR451
 234         default y
 235         help
 236           This causes appropriate flags to be passed to the compiler to
 237           optimise for the FR555 CPU
 238
 239 config FRV_L1_CACHE_SHIFT
 240         int
 241         default "5" if CPU_FR401 || CPU_FR405 || CPU_FR451
 242         default "6" if CPU_FR551
 243
 244 endmenu
 245
 246 choice
 247         prompt "System support"
 248         default MB93091_VDK
 249
 250 config MB93091_VDK
 251         bool "MB93091 CPU board with or without motherboard"
 252
 253 config MB93093_PDK
 254         bool "MB93093 PDK unit"
 255
 256 endchoice
 257
 258 if MB93091_VDK
 259 choice
 260         prompt "Motherboard support"
 261         default MB93090_MB00
 262
 263 config MB93090_MB00
 264         bool "Use the MB93090-MB00 motherboard"
 265         help
 266           Select this option if the MB93091 CPU board is going to be used with
 267           a MB93090-MB00 VDK motherboard
 268
 269 config MB93091_NO_MB
 270         bool "Use standalone"
 271         help
 272           Select this option if the MB93091 CPU board is going to be used
 273           without a motherboard
 274
 275 endchoice
 276 endif
 277
 278 config FUJITSU_MB93493
 279         bool "MB93493 Multimedia chip"
 280         help
 281           Select this option if the MB93493 multimedia chip is going to be
 282           used.
 283
 284 choice
 285         prompt "GP-Relative data support"
 286         default GPREL_DATA_8
 287         help
 288           This option controls what data, if any, should be placed in the GP
 289           relative data sections. Using this means that the compiler can
 290           generate accesses to the data using GR16-relative addressing which
 291           is faster than absolute instructions and saves space (2 instructions
 292           per access).
 293
 294           However, the GPREL region is limited in size because the immediate
 295           value used in the load and store instructions is limited to a 12-bit
 296           signed number.
 297
 298           So if the linker starts complaining that accesses to GPREL data are
 299           out of range, try changing this option from the default.
 300
 301           Note that modules will always be compiled with this feature disabled
 302           as the module data will not be in range of the GP base address.
 303
 304 config GPREL_DATA_8
 305         bool "Put data objects of up to 8 bytes into GP-REL"
 306
 307 config GPREL_DATA_4
 308         bool "Put data objects of up to 4 bytes into GP-REL"
 309
 310 config GPREL_DATA_NONE
 311         bool "Don't use GP-REL"
 312
 313 endchoice
 314
 315 config FRV_ONCPU_SERIAL
 316         bool "Use on-CPU serial ports"
 317         select SERIAL_8250
 318         default y
 319
 320 config PCI
 321         bool "Use PCI"
 322         depends on MB93090_MB00
 323         default y
 324         select GENERIC_PCI_IOMAP
 325         help
 326           Some FR-V systems (such as the MB93090-MB00 VDK) have PCI
 327           onboard. If you have one of these boards and you wish to use the PCI
 328           facilities, say Y here.
 329
 330 config RESERVE_DMA_COHERENT
 331         bool "Reserve DMA coherent memory"
 332         depends on PCI && !MMU
 333         default y
 334         help
 335           Many PCI drivers require access to uncached memory for DMA device
 336           communications (such as is done with some Ethernet buffer rings). If
 337           a fully featured MMU is available, this can be done through page
 338           table settings, but if not, a region has to be set aside and marked
 339           with a special DAMPR register.
 340
 341           Setting this option causes uClinux to set aside a portion of the
 342           available memory for use in this manner. The memory will then be
 343           unavailable for normal kernel use.
 344
 345 source "drivers/pci/Kconfig"
 346
 347 source "drivers/pcmcia/Kconfig"
 348
 349 menu "Power management options"
 350
 351 config ARCH_SUSPEND_POSSIBLE
 352         def_bool y
 353
 354 source kernel/power/Kconfig
 355 endmenu
 356
 357 endmenu
 358
 359
 360 menu "Executable formats"
 361
 362 source "fs/Kconfig.binfmt"
 363
 364 endmenu
 365
 366 source "net/Kconfig"
 367
 368 source "drivers/Kconfig"
 369
 370 source "fs/Kconfig"
 371
 372 source "arch/frv/Kconfig.debug"
 373
 374 source "security/Kconfig"
 375
 376 source "crypto/Kconfig"
 377
 378 source "lib/Kconfig"