ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds
authorArnd Bergmann <arnd@arndb.de>
Wed, 6 Dec 2017 13:17:17 +0000 (14:17 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 15 Mar 2018 09:54:22 +0000 (10:54 +0100)
commitc116baf79f0ecedd94be496be622ab6b65a243e7
treeb32b5e298034aa7c452fb7ef11893452a282fe7e
parent77fbdd1e2a0c316481313caa4246b87a95aa0f31
ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds

commit 863204cfdae98626a92535ac928ad79f4d6b74ff upstream.

In configurations without CONFIG_OMAP3 but with secure RAM support,
we now run into a link failure:

arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
omap-secure.c:(.text+0x130): undefined reference to `save_secure_ram_context'

The omap3_save_secure_ram() function is only called from the OMAP34xx
power management code, so we can simply hide that function in the
appropriate #ifdef.

Fixes: d09220a887f7 ("ARM: OMAP2+: Fix SRAM virt to phys translation for save_secure_ram_context")
Acked-by: Tony Lindgren <tony@atomide.com>
Tested-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/arm/mach-omap2/omap-secure.c