Overview.txt 6.2 KB

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