Overview.txt 8.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319
  1. S3C24XX ARM Linux Overview
  2. ==========================
  3. Introduction
  4. ------------
  5. The Samsung S3C24XX range of ARM9 System-on-Chip CPUs are supported
  6. by the 's3c2410' architecture of ARM Linux. Currently the S3C2410,
  7. S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443 and S3C2450 devices
  8. are supported.
  9. Support for the S3C2400 and S3C24A0 series was never completed and the
  10. corresponding code has been removed after a while. If someone wishes to
  11. revive this effort, partial support can be retrieved from earlier Linux
  12. versions.
  13. The S3C2416 and S3C2450 devices are very similar and S3C2450 support is
  14. included under the arch/arm/mach-s3c2416 directory. Note, whilst core
  15. support for these SoCs is in, work on some of the extra peripherals
  16. and extra interrupts is still ongoing.
  17. Configuration
  18. -------------
  19. A generic S3C2410 configuration is provided, and can be used as the
  20. default by `make s3c2410_defconfig`. This configuration has support
  21. for all the machines, and the commonly used features on them.
  22. Certain machines may have their own default configurations as well,
  23. please check the machine specific documentation.
  24. Layout
  25. ------
  26. The core support files are located in the platform code contained in
  27. arch/arm/plat-s3c24xx with headers in include/asm-arm/plat-s3c24xx.
  28. This directory should be kept to items shared between the platform
  29. code (arch/arm/plat-s3c24xx) and the arch/arm/mach-s3c24* code.
  30. Each cpu has a directory with the support files for it, and the
  31. machines that carry the device. For example S3C2410 is contained
  32. in arch/arm/mach-s3c2410 and S3C2440 in arch/arm/mach-s3c2440
  33. Register, kernel and platform data definitions are held in the
  34. arch/arm/mach-s3c2410 directory./include/mach
  35. arch/arm/plat-s3c24xx:
  36. Files in here are either common to all the s3c24xx family,
  37. or are common to only some of them with names to indicate this
  38. status. The files that are not common to all are generally named
  39. with the initial cpu they support in the series to ensure a short
  40. name without any possibility of confusion with newer devices.
  41. As an example, initially s3c244x would cover s3c2440 and s3c2442, but
  42. with the s3c2443 which does not share many of the same drivers in
  43. this directory, the name becomes invalid. We stick to s3c2440-<x>
  44. to indicate a driver that is s3c2440 and s3c2442 compatible.
  45. This does mean that to find the status of any given SoC, a number
  46. of directories may need to be searched.
  47. Machines
  48. --------
  49. The currently supported machines are as follows:
  50. Simtec Electronics EB2410ITX (BAST)
  51. A general purpose development board, see EB2410ITX.txt for further
  52. details
  53. Simtec Electronics IM2440D20 (Osiris)
  54. CPU Module from Simtec Electronics, with a S3C2440A CPU, nand flash
  55. and a PCMCIA controller.
  56. Samsung SMDK2410
  57. Samsung's own development board, geared for PDA work.
  58. Samsung/Aiji SMDK2412
  59. The S3C2412 version of the SMDK2440.
  60. Samsung/Aiji SMDK2413
  61. The S3C2412 version of the SMDK2440.
  62. Samsung/Meritech SMDK2440
  63. The S3C2440 compatible version of the SMDK2440, which has the
  64. option of an S3C2440 or S3C2442 CPU module.
  65. Thorcom VR1000
  66. Custom embedded board
  67. HP IPAQ 1940
  68. Handheld (IPAQ), available in several varieties
  69. HP iPAQ rx3715
  70. S3C2440 based IPAQ, with a number of variations depending on
  71. features shipped.
  72. Acer N30
  73. A S3C2410 based PDA from Acer. There is a Wiki page at
  74. http://handhelds.org/moin/moin.cgi/AcerN30Documentation .
  75. AML M5900
  76. American Microsystems' M5900
  77. Nex Vision Nexcoder
  78. Nex Vision Otom
  79. Two machines by Nex Vision
  80. Adding New Machines
  81. -------------------
  82. The architecture has been designed to support as many machines as can
  83. be configured for it in one kernel build, and any future additions
  84. should keep this in mind before altering items outside of their own
  85. machine files.
  86. Machine definitions should be kept in linux/arch/arm/mach-s3c2410,
  87. and there are a number of examples that can be looked at.
  88. Read the kernel patch submission policies as well as the
  89. Documentation/arm directory before submitting patches. The
  90. ARM kernel series is managed by Russell King, and has a patch system
  91. located at http://www.arm.linux.org.uk/developer/patches/
  92. as well as mailing lists that can be found from the same site.
  93. As a courtesy, please notify <ben-linux@fluff.org> of any new
  94. machines or other modifications.
  95. Any large scale modifications, or new drivers should be discussed
  96. on the ARM kernel mailing list (linux-arm-kernel) before being
  97. attempted. See http://www.arm.linux.org.uk/mailinglists/ for the
  98. mailing list information.
  99. I2C
  100. ---
  101. The hardware I2C core in the CPU is supported in single master
  102. mode, and can be configured via platform data.
  103. RTC
  104. ---
  105. Support for the onboard RTC unit, including alarm function.
  106. This has recently been upgraded to use the new RTC core,
  107. and the module has been renamed to rtc-s3c to fit in with
  108. the new rtc naming scheme.
  109. Watchdog
  110. --------
  111. The onchip watchdog is available via the standard watchdog
  112. interface.
  113. NAND
  114. ----
  115. The current kernels now have support for the s3c2410 NAND
  116. controller. If there are any problems the latest linux-mtd
  117. code can be found from http://www.linux-mtd.infradead.org/
  118. For more information see Documentation/arm/Samsung-S3C24XX/NAND.txt
  119. SD/MMC
  120. ------
  121. The SD/MMC hardware pre S3C2443 is supported in the current
  122. kernel, the driver is drivers/mmc/host/s3cmci.c and supports
  123. 1 and 4 bit SD or MMC cards.
  124. The SDIO behaviour of this driver has not been fully tested. There is no
  125. current support for hardware SDIO interrupts.
  126. Serial
  127. ------
  128. The s3c2410 serial driver provides support for the internal
  129. serial ports. These devices appear as /dev/ttySAC0 through 3.
  130. To create device nodes for these, use the following commands
  131. mknod ttySAC0 c 204 64
  132. mknod ttySAC1 c 204 65
  133. mknod ttySAC2 c 204 66
  134. GPIO
  135. ----
  136. The core contains support for manipulating the GPIO, see the
  137. documentation in GPIO.txt in the same directory as this file.
  138. Newer kernels carry GPIOLIB, and support is being moved towards
  139. this with some of the older support in line to be removed.
  140. As of v2.6.34, the move towards using gpiolib support is almost
  141. complete, and very little of the old calls are left.
  142. See Documentation/arm/Samsung-S3C24XX/GPIO.txt for the S3C24XX specific
  143. support and Documentation/arm/Samsung/GPIO.txt for the core Samsung
  144. implementation.
  145. Clock Management
  146. ----------------
  147. The core provides the interface defined in the header file
  148. include/asm-arm/hardware/clock.h, to allow control over the
  149. various clock units
  150. Suspend to RAM
  151. --------------
  152. For boards that provide support for suspend to RAM, the
  153. system can be placed into low power suspend.
  154. See Suspend.txt for more information.
  155. SPI
  156. ---
  157. SPI drivers are available for both the in-built hardware
  158. (although there is no DMA support yet) and a generic
  159. GPIO based solution.
  160. LEDs
  161. ----
  162. There is support for GPIO based LEDs via a platform driver
  163. in the LED subsystem.
  164. Platform Data
  165. -------------
  166. Whenever a device has platform specific data that is specified
  167. on a per-machine basis, care should be taken to ensure the
  168. following:
  169. 1) that default data is not left in the device to confuse the
  170. driver if a machine does not set it at startup
  171. 2) the data should (if possible) be marked as __initdata,
  172. to ensure that the data is thrown away if the machine is
  173. not the one currently in use.
  174. The best way of doing this is to make a function that
  175. kmalloc()s an area of memory, and copies the __initdata
  176. and then sets the relevant device's platform data. Making
  177. the function `__init` takes care of ensuring it is discarded
  178. with the rest of the initialisation code
  179. static __init void s3c24xx_xxx_set_platdata(struct xxx_data *pd)
  180. {
  181. struct s3c2410_xxx_mach_info *npd;
  182. npd = kmalloc(sizeof(struct s3c2410_xxx_mach_info), GFP_KERNEL);
  183. if (npd) {
  184. memcpy(npd, pd, sizeof(struct s3c2410_xxx_mach_info));
  185. s3c_device_xxx.dev.platform_data = npd;
  186. } else {
  187. printk(KERN_ERR "no memory for xxx platform data\n");
  188. }
  189. }
  190. Note, since the code is marked as __init, it should not be
  191. exported outside arch/arm/mach-s3c2410/, or exported to
  192. modules via EXPORT_SYMBOL() and related functions.
  193. Port Contributors
  194. -----------------
  195. Ben Dooks (BJD)
  196. Vincent Sanders
  197. Herbert Potzl
  198. Arnaud Patard (RTP)
  199. Roc Wu
  200. Klaus Fetscher
  201. Dimitry Andric
  202. Shannon Holland
  203. Guillaume Gourat (NexVision)
  204. Christer Weinigel (wingel) (Acer N30)
  205. Lucas Correia Villa Real (S3C2400 port)
  206. Document Author
  207. ---------------
  208. Ben Dooks, Copyright 2004-2006 Simtec Electronics