Kconfig 4.5 KB

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