Overview.txt 8.0 KB

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