1 comment "Processor Type"
3 # Select CPU types depending on the architecture selected. This selects
4 # which CPUs we support in the kernel image, and the compiler instruction
9 bool "Support ARM7TDMI processor"
14 select CPU_PABRT_LEGACY
16 A 32-bit RISC microprocessor based on the ARM7 processor core
17 which has no memory control unit and cache.
19 Say Y if you want support for the ARM7TDMI processor.
24 bool "Support ARM720T processor" if ARCH_INTEGRATOR
29 select CPU_COPY_V4WT if MMU
31 select CPU_PABRT_LEGACY
32 select CPU_TLB_V4WT if MMU
34 A 32-bit RISC processor with 8kByte Cache, Write Buffer and
35 MMU built around an ARM7TDMI core.
37 Say Y if you want support for the ARM720T processor.
42 bool "Support ARM740T processor" if ARCH_INTEGRATOR
48 select CPU_PABRT_LEGACY
50 A 32-bit RISC processor with 8KB cache or 4KB variants,
51 write buffer and MPU(Protection Unit) built around
54 Say Y if you want support for the ARM740T processor.
59 bool "Support ARM9TDMI processor"
64 select CPU_PABRT_LEGACY
66 A 32-bit RISC microprocessor based on the ARM9 processor core
67 which has no memory control unit and cache.
69 Say Y if you want support for the ARM9TDMI processor.
74 bool "Support ARM920T processor" if ARCH_INTEGRATOR
79 select CPU_COPY_V4WB if MMU
81 select CPU_PABRT_LEGACY
82 select CPU_TLB_V4WBI if MMU
84 The ARM920T is licensed to be produced by numerous vendors,
85 and is used in the Cirrus EP93xx and the Samsung S3C2410.
87 Say Y if you want support for the ARM920T processor.
92 bool "Support ARM922T processor" if ARCH_INTEGRATOR
97 select CPU_COPY_V4WB if MMU
99 select CPU_PABRT_LEGACY
100 select CPU_TLB_V4WBI if MMU
102 The ARM922T is a version of the ARM920T, but with smaller
103 instruction and data caches. It is used in Altera's
104 Excalibur XA device family and Micrel's KS8695 Centaur.
106 Say Y if you want support for the ARM922T processor.
111 bool "Support ARM925T processor" if ARCH_OMAP1
114 select CPU_CACHE_V4WT
115 select CPU_CACHE_VIVT
116 select CPU_COPY_V4WB if MMU
118 select CPU_PABRT_LEGACY
119 select CPU_TLB_V4WBI if MMU
121 The ARM925T is a mix between the ARM920T and ARM926T, but with
122 different instruction and data caches. It is used in TI's OMAP
125 Say Y if you want support for the ARM925T processor.
130 bool "Support ARM926T processor" if ARCH_INTEGRATOR || MACH_REALVIEW_EB
132 select CPU_ABRT_EV5TJ
133 select CPU_CACHE_VIVT
134 select CPU_COPY_V4WB if MMU
136 select CPU_PABRT_LEGACY
137 select CPU_TLB_V4WBI if MMU
139 This is a variant of the ARM920. It has slightly different
140 instruction sequences for cache and TLB operations. Curiously,
141 there is no documentation on it at the ARM corporate website.
143 Say Y if you want support for the ARM926T processor.
152 select CPU_CACHE_VIVT
153 select CPU_COPY_FA if MMU
155 select CPU_PABRT_LEGACY
156 select CPU_TLB_FA if MMU
158 The FA526 is a version of the ARMv4 compatible processor with
159 Branch Target Buffer, Unified TLB and cache line size 16.
161 Say Y if you want support for the FA526 processor.
166 bool "Support ARM940T processor" if ARCH_INTEGRATOR
169 select CPU_ABRT_NOMMU
170 select CPU_CACHE_VIVT
172 select CPU_PABRT_LEGACY
174 ARM940T is a member of the ARM9TDMI family of general-
175 purpose microprocessors with MPU and separate 4KB
176 instruction and 4KB data cases, each with a 4-word line
179 Say Y if you want support for the ARM940T processor.
184 bool "Support ARM946E-S processor" if ARCH_INTEGRATOR
187 select CPU_ABRT_NOMMU
188 select CPU_CACHE_VIVT
190 select CPU_PABRT_LEGACY
192 ARM946E-S is a member of the ARM9E-S family of high-
193 performance, 32-bit system-on-chip processor solutions.
194 The TCM and ARMv5TE 32-bit instruction set is supported.
196 Say Y if you want support for the ARM946E-S processor.
199 # ARM1020 - needs validating
201 bool "Support ARM1020T (rev 0) processor" if ARCH_INTEGRATOR
204 select CPU_CACHE_V4WT
205 select CPU_CACHE_VIVT
206 select CPU_COPY_V4WB if MMU
208 select CPU_PABRT_LEGACY
209 select CPU_TLB_V4WBI if MMU
211 The ARM1020 is the 32K cached version of the ARM10 processor,
212 with an addition of a floating-point unit.
214 Say Y if you want support for the ARM1020 processor.
217 # ARM1020E - needs validating
219 bool "Support ARM1020E processor" if ARCH_INTEGRATOR
223 select CPU_CACHE_V4WT
224 select CPU_CACHE_VIVT
225 select CPU_COPY_V4WB if MMU
227 select CPU_PABRT_LEGACY
228 select CPU_TLB_V4WBI if MMU
232 bool "Support ARM1022E processor" if ARCH_INTEGRATOR
235 select CPU_CACHE_VIVT
236 select CPU_COPY_V4WB if MMU # can probably do better
238 select CPU_PABRT_LEGACY
239 select CPU_TLB_V4WBI if MMU
241 The ARM1022E is an implementation of the ARMv5TE architecture
242 based upon the ARM10 integer core with a 16KiB L1 Harvard cache,
243 embedded trace macrocell, and a floating-point unit.
245 Say Y if you want support for the ARM1022E processor.
250 bool "Support ARM1026EJ-S processor" if ARCH_INTEGRATOR
252 select CPU_ABRT_EV5T # But need Jazelle, but EV5TJ ignores bit 10
253 select CPU_CACHE_VIVT
254 select CPU_COPY_V4WB if MMU # can probably do better
256 select CPU_PABRT_LEGACY
257 select CPU_TLB_V4WBI if MMU
259 The ARM1026EJ-S is an implementation of the ARMv5TEJ architecture
260 based upon the ARM10 integer core.
262 Say Y if you want support for the ARM1026EJ-S processor.
268 select CPU_32v3 if ARCH_RPC
269 select CPU_32v4 if !ARCH_RPC
271 select CPU_CACHE_V4WB
272 select CPU_CACHE_VIVT
273 select CPU_COPY_V4WB if MMU
275 select CPU_PABRT_LEGACY
276 select CPU_TLB_V4WB if MMU
278 The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and
279 is available at five speeds ranging from 100 MHz to 233 MHz.
280 More information is available at
281 <http://developer.intel.com/design/strong/sa110.htm>.
283 Say Y if you want support for the SA-110 processor.
291 select CPU_CACHE_V4WB
292 select CPU_CACHE_VIVT
294 select CPU_PABRT_LEGACY
295 select CPU_TLB_V4WB if MMU
302 select CPU_CACHE_VIVT
304 select CPU_PABRT_LEGACY
305 select CPU_TLB_V4WBI if MMU
307 # XScale Core Version 3
312 select CPU_CACHE_VIVT
314 select CPU_PABRT_LEGACY
315 select CPU_TLB_V4WBI if MMU
318 # Marvell PJ1 (Mohawk)
323 select CPU_CACHE_VIVT
324 select CPU_COPY_V4WB if MMU
326 select CPU_PABRT_LEGACY
327 select CPU_TLB_V4WBI if MMU
334 select CPU_CACHE_VIVT
335 select CPU_COPY_FEROCEON if MMU
337 select CPU_PABRT_LEGACY
338 select CPU_TLB_FEROCEON if MMU
340 config CPU_FEROCEON_OLD_ID
341 bool "Accept early Feroceon cores with an ARM926 ID"
342 depends on CPU_FEROCEON && !CPU_ARM926T
345 This enables the usage of some old Feroceon cores
346 for which the CPU ID is equal to the ARM926 ID.
347 Relevant for Feroceon-1850 and early Feroceon-2850.
361 bool "Support ARM V6 processor" if ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX
365 select CPU_CACHE_VIPT
366 select CPU_COPY_V6 if MMU
368 select CPU_HAS_ASID if MMU
370 select CPU_TLB_V6 if MMU
374 bool "Support ARM V6K processor" if ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX
379 select CPU_CACHE_VIPT
380 select CPU_COPY_V6 if MMU
382 select CPU_HAS_ASID if MMU
384 select CPU_TLB_V6 if MMU
388 bool "Support ARM V7 processor" if ARCH_INTEGRATOR || MACH_REALVIEW_EB || MACH_REALVIEW_PBX
393 select CPU_CACHE_VIPT
394 select CPU_COPY_V6 if MMU
395 select CPU_CP15_MMU if MMU
396 select CPU_CP15_MPU if !MMU
397 select CPU_HAS_ASID if MMU
399 select CPU_TLB_V7 if MMU
405 select CPU_ABRT_NOMMU
407 select CPU_PABRT_LEGACY
412 # There are no CPUs available with MMU that don't implement an ARM ISA:
415 Select this if your CPU doesn't support the 32 bit ARM instructions.
417 # Figure out what processor architecture version we should be using.
418 # This defines the compiler instruction set which depends on the machine type.
421 select CPU_USE_DOMAINS if MMU
422 select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
423 select NEED_KUSER_HELPERS
424 select TLS_REG_EMUL if SMP || !MMU
428 select CPU_USE_DOMAINS if MMU
429 select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
430 select NEED_KUSER_HELPERS
431 select TLS_REG_EMUL if SMP || !MMU
435 select CPU_USE_DOMAINS if MMU
436 select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
437 select NEED_KUSER_HELPERS
438 select TLS_REG_EMUL if SMP || !MMU
442 select CPU_USE_DOMAINS if MMU
443 select NEEDS_SYSCALL_FOR_CMPXCHG if SMP
444 select NEED_KUSER_HELPERS
445 select TLS_REG_EMUL if SMP || !MMU
449 select TLS_REG_EMUL if !CPU_32v6K && !MMU
461 config CPU_ABRT_NOMMU
476 config CPU_ABRT_EV5TJ
485 config CPU_PABRT_LEGACY
498 config CPU_CACHE_V4WT
501 config CPU_CACHE_V4WB
513 config CPU_CACHE_VIVT
516 config CPU_CACHE_VIPT
523 # The copy-page model
530 config CPU_COPY_FEROCEON
539 # This selects the TLB model
543 ARM Architecture Version 4 TLB with writethrough cache.
548 ARM Architecture Version 4 TLB with writeback cache.
553 ARM Architecture Version 4 TLB with writeback cache and invalidate
554 instruction cache entry.
556 config CPU_TLB_FEROCEON
559 Feroceon TLB (v4wbi with non-outer-cachable page table walks).
564 Faraday ARM FA526 architecture, unified TLB with writeback cache
565 and invalidate instruction cache entry. Branch target buffer is
574 config VERIFY_PERMISSION_FAULT
581 This indicates whether the CPU has the ASID register; used to
582 tag TLB and possibly cache entries.
587 Processor has the CP15 register.
593 Processor has the CP15 register, which has MMU related registers.
599 Processor has the CP15 register, which has MPU related registers.
601 config CPU_USE_DOMAINS
604 This option enables or disables the use of domain switching
605 via the set_fs() function.
608 # CPU supports 36-bit I/O
613 comment "Processor Features"
616 bool "Support for the Large Physical Address Extension"
617 depends on MMU && CPU_32v7 && !CPU_32v6 && !CPU_32v5 && \
618 !CPU_32v4 && !CPU_32v3
620 Say Y if you have an ARMv7 processor supporting the LPAE page
621 table format and you would like to access memory beyond the
622 4GB limit. The resulting kernel image will not run on
623 processors without the LPA extension.
627 config ARCH_PHYS_ADDR_T_64BIT
630 config ARCH_DMA_ADDR_T_64BIT
634 bool "Support Thumb user binaries" if !CPU_THUMBONLY
635 depends on CPU_ARM720T || CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || \
636 CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || \
637 CPU_ARM1020 || CPU_ARM1020E || CPU_ARM1022 || CPU_ARM1026 || \
638 CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_V6 || CPU_V6K || \
639 CPU_V7 || CPU_FEROCEON || CPU_V7M
642 Say Y if you want to include kernel support for running user space
645 The Thumb instruction set is a compressed form of the standard ARM
646 instruction set resulting in smaller binaries at the expense of
647 slightly less efficient code.
649 If you don't know what this all is, saying Y is a safe choice.
652 bool "Enable ThumbEE CPU extension"
655 Say Y here if you have a CPU with the ThumbEE extension and code to
656 make use of it. Say N for code that can run on CPUs without ThumbEE.
663 Enable the kernel to make use of the ARM Virtualization
664 Extensions to install hypervisors without run-time firmware
667 A compliant bootloader is required in order to make maximum
668 use of this feature. Refer to Documentation/arm/Booting for
672 bool "Emulate SWP/SWPB instructions" if !SMP
675 select HAVE_PROC_CPU if PROC_FS
677 ARMv6 architecture deprecates use of the SWP/SWPB instructions.
678 ARMv7 multiprocessing extensions introduce the ability to disable
679 these instructions, triggering an undefined instruction exception
680 when executed. Say Y here to enable software emulation of these
681 instructions for userspace (not kernel) using LDREX/STREX.
682 Also creates /proc/cpu/swp_emulation for statistics.
684 In some older versions of glibc [<=2.8] SWP is used during futex
685 trylock() operations with the assumption that the code will not
686 be preempted. This invalid assumption may be more likely to fail
687 with SWP emulation enabled, leading to deadlock of the user
690 NOTE: when accessing uncached shared regions, LDREX/STREX rely
691 on an external transaction monitoring block called a global
692 monitor to maintain update atomicity. If your system does not
693 implement a global monitor, this option can cause programs that
694 perform SWP operations to uncached memory to deadlock.
698 config CPU_BIG_ENDIAN
699 bool "Build big-endian kernel"
700 depends on ARCH_SUPPORTS_BIG_ENDIAN
702 Say Y if you plan on running a kernel in big-endian mode.
703 Note that your board must be properly built and your board
704 port must properly enable any big-endian related features
705 of your chipset/board/processor.
707 config CPU_ENDIAN_BE8
709 depends on CPU_BIG_ENDIAN
710 default CPU_V6 || CPU_V6K || CPU_V7
712 Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors.
714 config CPU_ENDIAN_BE32
716 depends on CPU_BIG_ENDIAN
717 default !CPU_ENDIAN_BE8
719 Support for the BE-32 (big-endian) mode on pre-ARMv6 processors.
721 config CPU_HIGH_VECTOR
722 depends on !MMU && CPU_CP15 && !CPU_ARM740T
723 bool "Select the High exception vector"
725 Say Y here to select high exception vector(0xFFFF0000~).
726 The exception vector can vary depending on the platform
727 design in nommu mode. If your platform needs to select
728 high exception vector, say Y.
729 Otherwise or if you are unsure, say N, and the low exception
730 vector (0x00000000~) will be used.
732 config CPU_ICACHE_DISABLE
733 bool "Disable I-Cache (I-bit)"
734 depends on CPU_CP15 && !(CPU_ARM720T || CPU_ARM740T || CPU_XSCALE || CPU_XSC3)
736 Say Y here to disable the processor instruction cache. Unless
737 you have a reason not to or are unsure, say N.
739 config CPU_DCACHE_DISABLE
740 bool "Disable D-Cache (C-bit)"
743 Say Y here to disable the processor data cache. Unless
744 you have a reason not to or are unsure, say N.
746 config CPU_DCACHE_SIZE
748 depends on CPU_ARM740T || CPU_ARM946E
749 default 0x00001000 if CPU_ARM740T
750 default 0x00002000 # default size for ARM946E-S
752 Some cores are synthesizable to have various sized cache. For
753 ARM946E-S case, it can vary from 0KB to 1MB.
754 To support such cache operations, it is efficient to know the size
756 If your SoC is configured to have a different size, define the value
757 here with proper conditions.
759 config CPU_DCACHE_WRITETHROUGH
760 bool "Force write through D-cache"
761 depends on (CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || CPU_ARM1020 || CPU_FA526) && !CPU_DCACHE_DISABLE
762 default y if CPU_ARM925T
764 Say Y here to use the data cache in writethrough mode. Unless you
765 specifically require this or are unsure, say N.
767 config CPU_CACHE_ROUND_ROBIN
768 bool "Round robin I and D cache replacement algorithm"
769 depends on (CPU_ARM926T || CPU_ARM946E || CPU_ARM1020) && (!CPU_ICACHE_DISABLE || !CPU_DCACHE_DISABLE)
771 Say Y here to use the predictable round-robin cache replacement
772 policy. Unless you specifically require this or are unsure, say N.
774 config CPU_BPREDICT_DISABLE
775 bool "Disable branch prediction"
776 depends on CPU_ARM1020 || CPU_V6 || CPU_V6K || CPU_MOHAWK || CPU_XSC3 || CPU_V7 || CPU_FA526
778 Say Y here to disable branch prediction. If unsure, say N.
782 select NEED_KUSER_HELPERS
784 An SMP system using a pre-ARMv6 processor (there are apparently
785 a few prototypes like that in existence) and therefore access to
786 that required register must be emulated.
788 config NEEDS_SYSCALL_FOR_CMPXCHG
790 select NEED_KUSER_HELPERS
792 SMP on a pre-ARMv6 processor? Well OK then.
793 Forget about fast user space cmpxchg support.
794 It is just not possible.
796 config NEED_KUSER_HELPERS
800 bool "Enable kuser helpers in vector page" if !NEED_KUSER_HELPERS
803 Warning: disabling this option may break user programs.
805 Provide kuser helpers in the vector page. The kernel provides
806 helper code to userspace in read only form at a fixed location
807 in the high vector page to allow userspace to be independent of
808 the CPU type fitted to the system. This permits binaries to be
809 run on ARMv4 through to ARMv7 without modification.
811 See Documentation/arm/kernel_user_helpers.txt for details.
813 However, the fixed address nature of these helpers can be used
814 by ROP (return orientated programming) authors when creating
817 If all of the binaries and libraries which run on your platform
818 are built specifically for your platform, and make no use of
819 these helpers, then you can turn this option off to hinder
820 such exploits. However, in that case, if a binary or library
821 relying on those helpers is run, it will receive a SIGILL signal,
822 which will terminate the program.
824 Say N here only if you are absolutely certain that you do not
825 need these helpers; otherwise, the safe option is to say Y.
827 config DMA_CACHE_RWFO
828 bool "Enable read/write for ownership DMA cache maintenance"
829 depends on CPU_V6K && SMP
832 The Snoop Control Unit on ARM11MPCore does not detect the
833 cache maintenance operations and the dma_{map,unmap}_area()
834 functions may leave stale cache entries on other CPUs. By
835 enabling this option, Read or Write For Ownership in the ARMv6
836 DMA cache maintenance functions is performed. These LDR/STR
837 instructions change the cache line state to shared or modified
838 so that the cache operation has the desired effect.
840 Note that the workaround is only valid on processors that do
841 not perform speculative loads into the D-cache. For such
842 processors, if cache maintenance operations are not broadcast
843 in hardware, other workarounds are needed (e.g. cache
844 maintenance broadcasting in software via FIQ).
849 config OUTER_CACHE_SYNC
852 The outer cache has a outer_cache_fns.sync function pointer
853 that can be used to drain the write buffer of the outer cache.
855 config CACHE_FEROCEON_L2
856 bool "Enable the Feroceon L2 cache controller"
857 depends on ARCH_MV78XX0 || ARCH_MVEBU
861 This option enables the Feroceon L2 cache controller.
863 config CACHE_FEROCEON_L2_WRITETHROUGH
864 bool "Force Feroceon L2 cache write through"
865 depends on CACHE_FEROCEON_L2
867 Say Y here to use the Feroceon L2 cache in writethrough mode.
868 Unless you specifically require this, say N for writeback mode.
870 config MIGHT_HAVE_CACHE_L2X0
873 This option should be selected by machines which have a L2x0
874 or PL310 cache controller, but where its use is optional.
876 The only effect of this option is to make CACHE_L2X0 and
877 related options available to the user for configuration.
879 Boards or SoCs which always require the cache controller
880 support to be present should select CACHE_L2X0 directly
881 instead of this option, thus preventing the user from
882 inadvertently configuring a broken kernel.
885 bool "Enable the L2x0 outer cache controller" if MIGHT_HAVE_CACHE_L2X0
886 default MIGHT_HAVE_CACHE_L2X0
888 select OUTER_CACHE_SYNC
890 This option enables the L2x0 PrimeCell.
896 default y if CPU_V7 && !(CPU_V6 || CPU_V6K)
898 This option enables optimisations for the PL310 cache
901 config PL310_ERRATA_588369
902 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
904 The PL310 L2 cache controller implements three types of Clean &
905 Invalidate maintenance operations: by Physical Address
906 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
907 They are architecturally defined to behave as the execution of a
908 clean operation followed immediately by an invalidate operation,
909 both performing to the same memory location. This functionality
910 is not correctly implemented in PL310 prior to r2p0 (fixed in r2p0)
911 as clean lines are not invalidated as a result of these operations.
913 config PL310_ERRATA_727915
914 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
916 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
917 operation (offset 0x7FC). This operation runs in background so that
918 PL310 can handle normal accesses while it is in progress. Under very
919 rare circumstances, due to this erratum, write data can be lost when
920 PL310 treats a cacheable write transaction during a Clean &
921 Invalidate by Way operation. Revisions prior to r3p1 are affected by
922 this errata (fixed in r3p1).
924 config PL310_ERRATA_753970
925 bool "PL310 errata: cache sync operation may be faulty"
927 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
929 Under some condition the effect of cache sync operation on
930 the store buffer still remains when the operation completes.
931 This means that the store buffer is always asked to drain and
932 this prevents it from merging any further writes. The workaround
933 is to replace the normal offset of cache sync operation (0x730)
934 by another offset targeting an unmapped PL310 register 0x740.
935 This has the same effect as the cache sync operation: store buffer
936 drain and waiting for all buffers empty.
938 config PL310_ERRATA_769419
939 bool "PL310 errata: no automatic Store Buffer drain"
941 On revisions of the PL310 prior to r3p2, the Store Buffer does
942 not automatically drain. This can cause normal, non-cacheable
943 writes to be retained when the memory system is idle, leading
944 to suboptimal I/O performance for drivers using coherent DMA.
945 This option adds a write barrier to the cpu_idle loop so that,
946 on systems with an outer cache, the store buffer is drained
952 bool "Enable the Tauros2 L2 cache controller"
953 depends on (ARCH_DOVE || ARCH_MMP || CPU_PJ4)
957 This option enables the Tauros2 L2 cache controller (as
961 bool "Enable the L2 cache on XScale3"
966 This option enables the L2 cache on XScale3.
968 config ARM_L1_CACHE_SHIFT_6
972 Setting ARM L1 cache line size to 64 Bytes.
974 config ARM_L1_CACHE_SHIFT
976 default 6 if ARM_L1_CACHE_SHIFT_6
979 config ARM_DMA_MEM_BUFFERABLE
980 bool "Use non-cacheable memory for DMA" if (CPU_V6 || CPU_V6K) && !CPU_V7
981 depends on !(MACH_REALVIEW_PB1176 || REALVIEW_EB_ARM11MP || \
982 MACH_REALVIEW_PB11MP)
983 default y if CPU_V6 || CPU_V6K || CPU_V7
985 Historically, the kernel has used strongly ordered mappings to
986 provide DMA coherent memory. With the advent of ARMv7, mapping
987 memory with differing types results in unpredictable behaviour,
988 so on these CPUs, this option is forced on.
990 Multiple mappings with differing attributes is also unpredictable
991 on ARMv6 CPUs, but since they do not have aggressive speculative
992 prefetch, no harm appears to occur.
994 However, drivers may be missing the necessary barriers for ARMv6,
995 and therefore turning this on may result in unpredictable driver
996 behaviour. Therefore, we offer this as an option.
998 You are recommended say 'Y' here and debug any affected drivers.
1000 config ARCH_HAS_BARRIERS
1003 This option allows the use of custom mandatory barriers
1004 included via the mach/barriers.h file.
1006 config ARCH_SUPPORTS_BIG_ENDIAN
1009 This option specifies the architecture can support big endian