Documentation: Update paths of Samsung S3C machine files

Documentation references Samsung S3C24xx and S3C64xx machine files in
multiple places but the files were traveling around the kernel multiple
times.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Link: https://lore.kernel.org/r/20200911143343.498-1-krzk@kernel.org
This commit is contained in:
Krzysztof Kozlowski 2020-09-11 16:33:41 +02:00
parent 9484f2cb83
commit 0f12999e27
6 changed files with 15 additions and 24 deletions

View File

@ -2951,7 +2951,7 @@
mtdset= [ARM] mtdset= [ARM]
ARM/S3C2412 JIVE boot control ARM/S3C2412 JIVE boot control
See arch/arm/mach-s3c2412/mach-jive.c See arch/arm/mach-s3c/mach-jive.c
mtouchusb.raw_coordinates= mtouchusb.raw_coordinates=
[HW] Make the MicroTouch USB driver use raw coordinates [HW] Make the MicroTouch USB driver use raw coordinates

View File

@ -29,7 +29,7 @@ GPIOLIB
The following functions now either have a `s3c_` specific variant The following functions now either have a `s3c_` specific variant
or are merged into gpiolib. See the definitions in or are merged into gpiolib. See the definitions in
arch/arm/plat-samsung/include/plat/gpio-cfg.h: arch/arm/mach-s3c/gpio-cfg.h:
- s3c2410_gpio_setpin() gpio_set_value() or gpio_direction_output() - s3c2410_gpio_setpin() gpio_set_value() or gpio_direction_output()
- s3c2410_gpio_getpin() gpio_get_value() or gpio_direction_input() - s3c2410_gpio_getpin() gpio_get_value() or gpio_direction_input()
@ -86,7 +86,7 @@ between the calls.
Headers Headers
------- -------
See arch/arm/mach-s3c24xx/include/mach/regs-gpio.h for the list See arch/arm/mach-s3c/regs-gpio-s3c24xx.h for the list
of GPIO pins, and the configuration values for them. This of GPIO pins, and the configuration values for them. This
is included by using #include <mach/regs-gpio.h> is included by using #include <mach/regs-gpio.h>

View File

@ -18,7 +18,7 @@ Introduction
versions. versions.
The S3C2416 and S3C2450 devices are very similar and S3C2450 support is The S3C2416 and S3C2450 devices are very similar and S3C2450 support is
included under the arch/arm/mach-s3c2416 directory. Note, while core included under the arch/arm/mach-s3c directory. Note, while core
support for these SoCs is in, work on some of the extra peripherals support for these SoCs is in, work on some of the extra peripherals
and extra interrupts is still ongoing. and extra interrupts is still ongoing.
@ -37,19 +37,11 @@ Configuration
Layout Layout
------ ------
The core support files are located in the platform code contained in The core support files, register, kernel and paltform data are located in the
arch/arm/plat-s3c24xx with headers in include/asm-arm/plat-s3c24xx. platform code contained in arch/arm/mach-s3c with headers in
This directory should be kept to items shared between the platform arch/arm/mach-s3c/include
code (arch/arm/plat-s3c24xx) and the arch/arm/mach-s3c24* code.
Each cpu has a directory with the support files for it, and the arch/arm/mach-s3c:
machines that carry the device. For example S3C2410 is contained
in arch/arm/mach-s3c2410 and S3C2440 in arch/arm/mach-s3c2440
Register, kernel and platform data definitions are held in the
arch/arm/mach-s3c2410 directory./include/mach
arch/arm/plat-s3c24xx:
Files in here are either common to all the s3c24xx family, Files in here are either common to all the s3c24xx family,
or are common to only some of them with names to indicate this or are common to only some of them with names to indicate this
@ -134,7 +126,7 @@ Adding New Machines
should keep this in mind before altering items outside of their own should keep this in mind before altering items outside of their own
machine files. machine files.
Machine definitions should be kept in linux/arch/arm/mach-s3c2410, Machine definitions should be kept in arch/arm/mach-s3c,
and there are a number of examples that can be looked at. and there are a number of examples that can be looked at.
Read the kernel patch submission policies as well as the Read the kernel patch submission policies as well as the
@ -293,7 +285,7 @@ Platform Data
} }
Note, since the code is marked as __init, it should not be Note, since the code is marked as __init, it should not be
exported outside arch/arm/mach-s3c2410/, or exported to exported outside arch/arm/mach-s3c/, or exported to
modules via EXPORT_SYMBOL() and related functions. modules via EXPORT_SYMBOL() and related functions.

View File

@ -36,7 +36,7 @@ Board Support
------------- -------------
The driver attaches to a platform device, which will need to be The driver attaches to a platform device, which will need to be
added by the board specific support file in linux/arch/arm/mach-s3c2410, added by the board specific support file in arch/arm/mach-s3c,
such as mach-bast.c or mach-smdk2410.c such as mach-bast.c or mach-smdk2410.c
The platform device's platform_data field is only needed if the The platform device's platform_data field is only needed if the
@ -51,9 +51,9 @@ Board Support
Platform Data Platform Data
------------- -------------
See arch/arm/mach-s3c2410/include/mach/usb-control.h for the See include/linux/platform_data/usb-ohci-s3c2410.h for the
descriptions of the platform device data. An implementation descriptions of the platform device data. An implementation
can be found in linux/arch/arm/mach-s3c2410/usb-simtec.c . can be found in arch/arm/mach-s3c/simtec-usb.c .
The `struct s3c2410_hcd_info` contains a pair of functions The `struct s3c2410_hcd_info` contains a pair of functions
that get called to enable over-current detection, and to that get called to enable over-current detection, and to

View File

@ -37,5 +37,4 @@ implementation to configure pins as necessary.
The s3c_gpio_cfgpin() and s3c_gpio_setpull() provide the means for a The s3c_gpio_cfgpin() and s3c_gpio_setpull() provide the means for a
driver or machine to change gpio configuration. driver or machine to change gpio configuration.
See arch/arm/plat-samsung/include/plat/gpio-cfg.h for more information See arch/arm/mach-s3c/gpio-cfg.h for more information on these functions.
on these functions.

View File

@ -34,7 +34,7 @@ These resources should be specified in that order, as the ordering of the
two address regions is important (the driver expects these to be address two address regions is important (the driver expects these to be address
and then data). and then data).
An example from arch/arm/mach-s3c2410/mach-bast.c is:: An example from arch/arm/mach-s3c/mach-bast.c is::
static struct resource bast_dm9k_resource[] = { static struct resource bast_dm9k_resource[] = {
[0] = { [0] = {