Kconfig 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188
  1. if ARCH_OMAP
  2. menu "TI OMAP Implementations"
  3. config ARCH_OMAP_OTG
  4. bool
  5. choice
  6. prompt "OMAP System Type"
  7. default ARCH_OMAP1
  8. config ARCH_OMAP1
  9. bool "TI OMAP1"
  10. select COMMON_CLKDEV
  11. config ARCH_OMAP2
  12. bool "TI OMAP2"
  13. select CPU_V6
  14. select COMMON_CLKDEV
  15. config ARCH_OMAP3
  16. bool "TI OMAP3"
  17. select CPU_V7
  18. select COMMON_CLKDEV
  19. config ARCH_OMAP4
  20. bool "TI OMAP4"
  21. select CPU_V7
  22. select ARM_GIC
  23. endchoice
  24. comment "OMAP Feature Selections"
  25. config OMAP_DEBUG_DEVICES
  26. bool
  27. help
  28. For debug cards on TI reference boards.
  29. config OMAP_DEBUG_LEDS
  30. bool
  31. depends on OMAP_DEBUG_DEVICES
  32. default y if LEDS || LEDS_OMAP_DEBUG
  33. config OMAP_DEBUG_POWERDOMAIN
  34. bool "Emit debug messages from powerdomain layer"
  35. depends on ARCH_OMAP2 || ARCH_OMAP3
  36. help
  37. Say Y here if you want to compile in powerdomain layer
  38. debugging messages for OMAP2/3. These messages can
  39. provide more detail as to why some powerdomain calls
  40. may be failing, and will also emit a descriptive message
  41. for every powerdomain register write. However, the
  42. extra detail costs some memory.
  43. config OMAP_DEBUG_CLOCKDOMAIN
  44. bool "Emit debug messages from clockdomain layer"
  45. depends on ARCH_OMAP2 || ARCH_OMAP3
  46. help
  47. Say Y here if you want to compile in clockdomain layer
  48. debugging messages for OMAP2/3. These messages can
  49. provide more detail as to why some clockdomain calls
  50. may be failing, and will also emit a descriptive message
  51. for every clockdomain register write. However, the
  52. extra detail costs some memory.
  53. config OMAP_RESET_CLOCKS
  54. bool "Reset unused clocks during boot"
  55. depends on ARCH_OMAP
  56. help
  57. Say Y if you want to reset unused clocks during boot.
  58. This option saves power, but assumes all drivers are
  59. using the clock framework. Broken drivers that do not
  60. yet use clock framework may not work with this option.
  61. If you are booting from another operating system, you
  62. probably do not want this option enabled until your
  63. device drivers work properly.
  64. config OMAP_MUX
  65. bool "OMAP multiplexing support"
  66. depends on ARCH_OMAP
  67. default y
  68. help
  69. Pin multiplexing support for OMAP boards. If your bootloader
  70. sets the multiplexing correctly, say N. Otherwise, or if unsure,
  71. say Y.
  72. config OMAP_MUX_DEBUG
  73. bool "Multiplexing debug output"
  74. depends on OMAP_MUX
  75. help
  76. Makes the multiplexing functions print out a lot of debug info.
  77. This is useful if you want to find out the correct values of the
  78. multiplexing registers.
  79. config OMAP_MUX_WARNINGS
  80. bool "Warn about pins the bootloader didn't set up"
  81. depends on OMAP_MUX
  82. default y
  83. help
  84. Choose Y here to warn whenever driver initialization logic needs
  85. to change the pin multiplexing setup. When there are no warnings
  86. printed, it's safe to deselect OMAP_MUX for your product.
  87. config OMAP_MCBSP
  88. bool "McBSP support"
  89. depends on ARCH_OMAP
  90. default y
  91. help
  92. Say Y here if you want support for the OMAP Multichannel
  93. Buffered Serial Port.
  94. config OMAP_MBOX_FWK
  95. tristate "Mailbox framework support"
  96. depends on ARCH_OMAP
  97. help
  98. Say Y here if you want to use OMAP Mailbox framework support for
  99. DSP, IVA1.0 and IVA2 in OMAP1/2/3.
  100. config OMAP_IOMMU
  101. tristate
  102. choice
  103. prompt "System timer"
  104. default OMAP_MPU_TIMER
  105. config OMAP_MPU_TIMER
  106. bool "Use mpu timer"
  107. help
  108. Select this option if you want to use the OMAP mpu timer. This
  109. timer provides more intra-tick resolution than the 32KHz timer,
  110. but consumes more power.
  111. config OMAP_32K_TIMER
  112. bool "Use 32KHz timer"
  113. depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX || ARCH_OMAP4
  114. help
  115. Select this option if you want to enable the OMAP 32KHz timer.
  116. This timer saves power compared to the OMAP_MPU_TIMER, and has
  117. support for no tick during idle. The 32KHz timer provides less
  118. intra-tick resolution than OMAP_MPU_TIMER. The 32KHz timer is
  119. currently only available for OMAP16XX, 24XX, 34XX and OMAP4.
  120. endchoice
  121. config OMAP_32K_TIMER_HZ
  122. int "Kernel internal timer frequency for 32KHz timer"
  123. range 32 1024
  124. depends on OMAP_32K_TIMER
  125. default "128"
  126. help
  127. Kernel internal timer frequency should be a divisor of 32768,
  128. such as 64 or 128.
  129. config OMAP_DM_TIMER
  130. bool "Use dual-mode timer"
  131. depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX || ARCH_OMAP4
  132. help
  133. Select this option if you want to use OMAP Dual-Mode timers.
  134. choice
  135. prompt "Low-level debug console UART"
  136. depends on ARCH_OMAP
  137. default OMAP_LL_DEBUG_UART1
  138. config OMAP_LL_DEBUG_UART1
  139. bool "UART1"
  140. config OMAP_LL_DEBUG_UART2
  141. bool "UART2"
  142. config OMAP_LL_DEBUG_UART3
  143. bool "UART3"
  144. endchoice
  145. config OMAP_SERIAL_WAKE
  146. bool "Enable wake-up events for serial ports"
  147. depends on ARCH_OMAP1 && OMAP_MUX
  148. default y
  149. help
  150. Select this option if you want to have your system wake up
  151. to data on the serial RX line. This allows you to wake the
  152. system from serial console.
  153. endmenu
  154. endif