overview.rst 8.3 KB

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