Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125
  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_RESET_CLOCKS
  15. bool "Reset unused clocks during boot"
  16. depends on ARCH_OMAP
  17. help
  18. Say Y if you want to reset unused clocks during boot.
  19. This option saves power, but assumes all drivers are
  20. using the clock framework. Broken drivers that do not
  21. yet use clock framework may not work with this option.
  22. If you are booting from another operating system, you
  23. probably do not want this option enabled until your
  24. device drivers work properly.
  25. config OMAP_MUX
  26. bool "OMAP multiplexing support"
  27. depends on ARCH_OMAP
  28. default y
  29. help
  30. Pin multiplexing support for OMAP boards. If your bootloader
  31. sets the multiplexing correctly, say N. Otherwise, or if unsure,
  32. say Y.
  33. config OMAP_MUX_DEBUG
  34. bool "Multiplexing debug output"
  35. depends on OMAP_MUX
  36. help
  37. Makes the multiplexing functions print out a lot of debug info.
  38. This is useful if you want to find out the correct values of the
  39. multiplexing registers.
  40. config OMAP_MUX_WARNINGS
  41. bool "Warn about pins the bootloader didn't set up"
  42. depends on OMAP_MUX
  43. default y
  44. help
  45. Choose Y here to warn whenever driver initialization logic needs
  46. to change the pin multiplexing setup. When there are no warnings
  47. printed, it's safe to deselect OMAP_MUX for your product.
  48. choice
  49. prompt "System timer"
  50. default OMAP_MPU_TIMER
  51. config OMAP_MPU_TIMER
  52. bool "Use mpu timer"
  53. help
  54. Select this option if you want to use the OMAP mpu timer. This
  55. timer provides more intra-tick resolution than the 32KHz timer,
  56. but consumes more power.
  57. config OMAP_32K_TIMER
  58. bool "Use 32KHz timer"
  59. depends on ARCH_OMAP16XX || ARCH_OMAP24XX
  60. help
  61. Select this option if you want to enable the OMAP 32KHz timer.
  62. This timer saves power compared to the OMAP_MPU_TIMER, and has
  63. support for no tick during idle. The 32KHz timer provides less
  64. intra-tick resolution than OMAP_MPU_TIMER. The 32KHz timer is
  65. currently only available for OMAP16XX and 24XX.
  66. endchoice
  67. config OMAP_32K_TIMER_HZ
  68. int "Kernel internal timer frequency for 32KHz timer"
  69. range 32 1024
  70. depends on OMAP_32K_TIMER
  71. default "128"
  72. help
  73. Kernel internal timer frequency should be a divisor of 32768,
  74. such as 64 or 128.
  75. config OMAP_DM_TIMER
  76. bool "Use dual-mode timer"
  77. depends on ARCH_OMAP16XX || ARCH_OMAP24XX
  78. help
  79. Select this option if you want to use OMAP Dual-Mode timers.
  80. choice
  81. prompt "Low-level debug console UART"
  82. depends on ARCH_OMAP
  83. default OMAP_LL_DEBUG_UART1
  84. config OMAP_LL_DEBUG_UART1
  85. bool "UART1"
  86. config OMAP_LL_DEBUG_UART2
  87. bool "UART2"
  88. config OMAP_LL_DEBUG_UART3
  89. bool "UART3"
  90. endchoice
  91. config OMAP_SERIAL_WAKE
  92. bool "Enable wake-up events for serial ports"
  93. depends OMAP_MUX
  94. default y
  95. help
  96. Select this option if you want to have your system wake up
  97. to data on the serial RX line. This allows you to wake the
  98. system from serial console.
  99. endmenu
  100. endif