diff options
| author | Russell King <rmk@dyn-67.arm.linux.org.uk> | 2008-08-05 11:14:15 -0400 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2008-08-07 04:55:48 -0400 |
| commit | a09e64fbc0094e3073dbb09c3b4bfe4ab669244b (patch) | |
| tree | 69689f467179891b498bd7423fcf61925173db31 /Documentation/spi | |
| parent | a1b81a84fff05dbfef45b7012c26e1fee9973e5d (diff) | |
[ARM] Move include/asm-arm/arch-* to arch/arm/*/include/mach
This just leaves include/asm-arm/plat-* to deal with.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'Documentation/spi')
| -rw-r--r-- | Documentation/spi/pxa2xx | 4 | ||||
| -rw-r--r-- | Documentation/spi/spi-summary | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/spi/pxa2xx b/Documentation/spi/pxa2xx index f3853cc37bd..bbe8dee681a 100644 --- a/Documentation/spi/pxa2xx +++ b/Documentation/spi/pxa2xx | |||
| @@ -19,7 +19,7 @@ Declaring PXA2xx Master Controllers | |||
| 19 | ----------------------------------- | 19 | ----------------------------------- |
| 20 | Typically a SPI master is defined in the arch/.../mach-*/board-*.c as a | 20 | Typically a SPI master is defined in the arch/.../mach-*/board-*.c as a |
| 21 | "platform device". The master configuration is passed to the driver via a table | 21 | "platform device". The master configuration is passed to the driver via a table |
| 22 | found in include/asm-arm/arch-pxa/pxa2xx_spi.h: | 22 | found in arch/arm/mach-pxa/include/mach/pxa2xx_spi.h: |
| 23 | 23 | ||
| 24 | struct pxa2xx_spi_master { | 24 | struct pxa2xx_spi_master { |
| 25 | enum pxa_ssp_type ssp_type; | 25 | enum pxa_ssp_type ssp_type; |
| @@ -94,7 +94,7 @@ using the "spi_board_info" structure found in "linux/spi/spi.h". See | |||
| 94 | 94 | ||
| 95 | Each slave device attached to the PXA must provide slave specific configuration | 95 | Each slave device attached to the PXA must provide slave specific configuration |
| 96 | information via the structure "pxa2xx_spi_chip" found in | 96 | information via the structure "pxa2xx_spi_chip" found in |
| 97 | "include/asm-arm/arch-pxa/pxa2xx_spi.h". The pxa2xx_spi master controller driver | 97 | "arch/arm/mach-pxa/include/mach/pxa2xx_spi.h". The pxa2xx_spi master controller driver |
| 98 | will uses the configuration whenever the driver communicates with the slave | 98 | will uses the configuration whenever the driver communicates with the slave |
| 99 | device. | 99 | device. |
| 100 | 100 | ||
diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary index 6d5f18143c5..8bae2f018d3 100644 --- a/Documentation/spi/spi-summary +++ b/Documentation/spi/spi-summary | |||
| @@ -210,7 +210,7 @@ board should normally be set up and registered. | |||
| 210 | 210 | ||
| 211 | So for example arch/.../mach-*/board-*.c files might have code like: | 211 | So for example arch/.../mach-*/board-*.c files might have code like: |
| 212 | 212 | ||
| 213 | #include <asm/arch/spi.h> /* for mysoc_spi_data */ | 213 | #include <mach/spi.h> /* for mysoc_spi_data */ |
| 214 | 214 | ||
| 215 | /* if your mach-* infrastructure doesn't support kernels that can | 215 | /* if your mach-* infrastructure doesn't support kernels that can |
| 216 | * run on multiple boards, pdata wouldn't benefit from "__init". | 216 | * run on multiple boards, pdata wouldn't benefit from "__init". |
| @@ -227,7 +227,7 @@ So for example arch/.../mach-*/board-*.c files might have code like: | |||
| 227 | 227 | ||
| 228 | And SOC-specific utility code might look something like: | 228 | And SOC-specific utility code might look something like: |
| 229 | 229 | ||
| 230 | #include <asm/arch/spi.h> | 230 | #include <mach/spi.h> |
| 231 | 231 | ||
| 232 | static struct platform_device spi2 = { ... }; | 232 | static struct platform_device spi2 = { ... }; |
| 233 | 233 | ||
