Overview.txt 6.7 KB

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