Kconfig 4.5 KB

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