20 select CPU_HAS_PTEA if (!CPU_SUBTYPE_ST40 && !CPU_SH4A) || CPU_SHX2
31 config CPU_SUBTYPE_ST40
42 prompt "Processor sub-type selection"
48 # SH-2 Processor Support
50 config CPU_SUBTYPE_SH7619
51 bool "Support SH7619 processor"
53 select CPU_HAS_IPR_IRQ
55 # SH-2A Processor Support
57 config CPU_SUBTYPE_SH7206
58 bool "Support SH7206 processor"
60 select CPU_HAS_IPR_IRQ
62 # SH-3 Processor Support
64 config CPU_SUBTYPE_SH7705
65 bool "Support SH7705 processor"
67 select CPU_HAS_INTC_IRQ
69 config CPU_SUBTYPE_SH7706
70 bool "Support SH7706 processor"
72 select CPU_HAS_INTC_IRQ
74 Select SH7706 if you have a 133 Mhz SH-3 HD6417706 CPU.
76 config CPU_SUBTYPE_SH7707
77 bool "Support SH7707 processor"
79 select CPU_HAS_INTC_IRQ
81 Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU.
83 config CPU_SUBTYPE_SH7708
84 bool "Support SH7708 processor"
86 select CPU_HAS_INTC_IRQ
88 Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
89 if you have a 100 Mhz SH-3 HD6417708R CPU.
91 config CPU_SUBTYPE_SH7709
92 bool "Support SH7709 processor"
94 select CPU_HAS_INTC_IRQ
96 Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
98 config CPU_SUBTYPE_SH7710
99 bool "Support SH7710 processor"
101 select CPU_HAS_INTC_IRQ
104 Select SH7710 if you have a SH3-DSP SH7710 CPU.
106 config CPU_SUBTYPE_SH7712
107 bool "Support SH7712 processor"
109 select CPU_HAS_INTC_IRQ
112 Select SH7712 if you have a SH3-DSP SH7712 CPU.
114 # SH-4 Processor Support
116 config CPU_SUBTYPE_SH7750
117 bool "Support SH7750 processor"
119 select CPU_HAS_INTC_IRQ
121 Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
123 config CPU_SUBTYPE_SH7091
124 bool "Support SH7091 processor"
126 select CPU_HAS_INTC_IRQ
128 Select SH7091 if you have an SH-4 based Sega device (such as
129 the Dreamcast, Naomi, and Naomi 2).
131 config CPU_SUBTYPE_SH7750R
132 bool "Support SH7750R processor"
134 select CPU_HAS_INTC_IRQ
136 config CPU_SUBTYPE_SH7750S
137 bool "Support SH7750S processor"
139 select CPU_HAS_INTC_IRQ
141 config CPU_SUBTYPE_SH7751
142 bool "Support SH7751 processor"
144 select CPU_HAS_INTC_IRQ
146 Select SH7751 if you have a 166 Mhz SH-4 HD6417751 CPU,
147 or if you have a HD6417751R CPU.
149 config CPU_SUBTYPE_SH7751R
150 bool "Support SH7751R processor"
152 select CPU_HAS_INTC_IRQ
154 config CPU_SUBTYPE_SH7760
155 bool "Support SH7760 processor"
157 select CPU_HAS_INTC_IRQ
159 config CPU_SUBTYPE_SH4_202
160 bool "Support SH4-202 processor"
163 # ST40 Processor Support
165 config CPU_SUBTYPE_ST40STB1
166 bool "Support ST40STB1/ST40RA processors"
167 select CPU_SUBTYPE_ST40
169 Select ST40STB1 if you have a ST40RA CPU.
170 This was previously called the ST40STB1, hence the option name.
172 config CPU_SUBTYPE_ST40GX1
173 bool "Support ST40GX1 processor"
174 select CPU_SUBTYPE_ST40
176 Select ST40GX1 if you have a ST40GX1 CPU.
178 # SH-4A Processor Support
180 config CPU_SUBTYPE_SH7770
181 bool "Support SH7770 processor"
184 config CPU_SUBTYPE_SH7780
185 bool "Support SH7780 processor"
187 select CPU_HAS_INTC_IRQ
189 config CPU_SUBTYPE_SH7785
190 bool "Support SH7785 processor"
193 select CPU_HAS_INTC_IRQ
195 config CPU_SUBTYPE_SHX3
196 bool "Support SH-X3 processor"
199 select CPU_HAS_INTC_IRQ
200 select ARCH_SPARSEMEM_ENABLE
201 select SYS_SUPPORTS_NUMA
203 # SH4AL-DSP Processor Support
205 config CPU_SUBTYPE_SH7343
206 bool "Support SH7343 processor"
209 config CPU_SUBTYPE_SH7722
210 bool "Support SH7722 processor"
213 select CPU_HAS_INTC_IRQ
214 select ARCH_SPARSEMEM_ENABLE
215 select SYS_SUPPORTS_NUMA
219 menu "Memory management options"
225 bool "Support for memory management hardware"
229 Some SH processors (such as SH-2/SH-2A) lack an MMU. In order to
230 boot on these systems, this option must not be set.
232 On other systems (such as the SH-3 and 4) where an MMU exists,
233 turning this off will boot the kernel on these machines with the
234 MMU implicitly switched off.
238 default "0x80000000" if MMU
242 hex "Physical memory start address"
245 Computers built with Hitachi SuperH processors always
246 map the ROM starting at address zero. But the processor
247 does not specify the range that RAM takes.
249 The physical memory (RAM) start address will be automatically
250 set to 08000000. Other platforms, such as the Solution Engine
251 boards typically map RAM at 0C000000.
253 Tweak this only when porting to a new machine which does not
254 already have a defconfig. Changing it from the known correct
255 value on any of the known systems will only lead to disaster.
258 hex "Physical memory size"
261 This sets the default memory size assumed by your SH kernel. It can
262 be overridden as normal by the 'mem=' argument on the kernel command
263 line. If unsure, consult your board specifications or just leave it
264 as 0x00400000 which was the default value before this became
268 bool "Support 32-bit physical addressing through PMB"
269 depends on MMU && (CPU_SUBTYPE_SH7780 || CPU_SUBTYPE_SH7785)
272 If you say Y here, physical addressing will be extended to
273 32-bits through the SH-4A PMB. If this is not set, legacy
274 29-bit physical addressing will be used.
277 bool "Enable extended TLB mode"
278 depends on CPU_SHX2 && MMU && EXPERIMENTAL
280 Selecting this option will enable the extended mode of the SH-X2
281 TLB. For legacy SH-X behaviour and interoperability, say N. For
282 all of the fun new features and a willingless to submit bug reports,
286 bool "Support vsyscall page"
290 This will enable support for the kernel mapping a vDSO page
291 in process space, and subsequently handing down the entry point
292 to the libc through the ELF auxiliary vector.
294 From the kernel side this is used for the signal trampoline.
295 For systems with an MMU that can afford to give up a page,
296 (the default value) say Y.
299 bool "Non Uniform Memory Access (NUMA) Support"
300 depends on MMU && SYS_SUPPORTS_NUMA && EXPERIMENTAL
303 Some SH systems have many various memories scattered around
304 the address space, each with varying latencies. This enables
305 support for these blocks by binding them to nodes and allowing
306 memory policies to be used for prioritizing and controlling
307 allocation behaviour.
311 default "3" if CPU_SUBTYPE_SHX3
313 depends on NEED_MULTIPLE_NODES
315 config ARCH_FLATMEM_ENABLE
319 config ARCH_SPARSEMEM_ENABLE
321 select SPARSEMEM_STATIC
323 config ARCH_SPARSEMEM_DEFAULT
326 config MAX_ACTIVE_REGIONS
328 default "6" if (CPU_SUBTYPE_SHX3 && SPARSEMEM)
329 default "2" if (CPU_SUBTYPE_SH7722 && SPARSEMEM)
332 config ARCH_POPULATES_NODE_MAP
335 config ARCH_SELECT_MEMORY_MODEL
338 config ARCH_ENABLE_MEMORY_HOTPLUG
342 config ARCH_MEMORY_PROBE
344 depends on MEMORY_HOTPLUG
347 prompt "Kernel page size"
348 default PAGE_SIZE_4KB
353 This is the default page size used by all SuperH CPUs.
357 depends on EXPERIMENTAL && X2TLB
359 This enables 8kB pages as supported by SH-X2 and later MMUs.
361 config PAGE_SIZE_64KB
363 depends on EXPERIMENTAL && CPU_SH4
365 This enables support for 64kB pages, possible on all SH-4
366 CPUs and later. Highly experimental, not recommended.
371 prompt "HugeTLB page size"
372 depends on HUGETLB_PAGE && CPU_SH4 && MMU
373 default HUGETLB_PAGE_SIZE_64K
375 config HUGETLB_PAGE_SIZE_64K
378 config HUGETLB_PAGE_SIZE_256K
382 config HUGETLB_PAGE_SIZE_1MB
385 config HUGETLB_PAGE_SIZE_4MB
389 config HUGETLB_PAGE_SIZE_64MB
399 menu "Cache configuration"
401 config SH7705_CACHE_32KB
402 bool "Enable 32KB cache size for SH7705"
403 depends on CPU_SUBTYPE_SH7705
406 config SH_DIRECT_MAPPED
407 bool "Use direct-mapped caching"
410 Selecting this option will configure the caches to be direct-mapped,
411 even if the cache supports a 2 or 4-way mode. This is useful primarily
412 for debugging on platforms with 2 and 4-way caches (SH7750R/SH7751R,
413 SH4-202, SH4-501, etc.)
415 Turn this option off for platforms that do not have a direct-mapped
416 cache, and you have no need to run the caches in such a configuration.
420 default CACHE_WRITEBACK if CPU_SH2A || CPU_SH3 || CPU_SH4
421 default CACHE_WRITETHROUGH if (CPU_SH2 && !CPU_SH2A)
423 config CACHE_WRITEBACK
425 depends on CPU_SH2A || CPU_SH3 || CPU_SH4
427 config CACHE_WRITETHROUGH
430 Selecting this option will configure the caches in write-through
431 mode, as opposed to the default write-back configuration.
433 Since there's sill some aliasing issues on SH-4, this option will
434 unfortunately still require the majority of flushing functions to
435 be implemented to deal with aliasing.