Commit 61b7f892 authored by Arnd Bergmann's avatar Arnd Bergmann
Browse files

ARM: s3c: remove all s3c24xx support



The platform was deprecated in commit 6a5e69c7 ("ARM: s3c: mark
as deprecated and schedule removal") and can be removed. This includes
all files that are exclusively for s3c24xx and not shared with s3c64xx,
as well as the glue logic in Kconfig and the maintainer file entries.

Cc: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: Ben Dooks <ben-linux@fluff.org>
Cc: Christer Weinigel <christer@weinigel.se>
Cc: Guillaume GOURAT <guillaume.gourat@nexvision.tv>
Cc: Heiko Stuebner <heiko@sntech.de>
Cc: Simtec Linux Team <linux@simtec.co.uk>
Cc: openmoko-kernel@lists.openmoko.org
Acked-by: default avatarHeiko Stuebner <heiko@sntech.de>
Acked-by: default avatarKrzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
parent 1027b4df
Loading
Loading
Loading
Loading
+0 −1
Original line number Diff line number Diff line
@@ -64,7 +64,6 @@ SoC-specific documents
   sunxi

   samsung/index
   samsung-s3c24xx/index

   sunxi/clocks

+0 −77
Original line number Diff line number Diff line
.. SPDX-License-Identifier: GPL-2.0-only

=======================
S3C24XX CPUfreq support
=======================

Introduction
------------

 The S3C24XX series support a number of power saving systems, such as
 the ability to change the core, memory and peripheral operating
 frequencies. The core control is exported via the CPUFreq driver
 which has a number of different manual or automatic controls over the
 rate the core is running at.

 There are two forms of the driver depending on the specific CPU and
 how the clocks are arranged. The first implementation used as single
 PLL to feed the ARM, memory and peripherals via a series of dividers
 and muxes and this is the implementation that is documented here. A
 newer version where there is a separate PLL and clock divider for the
 ARM core is available as a separate driver.


Layout
------

 The code core manages the CPU specific drivers, any data that they
 need to register and the interface to the generic drivers/cpufreq
 system. Each CPU registers a driver to control the PLL, clock dividers
 and anything else associated with it. Any board that wants to use this
 framework needs to supply at least basic details of what is required.

 The core registers with drivers/cpufreq at init time if all the data
 necessary has been supplied.


CPU support
-----------

 The support for each CPU depends on the facilities provided by the
 SoC and the driver as each device has different PLL and clock chains
 associated with it.


Slow Mode
---------

 The SLOW mode where the PLL is turned off altogether and the
 system is fed by the external crystal input is currently not
 supported.


sysfs
-----

 The core code exports extra information via sysfs in the directory
 devices/system/cpu/cpu0/arch-freq.


Board Support
-------------

 Each board that wants to use the cpufreq code must register some basic
 information with the core driver to provide information about what the
 board requires and any restrictions being placed on it.

 The board needs to supply information about whether it needs the IO bank
 timings changing, any maximum frequency limits and information about the
 SDRAM refresh rate.




Document Author
---------------

Ben Dooks, Copyright 2009 Simtec Electronics
+0 −59
Original line number Diff line number Diff line
===================================
Simtec Electronics EB2410ITX (BAST)
===================================

	http://www.simtec.co.uk/products/EB2410ITX/

Introduction
------------

  The EB2410ITX is a S3C2410 based development board with a variety of
  peripherals and expansion connectors. This board is also known by
  the shortened name of Bast.


Configuration
-------------

  To set the default configuration, use `make bast_defconfig` which
  supports the commonly used features of this board.


Support
-------

  Official support information can be found on the Simtec Electronics
  website, at the product page http://www.simtec.co.uk/products/EB2410ITX/

  Useful links:

    - Resources Page http://www.simtec.co.uk/products/EB2410ITX/resources.html

    - Board FAQ at http://www.simtec.co.uk/products/EB2410ITX/faq.html

    - Bootloader info http://www.simtec.co.uk/products/SWABLE/resources.html
      and FAQ http://www.simtec.co.uk/products/SWABLE/faq.html


MTD
---

  The NAND and NOR support has been merged from the linux-mtd project.
  Any problems, see http://www.linux-mtd.infradead.org/ for more
  information or up-to-date versions of linux-mtd.


IDE
---

  Both onboard IDE ports are supported, however there is no support for
  changing speed of devices, PIO Mode 4 capable drives should be used.


Maintainers
-----------

  This board is maintained by Simtec Electronics.


Copyright 2004 Ben Dooks, Simtec Electronics
+0 −172
Original line number Diff line number Diff line
====================
S3C24XX GPIO Control
====================

Introduction
------------

  The s3c2410 kernel provides an interface to configure and
  manipulate the state of the GPIO pins, and find out other
  information about them.

  There are a number of conditions attached to the configuration
  of the s3c2410 GPIO system, please read the Samsung provided
  data-sheet/users manual to find out the complete list.

  See Documentation/arm/samsung/gpio.rst for the core implementation.


GPIOLIB
-------

  With the event of the GPIOLIB in drivers/gpio, support for some
  of the GPIO functions such as reading and writing a pin will
  be removed in favour of this common access method.

  Once all the extant drivers have been converted, the functions
  listed below will be removed (they may be marked as __deprecated
  in the near future).

  The following functions now either have a `s3c_` specific variant
  or are merged into gpiolib. See the definitions in
  arch/arm/mach-s3c/gpio-cfg.h:

  - s3c2410_gpio_setpin()	gpio_set_value() or gpio_direction_output()
  - s3c2410_gpio_getpin()	gpio_get_value() or gpio_direction_input()
  - s3c2410_gpio_getirq()	gpio_to_irq()
  - s3c2410_gpio_cfgpin()	s3c_gpio_cfgpin()
  - s3c2410_gpio_getcfg()	s3c_gpio_getcfg()
  - s3c2410_gpio_pullup()	s3c_gpio_setpull()


GPIOLIB conversion
------------------

If you need to convert your board or driver to use gpiolib from the phased
out s3c2410 API, then here are some notes on the process.

1) If your board is exclusively using an GPIO, say to control peripheral
   power, then it will require to claim the gpio with gpio_request() before
   it can use it.

   It is recommended to check the return value, with at least WARN_ON()
   during initialisation.

