Overview.txt 8.5 KB

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