Kconfig 4.5 KB

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