summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap1/include/mach/hardware.h
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2012-10-25 00:25:44 +0400
committerTony Lindgren <tony@atomide.com>2012-10-25 00:25:44 +0400
commit3e9a6321f9895eac9a3d241d3126e44021e7102b (patch)
treed674cf54e26837bee89095c211ffa362c8546f03 /arch/arm/mach-omap1/include/mach/hardware.h
parent54ec52b6dd3b0ba4bc4eb97e7e1b2534705b326c (diff)
parente4c060db2c13f10de09101afc564763f9fd0019a (diff)
downloadlinux-3e9a6321f9895eac9a3d241d3126e44021e7102b.tar.xz
Merge tag 'omap-for-v3.8/cleanup-headers-signed' into omap-for-v3.8/cleanup-headers-serial-take2
This is the first set of omap cleanup patches for v3.8 merge window to remove most of the remaining plat includes to get us closer to ARM common zImage support. To avoid a huge amount of trivial merge conflicts with includes, this branch is based on several small topic branches coordinated with the driver subsystem maintainers. These branches are based on v3.7-rc1 and can also be merged into the related driver subsystem branches as needed: omap-for-v3.8/cleanup-headers-prepare few trivial driver changes omap-for-v3.8/cleanup-headers-dma move of the DMA header omap-for-v3.8/cleanup-headers-gpmc GPMC and MTD changes omap-for-v3.8/cleanup-headers-mmc MMC related changes omap-for-v3.8/cleanup-headers-dss DSS related changes omap-for-v3.8/cleanup-headers-asoc ASoC related changes Note that for the dma-omap.h, it was decided that it should be is completed. For the related discussion, please see: https://patchwork.kernel.org/patch/1519591/# After these patches we still have a few plat headers remaining that will be handled in later pull requests.
Diffstat (limited to 'arch/arm/mach-omap1/include/mach/hardware.h')
-rw-r--r--arch/arm/mach-omap1/include/mach/hardware.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/mach-omap1/include/mach/hardware.h b/arch/arm/mach-omap1/include/mach/hardware.h
index 84248d250adb..f9989d38c464 100644
--- a/arch/arm/mach-omap1/include/mach/hardware.h
+++ b/arch/arm/mach-omap1/include/mach/hardware.h
@@ -39,7 +39,7 @@
#include <asm/sizes.h>
#ifndef __ASSEMBLER__
#include <asm/types.h>
-#include <plat/cpu.h>
+#include "../../mach-omap1/soc.h"
/*
* NOTE: Please use ioremap + __raw_read/write where possible instead of these
@@ -51,7 +51,7 @@ extern void omap_writeb(u8 v, u32 pa);
extern void omap_writew(u16 v, u32 pa);
extern void omap_writel(u32 v, u32 pa);
-#include <plat/tc.h>
+#include <mach/tc.h>
/* Almost all documentation for chip and board memory maps assumes
* BM is clear. Most devel boards have a switch to control booting