Kconfig 4.5 KB

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