Kconfig 4.8 KB

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