3 menu "TI OMAP Implementations"
9 prompt "OMAP System Type"
25 comment "OMAP Feature Selections"
27 config OMAP_DEBUG_DEVICES
30 For debug cards on TI reference boards.
32 config OMAP_DEBUG_LEDS
34 depends on OMAP_DEBUG_DEVICES
35 default y if LEDS || LEDS_OMAP_DEBUG
37 config OMAP_DEBUG_POWERDOMAIN
38 bool "Emit debug messages from powerdomain layer"
39 depends on ARCH_OMAP2 || ARCH_OMAP3
42 Say Y here if you want to compile in powerdomain layer
43 debugging messages for OMAP2/3. These messages can
44 provide more detail as to why some powerdomain calls
45 may be failing, and will also emit a descriptive message
46 for every powerdomain register write. However, the
47 extra detail costs some memory.
49 config OMAP_DEBUG_CLOCKDOMAIN
50 bool "Emit debug messages from clockdomain layer"
51 depends on ARCH_OMAP2 || ARCH_OMAP3
54 Say Y here if you want to compile in clockdomain layer
55 debugging messages for OMAP2/3. These messages can
56 provide more detail as to why some clockdomain calls
57 may be failing, and will also emit a descriptive message
58 for every clockdomain register write. However, the
59 extra detail costs some memory.
61 config OMAP_SMARTREFLEX
62 bool "SmartReflex support"
63 depends on ARCH_OMAP34XX && TWL4030_CORE
65 Say Y if you want to enable SmartReflex.
67 SmartReflex can perform continuous dynamic voltage
68 scaling around the nominal operating point voltage
69 according to silicon characteristics and operating
70 conditions. Enabling SmartReflex reduces power
73 Please note, that by default SmartReflex is only
74 initialized. To enable the automatic voltage
75 compensation for VDD1 and VDD2, user must write 1 to
76 /sys/power/sr_vddX_autocomp, where X is 1 or 2.
78 config OMAP_SMARTREFLEX_TESTING
79 bool "Smartreflex testing support"
80 depends on OMAP_SMARTREFLEX
83 Say Y if you want to enable SmartReflex testing with SW hardcoded
84 NVALUES intead of E-fuse NVALUES set in factory silicon testing.
86 In some devices the E-fuse values have not been set, even though
87 SmartReflex modules are included. Using these hardcoded values set
88 in software, one can test the SmartReflex features without E-fuse.
90 WARNING: Enabling this option may cause your device to hang!
92 config OMAP_RESET_CLOCKS
93 bool "Reset unused clocks during boot"
96 Say Y if you want to reset unused clocks during boot.
97 This option saves power, but assumes all drivers are
98 using the clock framework. Broken drivers that do not
99 yet use clock framework may not work with this option.
100 If you are booting from another operating system, you
101 probably do not want this option enabled until your
102 device drivers work properly.
105 bool "OMAP bootloader information passing"
109 Say Y, if you have a bootloader which passes information
110 about your board and its peripheral configuration.
112 config OMAP_BOOT_REASON
113 bool "Support for boot reason"
114 depends on OMAP_BOOT_TAG
117 Say Y, if you want to have a procfs entry for reading the boot
118 reason in user-space.
120 config OMAP_COMPONENT_VERSION
121 bool "Support for component version display"
122 depends on OMAP_BOOT_TAG && PROC_FS
125 Say Y, if you want to have a procfs entry for reading component
126 versions (supplied by the bootloader) in user-space.
128 config OMAP_GPIO_SWITCH
129 bool "GPIO switch support"
132 Say Y, if you want to have support for reporting of GPIO
133 switches (e.g. cover switches) via sysfs. Your bootloader has
134 to provide information about the switches to the kernel via the
135 ATAG_BOARD mechanism if they're not defined by the board config.
138 bool "OMAP multiplexing support"
142 Pin multiplexing support for OMAP boards. If your bootloader
143 sets the multiplexing correctly, say N. Otherwise, or if unsure,
146 config OMAP_MUX_DEBUG
147 bool "Multiplexing debug output"
150 Makes the multiplexing functions print out a lot of debug info.
151 This is useful if you want to find out the correct values of the
152 multiplexing registers.
154 config OMAP_MUX_WARNINGS
155 bool "Warn about pins the bootloader didn't set up"
159 Choose Y here to warn whenever driver initialization logic needs
160 to change the pin multiplexing setup. When there are no warnings
161 printed, it's safe to deselect OMAP_MUX for your product.
168 Say Y here if you want support for the OMAP Multichannel
169 Buffered Serial Port.
172 tristate "Mailbox framework support"
176 Say Y here if you want to use OMAP Mailbox framework support for
177 DSP, IVA1.0 and IVA2 in OMAP1/2/3.
180 prompt "System timer"
181 default OMAP_MPU_TIMER
183 config OMAP_MPU_TIMER
186 Select this option if you want to use the OMAP mpu timer. This
187 timer provides more intra-tick resolution than the 32KHz timer,
188 but consumes more power.
190 config OMAP_32K_TIMER
191 bool "Use 32KHz timer"
192 depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX
194 Select this option if you want to enable the OMAP 32KHz timer.
195 This timer saves power compared to the OMAP_MPU_TIMER, and has
196 support for no tick during idle. The 32KHz timer provides less
197 intra-tick resolution than OMAP_MPU_TIMER. The 32KHz timer is
198 currently only available for OMAP16XX, 24XX and 34XX.
202 config OMAP_32K_TIMER_HZ
203 int "Kernel internal timer frequency for 32KHz timer"
205 depends on OMAP_32K_TIMER
208 Kernel internal timer frequency should be a divisor of 32768,
211 config OMAP_TICK_GPTIMER
212 int "GPTIMER used for system tick timer"
213 depends on ARCH_OMAP2 || ARCH_OMAP3
217 Linux uses one of the twelve on-board OMAP GPTIMER blocks to generate
218 system tick interrupts. The twelve GPTIMERs have slightly
219 different powerdomain, source clock, and security properties
220 (mostly documented in the OMAP3 TRMs) that can affect the selection
221 of which GPTIMER to use. The historical default is GPTIMER1.
222 If CONFIG_OMAP_32K_TIMER is selected, Beagle may require GPTIMER12
223 due to hardware sensitivity to glitches on the OMAP 32kHz clock
227 bool "Use dual-mode timer"
228 depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX
230 Select this option if you want to use OMAP Dual-Mode timers.
233 prompt "Low-level debug console UART"
235 default OMAP_LL_DEBUG_UART1
237 config OMAP_LL_DEBUG_UART1
240 config OMAP_LL_DEBUG_UART2
243 config OMAP_LL_DEBUG_UART3
248 config OMAP_SERIAL_WAKE
249 bool "Enable wake-up events for serial ports"
253 Select this option if you want to have your system wake up
254 to data on the serial RX line. This allows you to wake the
255 system from serial console.