diff options
| author | Kevin Hilman | 2010-03-10 18:16:31 +0100 |
|---|---|---|
| committer | Tony Lindgren | 2010-03-12 00:55:43 +0100 |
| commit | aa4b1f6e83aaf20997edc4c10e03baf834343e5a (patch) | |
| tree | 55fd98afbd265d7850d8f4c408415abf25fa97d7 /security/selinux/include/objsec.h | |
| parent | OMAP2: cpu_is_omap2*: fix compile-time removal of unused code (diff) | |
| download | kernel-qcow2-linux-aa4b1f6e83aaf20997edc4c10e03baf834343e5a.tar.gz kernel-qcow2-linux-aa4b1f6e83aaf20997edc4c10e03baf834343e5a.tar.xz kernel-qcow2-linux-aa4b1f6e83aaf20997edc4c10e03baf834343e5a.zip | |
OMAP4: fix temporary hacks that break multi-omap PM
When building for multi-omap, and OMAP4 is enabled, CONFIG_ARCH_OMAP4
will be true and prevent included code from building/running for
OMAP2/3 as well.
This problem exists in io.c where some hwmod/PM/SDRC init code is
prevented from running even on OMAP2/3 when OMAP4 is included in a
multi-OMAP build.
A quick glance suggests that this #ifndef is no longer needed in most
of the cases. In the remaining cases, the function is wrapped with
"if (cpu_is_omap24xx() || cpu_is_omap34xx())" which will be optimized
out for OMAP4-only builds.
Note that this is only a short-term fix. Longer-term, OMAP4
needs to create init functions for SDRC and hwmod late-init.
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'security/selinux/include/objsec.h')
0 files changed, 0 insertions, 0 deletions