Kconfig 4.4 KB

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