Overview.txt 6.2 KB

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