aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'arch/arm/Kconfig')
-rw-r--r--arch/arm/Kconfig53
1 files changed, 0 insertions, 53 deletions
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index a91009c6187..dc57d379235 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1739,59 +1739,6 @@ config FORCE_MAX_ZONEORDER
1739 This config option is actually maximum order plus one. For example, 1739 This config option is actually maximum order plus one. For example,
1740 a value of 11 means that the largest free memory block is 2^10 pages. 1740 a value of 11 means that the largest free memory block is 2^10 pages.
1741 1741
1742config LEDS
1743 bool "Timer and CPU usage LEDs"
1744 depends on ARCH_CDB89712 || ARCH_EBSA110 || \
1745 ARCH_EBSA285 || ARCH_INTEGRATOR || \
1746 ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
1747 ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
1748 ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE || \
1749 ARCH_AT91 || ARCH_DAVINCI || \
1750 ARCH_KS8695 || MACH_RD88F5182 || ARCH_REALVIEW
1751 help
1752 If you say Y here, the LEDs on your machine will be used
1753 to provide useful information about your current system status.
1754
1755 If you are compiling a kernel for a NetWinder or EBSA-285, you will
1756 be able to select which LEDs are active using the options below. If
1757 you are compiling a kernel for the EBSA-110 or the LART however, the
1758 red LED will simply flash regularly to indicate that the system is
1759 still functional. It is safe to say Y here if you have a CATS
1760 system, but the driver will do nothing.
1761
1762config LEDS_TIMER
1763 bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
1764 OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1765 || MACH_OMAP_PERSEUS2
1766 depends on LEDS
1767 depends on !GENERIC_CLOCKEVENTS
1768 default y if ARCH_EBSA110
1769 help
1770 If you say Y here, one of the system LEDs (the green one on the
1771 NetWinder, the amber one on the EBSA285, or the red one on the LART)
1772 will flash regularly to indicate that the system is still
1773 operational. This is mainly useful to kernel hackers who are
1774 debugging unstable kernels.
1775
1776 The LART uses the same LED for both Timer LED and CPU usage LED
1777 functions. You may choose to use both, but the Timer LED function
1778 will overrule the CPU usage LED.
1779
1780config LEDS_CPU
1781 bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
1782 !ARCH_OMAP) \
1783 || OMAP_OSK_MISTRAL || MACH_OMAP_H2 \
1784 || MACH_OMAP_PERSEUS2
1785 depends on LEDS
1786 help
1787 If you say Y here, the red LED will be used to give a good real
1788 time indication of CPU usage, by lighting whenever the idle task
1789 is not currently executing.
1790
1791 The LART uses the same LED for both Timer LED and CPU usage LED
1792 functions. You may choose to use both, but the Timer LED function
1793 will overrule the CPU usage LED.
1794
1795config ALIGNMENT_TRAP 1742config ALIGNMENT_TRAP
1796 bool 1743 bool
1797 depends on CPU_CP15_MMU 1744 depends on CPU_CP15_MMU