1 menu "Processor selection"
7 select SH_WRITETHROUGH if !CPU_SH2A
32 config CPU_SUBTYPE_ST40
35 select CPU_HAS_INTC2_IRQ
41 comment "SH-2 Processor Support"
43 config CPU_SUBTYPE_SH7604
44 bool "Support SH7604 processor"
47 config CPU_SUBTYPE_SH7619
48 bool "Support SH7619 processor"
51 comment "SH-2A Processor Support"
53 config CPU_SUBTYPE_SH7206
54 bool "Support SH7206 processor"
57 comment "SH-3 Processor Support"
59 config CPU_SUBTYPE_SH7300
60 bool "Support SH7300 processor"
63 config CPU_SUBTYPE_SH7705
64 bool "Support SH7705 processor"
66 select CPU_HAS_PINT_IRQ
68 config CPU_SUBTYPE_SH7706
69 bool "Support SH7706 processor"
72 Select SH7706 if you have a 133 Mhz SH-3 HD6417706 CPU.
74 config CPU_SUBTYPE_SH7707
75 bool "Support SH7707 processor"
77 select CPU_HAS_PINT_IRQ
79 Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU.
81 config CPU_SUBTYPE_SH7708
82 bool "Support SH7708 processor"
85 Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
86 if you have a 100 Mhz SH-3 HD6417708R CPU.
88 config CPU_SUBTYPE_SH7709
89 bool "Support SH7709 processor"
91 select CPU_HAS_PINT_IRQ
93 Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
95 config CPU_SUBTYPE_SH7710
96 bool "Support SH7710 processor"
99 Select SH7710 if you have a SH3-DSP SH7710 CPU.
101 comment "SH-4 Processor Support"
103 config CPU_SUBTYPE_SH7750
104 bool "Support SH7750 processor"
107 Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
109 config CPU_SUBTYPE_SH7091
110 bool "Support SH7091 processor"
112 select CPU_SUBTYPE_SH7750
114 Select SH7091 if you have an SH-4 based Sega device (such as
115 the Dreamcast, Naomi, and Naomi 2).
117 config CPU_SUBTYPE_SH7750R
118 bool "Support SH7750R processor"
120 select CPU_SUBTYPE_SH7750
122 config CPU_SUBTYPE_SH7750S
123 bool "Support SH7750S processor"
125 select CPU_SUBTYPE_SH7750
127 config CPU_SUBTYPE_SH7751
128 bool "Support SH7751 processor"
131 Select SH7751 if you have a 166 Mhz SH-4 HD6417751 CPU,
132 or if you have a HD6417751R CPU.
134 config CPU_SUBTYPE_SH7751R
135 bool "Support SH7751R processor"
137 select CPU_SUBTYPE_SH7751
139 config CPU_SUBTYPE_SH7760
140 bool "Support SH7760 processor"
142 select CPU_HAS_INTC2_IRQ
144 config CPU_SUBTYPE_SH4_202
145 bool "Support SH4-202 processor"
148 comment "ST40 Processor Support"
150 config CPU_SUBTYPE_ST40STB1
151 bool "Support ST40STB1/ST40RA processors"
152 select CPU_SUBTYPE_ST40
154 Select ST40STB1 if you have a ST40RA CPU.
155 This was previously called the ST40STB1, hence the option name.
157 config CPU_SUBTYPE_ST40GX1
158 bool "Support ST40GX1 processor"
159 select CPU_SUBTYPE_ST40
161 Select ST40GX1 if you have a ST40GX1 CPU.
163 comment "SH-4A Processor Support"
165 config CPU_SUBTYPE_SH7770
166 bool "Support SH7770 processor"
169 config CPU_SUBTYPE_SH7780
170 bool "Support SH7780 processor"
172 select CPU_HAS_INTC2_IRQ
174 config CPU_SUBTYPE_SH7785
175 bool "Support SH7785 processor"
177 select CPU_HAS_INTC2_IRQ
179 comment "SH4AL-DSP Processor Support"
181 config CPU_SUBTYPE_SH73180
182 bool "Support SH73180 processor"
185 config CPU_SUBTYPE_SH7343
186 bool "Support SH7343 processor"
191 menu "Memory management options"
194 bool "Support for memory management hardware"
198 Some SH processors (such as SH-2/SH-2A) lack an MMU. In order to
199 boot on these systems, this option must not be set.
201 On other systems (such as the SH-3 and 4) where an MMU exists,
202 turning this off will boot the kernel on these machines with the
203 MMU implicitly switched off.
207 default "0x80000000" if MMU
211 hex "Physical memory start address"
214 Computers built with Hitachi SuperH processors always
215 map the ROM starting at address zero. But the processor
216 does not specify the range that RAM takes.
218 The physical memory (RAM) start address will be automatically
219 set to 08000000. Other platforms, such as the Solution Engine
220 boards typically map RAM at 0C000000.
222 Tweak this only when porting to a new machine which does not
223 already have a defconfig. Changing it from the known correct
224 value on any of the known systems will only lead to disaster.
227 hex "Physical memory size"
230 This sets the default memory size assumed by your SH kernel. It can
231 be overridden as normal by the 'mem=' argument on the kernel command
232 line. If unsure, consult your board specifications or just leave it
233 as 0x00400000 which was the default value before this became
237 bool "Support 32-bit physical addressing through PMB"
238 depends on CPU_SH4A && MMU
241 If you say Y here, physical addressing will be extended to
242 32-bits through the SH-4A PMB. If this is not set, legacy
243 29-bit physical addressing will be used.
246 bool "Support vsyscall page"
250 This will enable support for the kernel mapping a vDSO page
251 in process space, and subsequently handing down the entry point
252 to the libc through the ELF auxiliary vector.
254 From the kernel side this is used for the signal trampoline.
255 For systems with an MMU that can afford to give up a page,
256 (the default value) say Y.
259 prompt "HugeTLB page size"
260 depends on HUGETLB_PAGE && CPU_SH4 && MMU
261 default HUGETLB_PAGE_SIZE_64K
263 config HUGETLB_PAGE_SIZE_64K
266 config HUGETLB_PAGE_SIZE_1MB
275 menu "Cache configuration"
277 config SH7705_CACHE_32KB
278 bool "Enable 32KB cache size for SH7705"
279 depends on CPU_SUBTYPE_SH7705
282 config SH_DIRECT_MAPPED
283 bool "Use direct-mapped caching"
286 Selecting this option will configure the caches to be direct-mapped,
287 even if the cache supports a 2 or 4-way mode. This is useful primarily
288 for debugging on platforms with 2 and 4-way caches (SH7750R/SH7751R,
289 SH4-202, SH4-501, etc.)
291 Turn this option off for platforms that do not have a direct-mapped
292 cache, and you have no need to run the caches in such a configuration.
294 config SH_WRITETHROUGH
295 bool "Use write-through caching"
297 Selecting this option will configure the caches in write-through
298 mode, as opposed to the default write-back configuration.
300 Since there's sill some aliasing issues on SH-4, this option will
301 unfortunately still require the majority of flushing functions to
302 be implemented to deal with aliasing.
307 bool "Operand Cache RAM (OCRAM) support"
309 Selecting this option will automatically tear down the number of
310 sets in the dcache by half, which in turn exposes a memory range.
312 The addresses for the OC RAM base will vary according to the
313 processor version. Consult vendor documentation for specifics.