On Tue, 14 Dec 2010, Paul Walmsley wrote: > On Tue, 7 Dec 2010, Paul Walmsley wrote: > > > The OMAP powerdomain code and data is all OMAP2+-specific. This seems > > unlikely to change any time soon. Move plat-omap/include/plat/powerdomain.h > > to mach-omap2/powerdomain.h. The primary point of doing this is to remove > > the temptation for unrelated upper-layer code to access powerdomain code > > and data directly. > > > > As part of this process, remove the references to powerdomain data from > > the GPIO "driver" and the OMAP PM no-op layer, both in plat-omap. > > > > Signed-off-by: Paul Walmsley <p...@pwsan.com> > > Cc: Kevin Hilman <khil...@deeprootsystems.com> > > This patch has been updated to get DSPBridge building again. The > DSPBridge should not be touching the powerdomain headers; this is > just a temporary workaround until the DSPBridge people fix the code.
An old version of this patch was inadvertently sent. The crucial diff (for review purposes anyway) from the previous patch is below. Nothing earthshattering. The updated integration tag that contains all of these updated changes is 'integration-2.6.38-20101214-013' available from git://git.pwsan.com/linux-integration - Paul diff --git a/drivers/staging/tidspbridge/core/_tiomap.h b/drivers/staging/tidspbridge/core/_tiomap.h index a3190e7..1159a50 100644 --- a/drivers/staging/tidspbridge/core/_tiomap.h +++ b/drivers/staging/tidspbridge/core/_tiomap.h @@ -24,7 +24,7 @@ * 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 <mach-omap2/powerdomain.h> #include <mach-omap2/clockdomain.h> /* * XXX These mach-omap2/ includes are wrong and should be removed. No -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