2) The s3c2410_gpio_cfgpin() can be directly replaced with s3c_gpio_cfgpin()
   as they have the same arguments, and can either take the pin specific
   values, or the more generic special-function-number arguments.

3) s3c2410_gpio_pullup() changes have the problem that while the
   s3c2410_gpio_pullup(x, 1) can be easily translated to the
   s3c_gpio_setpull(x, S3C_GPIO_PULL_NONE), the s3c2410_gpio_pullup(x, 0)
   are not so easy.

   The s3c2410_gpio_pullup(x, 0) case enables the pull-up (or in the case
   of some of the devices, a pull-down) and as such the new API distinguishes
   between the UP and DOWN case. There is currently no 'just turn on' setting
   which may be required if this becomes a problem.

4) s3c2410_gpio_setpin() can be replaced by gpio_set_value(), the old call
   does not implicitly configure the relevant gpio to output. The gpio
   direction should be changed before using gpio_set_value().

5) s3c2410_gpio_getpin() is replaceable by gpio_get_value() if the pin
   has been set to input. It is currently unknown what the behaviour is
   when using gpio_get_value() on an output pin (s3c2410_gpio_getpin
   would return the value the pin is supposed to be outputting).

6) s3c2410_gpio_getirq() should be directly replaceable with the
   gpio_to_irq() call.

The s3c2410_gpio and `gpio_` calls have always operated on the same gpio
numberspace, so there is no problem with converting the gpio numbering
between the calls.


Headers
-------

  See arch/arm/mach-s3c/regs-gpio-s3c24xx.h for the list
  of GPIO pins, and the configuration values for them. This
  is included by using #include <mach/regs-gpio.h>


PIN Numbers
-----------

  Each pin has an unique number associated with it in regs-gpio.h,
  e.g. S3C2410_GPA(0) or S3C2410_GPF(1). These defines are used to tell
  the GPIO functions which pin is to be used.

  With the conversion to gpiolib, there is no longer a direct conversion
  from gpio pin number to register base address as in earlier kernels. This
  is due to the number space required for newer SoCs where the later
  GPIOs are not contiguous.


Configuring a pin
-----------------

  The following function allows the configuration of a given pin to
  be changed.

    void s3c_gpio_cfgpin(unsigned int pin, unsigned int function);

  e.g.:

     s3c_gpio_cfgpin(S3C2410_GPA(0), S3C_GPIO_SFN(1));
     s3c_gpio_cfgpin(S3C2410_GPE(8), S3C_GPIO_SFN(2));

   which would turn GPA(0) into the lowest Address line A0, and set
   GPE(8) to be connected to the SDIO/MMC controller's SDDAT1 line.


Reading the current configuration
---------------------------------

  The current configuration of a pin can be read by using standard
  gpiolib function:

  s3c_gpio_getcfg(unsigned int pin);

  The return value will be from the same set of values which can be
  passed to s3c_gpio_cfgpin().


Configuring a pull-up resistor
------------------------------

  A large proportion of the GPIO pins on the S3C2410 can have weak
  pull-up resistors enabled. This can be configured by the following
  function:

    void s3c_gpio_setpull(unsigned int pin, unsigned int to);

  Where the to value is S3C_GPIO_PULL_NONE to set the pull-up off,
  and S3C_GPIO_PULL_UP to enable the specified pull-up. Any other
  values are currently undefined.


Getting and setting the state of a PIN
--------------------------------------

  These calls are now implemented by the relevant gpiolib calls, convert
  your board or driver to use gpiolib.


Getting the IRQ number associated with a PIN
--------------------------------------------

  A standard gpiolib function can map the given pin number to an IRQ
  number to pass to the IRQ system.

   int gpio_to_irq(unsigned int pin);

  Note, not all pins have an IRQ.


Author
-------

Ben Dooks, 03 October 2004
Copyright 2004 Ben Dooks, Simtec Electronics
+0 −41
Original line number Diff line number Diff line
=============
HP IPAQ H1940
=============

http://www.handhelds.org/projects/h1940.html

Introduction
------------

  The HP H1940 is a S3C2410 based handheld device, with
  bluetooth connectivity.


Support
-------

  A variety of information is available

  handhelds.org project page:

    http://www.handhelds.org/projects/h1940.html

  handhelds.org wiki page:

    http://handhelds.org/moin/moin.cgi/HpIpaqH1940

  Herbert Pötzl pages:

    http://vserver.13thfloor.at/H1940/


Maintainers
-----------

  This project is being maintained and developed by a variety
  of people, including Ben Dooks, Arnaud Patard, and Herbert Pötzl.

  Thanks to the many others who have also provided support.


(c) 2005 Ben Dooks
Loading