Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | if ARCH_S3C2410 |
| 2 | |
| 3 | menu "S3C24XX Implementations" |
| 4 | |
| 5 | config ARCH_BAST |
| 6 | bool "Simtec Electronics BAST (EB2410ITX)" |
| 7 | select CPU_S3C2410 |
| 8 | help |
| 9 | Say Y here if you are using the Simtec Electronics EB2410ITX |
| 10 | development board (also known as BAST) |
| 11 | |
| 12 | Product page: <http://www.simtec.co.uk/products/EB2410ITX/>. |
| 13 | |
| 14 | config ARCH_H1940 |
| 15 | bool "IPAQ H1940" |
| 16 | select CPU_S3C2410 |
| 17 | help |
| 18 | Say Y here if you are using the HP IPAQ H1940 |
| 19 | |
| 20 | <http://www.handhelds.org/projects/h1940.html>. |
| 21 | |
| 22 | config MACH_N30 |
| 23 | bool "Acer N30" |
| 24 | select CPU_S3C2410 |
| 25 | help |
| 26 | Say Y here if you are using the Acer N30 |
| 27 | |
| 28 | <http://zoo.weinigel.se/n30>. |
| 29 | |
| 30 | config ARCH_SMDK2410 |
| 31 | bool "SMDK2410/A9M2410" |
| 32 | select CPU_S3C2410 |
| 33 | help |
| 34 | Say Y here if you are using the SMDK2410 or the derived module A9M2410 |
| 35 | <http://www.fsforth.de> |
| 36 | |
| 37 | config ARCH_S3C2440 |
| 38 | bool "SMDK2440" |
| 39 | select CPU_S3C2440 |
| 40 | help |
| 41 | Say Y here if you are using the SMDK2440. |
| 42 | |
| 43 | config MACH_VR1000 |
| 44 | bool "Thorcom VR1000" |
| 45 | select CPU_S3C2410 |
| 46 | help |
| 47 | Say Y here if you are using the Thorcom VR1000 board. |
| 48 | |
| 49 | This linux port is currently being maintained by Simtec, on behalf |
| 50 | of Thorcom. Any queries, please contact Thorcom first. |
| 51 | |
| 52 | config MACH_RX3715 |
| 53 | bool "HP iPAQ rx3715" |
| 54 | select CPU_S3C2440 |
| 55 | help |
| 56 | Say Y here if you are using the HP iPAQ rx3715. |
| 57 | |
| 58 | See <http://www.handhelds.org/projects/rx3715.html> for more |
| 59 | information on this project |
| 60 | |
| 61 | config MACH_OTOM |
| 62 | bool "NexVision OTOM Board" |
| 63 | select CPU_S3C2410 |
| 64 | help |
| 65 | Say Y here if you are using the Nex Vision OTOM board |
| 66 | |
| 67 | config MACH_NEXCODER_2440 |
| 68 | bool "NexVision NEXCODER 2440 Light Board" |
| 69 | select CPU_S3C2440 |
| 70 | help |
| 71 | Say Y here if you are using the Nex Vision NEXCODER 2440 Light Board |
| 72 | |
| 73 | endmenu |
| 74 | |
| 75 | config CPU_S3C2410 |
| 76 | bool |
| 77 | depends on ARCH_S3C2410 |
| 78 | help |
| 79 | Support for S3C2410 and S3C2410A family from the S3C24XX line |
| 80 | of Samsung Mobile CPUs. |
| 81 | |
| 82 | config CPU_S3C2440 |
| 83 | bool |
| 84 | depends on ARCH_S3C2410 |
| 85 | help |
| 86 | Support for S3C2440 Samsung Mobile CPU based systems. |
| 87 | |
| 88 | comment "S3C2410 Boot" |
| 89 | |
| 90 | config S3C2410_BOOT_WATCHDOG |
| 91 | bool "S3C2410 Initialisation watchdog" |
| 92 | depends on ARCH_S3C2410 && S3C2410_WATCHDOG |
| 93 | help |
| 94 | Say y to enable the watchdog during the kernel decompression |
| 95 | stage. If the kernel fails to uncompress, then the watchdog |
| 96 | will trigger a reset and the system should restart. |
| 97 | |
| 98 | Although this uses the same hardware unit as the kernel watchdog |
| 99 | driver, it is not a replacement for it. If you use this option, |
| 100 | you will have to use the watchdg driver to either stop the timeout |
| 101 | or restart it. If you do not, then your kernel will reboot after |
| 102 | startup. |
| 103 | |
| 104 | The driver uses a fixed timeout value, so the exact time till the |
| 105 | system resets depends on the value of PCLK. The timeout on an |
| 106 | 200MHz s3c2410 should be about 30 seconds. |
| 107 | |
| 108 | comment "S3C2410 Setup" |
| 109 | |
| 110 | config S3C2410_DMA |
| 111 | bool "S3C2410 DMA support" |
| 112 | depends on ARCH_S3C2410 |
| 113 | help |
| 114 | S3C2410 DMA support. This is needed for drivers like sound which |
| 115 | use the S3C2410's DMA system to move data to and from the |
| 116 | peripheral blocks. |
| 117 | |
| 118 | config S3C2410_DMA_DEBUG |
| 119 | bool "S3C2410 DMA support debug" |
| 120 | depends on ARCH_S3C2410 && S3C2410_DMA |
| 121 | help |
| 122 | Enable debugging output for the DMA code. This option sends info |
| 123 | to the kernel log, at priority KERN_DEBUG. |
| 124 | |
| 125 | Note, it is easy to create and fill the log buffer in a small |
| 126 | amount of time, as well as using an significant percentage of |
| 127 | the CPU time doing so. |
| 128 | |
| 129 | |
| 130 | config S3C2410_PM_DEBUG |
| 131 | bool "S3C2410 PM Suspend debug" |
| 132 | depends on ARCH_S3C2410 && PM |
| 133 | help |
| 134 | Say Y here if you want verbose debugging from the PM Suspend and |
| 135 | Resume code. See `Documentation/arm/Samsing-S3C24XX/Suspend.txt` |
| 136 | for more information. |
| 137 | |
| 138 | config S3C2410_PM_CHECK |
| 139 | bool "S3C2410 PM Suspend Memory CRC" |
| 140 | depends on ARCH_S3C2410 && PM && CRC32 |
| 141 | help |
| 142 | Enable the PM code's memory area checksum over sleep. This option |
| 143 | will generate CRCs of all blocks of memory, and store them before |
| 144 | going to sleep. The blocks are then checked on resume for any |
| 145 | errors. |
| 146 | |
| 147 | config S3C2410_PM_CHECK_CHUNKSIZE |
| 148 | int "S3C2410 PM Suspend CRC Chunksize (KiB)" |
| 149 | depends on ARCH_S3C2410 && PM && S3C2410_PM_CHECK |
| 150 | default 64 |
| 151 | help |
| 152 | Set the chunksize in Kilobytes of the CRC for checking memory |
| 153 | corruption over suspend and resume. A smaller value will mean that |
| 154 | the CRC data block will take more memory, but wil identify any |
| 155 | faults with better precision. |
| 156 | |
Ben Dooks | f705b1a | 2005-06-29 11:09:15 +0100 | [diff] [blame^] | 157 | config PM_SIMTEC |
| 158 | bool |
| 159 | depends on PM && (ARCH_BAST || MACH_VR1000) |
| 160 | default y |
| 161 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 162 | config S3C2410_LOWLEVEL_UART_PORT |
| 163 | int "S3C2410 UART to use for low-level messages" |
| 164 | default 0 |
| 165 | help |
| 166 | Choice of which UART port to use for the low-level messages, |
| 167 | such as the `Uncompressing...` at start time. The value of |
| 168 | this configuration should be between zero and two. The port |
| 169 | must have been initialised by the boot-loader before use. |
| 170 | |
| 171 | Note, this does not affect the port used by the debug messages, |
| 172 | which is a separate configuration. |
| 173 | |
| 174 | endif |