diff options
author | Paul Walmsley <paul@pwsan.com> | 2010-12-22 04:05:15 (GMT) |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2010-12-22 04:05:15 (GMT) |
commit | 1540f214065982e6cbc6b8da1fe65a15e358f7c5 (patch) | |
tree | 8a6c11fd7d07dd027ec14e5fe3403d2aaf0f02b0 /drivers/staging | |
parent | 55ae35073b1c76f24c3736cf797c40d9932b19aa (diff) | |
download | linux-fsl-qoriq-1540f214065982e6cbc6b8da1fe65a15e358f7c5.tar.xz |
OMAP2+: clockdomain: move header file from plat-omap to mach-omap2
The OMAP clockdomain code and data is all OMAP2+-specific. This seems
unlikely to change any time soon. Move plat-omap/include/plat/clockdomain.h
to mach-omap2/clockdomain.h. The primary point of doing this is to remove
the temptation for unrelated upper-layer code to access clockdomain code
and data directly.
DSPBridge also uses the clockdomain headers for some reason, so,
modify it also. The DSPBridge code should not be including the
clockdomain headers; these should be removed.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>
Tested-by: Rajendra Nayak <rnayak@ti.com>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Diffstat (limited to 'drivers/staging')
-rw-r--r-- | drivers/staging/tidspbridge/core/_tiomap.h | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/drivers/staging/tidspbridge/core/_tiomap.h b/drivers/staging/tidspbridge/core/_tiomap.h index 7fac488..a3190e7 100644 --- a/drivers/staging/tidspbridge/core/_tiomap.h +++ b/drivers/staging/tidspbridge/core/_tiomap.h @@ -19,8 +19,13 @@ #ifndef _TIOMAP_ #define _TIOMAP_ +/* + * XXX These powerdomain.h/clockdomain.h includes are wrong and should + * be removed. No driver should call pwrdm_* or clkdm_* functions + * directly; they should rely on OMAP core code to do this. + */ #include <plat/powerdomain.h> -#include <plat/clockdomain.h> +#include <mach-omap2/clockdomain.h> /* * XXX These mach-omap2/ includes are wrong and should be removed. No * driver should read or write to PRM/CM registers directly; they |