diff options
author | Jon Hunter <jon-hunter@ti.com> | 2012-11-27 11:22:39 -0600 |
---|---|---|
committer | Jon Hunter <jon-hunter@ti.com> | 2012-12-14 10:14:16 -0600 |
commit | 34cceb7464f2db0da4da900afa82a210f4470b89 (patch) | |
tree | 30e979221b4d99f19b9d7b078290b67446cf1d03 /arch/arm/mach-omap2/timer.c | |
parent | 698d601224824bc1a5bf17f3d86be902e2aabff0 (diff) | |
download | linux-stable-34cceb7464f2db0da4da900afa82a210f4470b89.tar.gz linux-stable-34cceb7464f2db0da4da900afa82a210f4470b89.tar.bz2 linux-stable-34cceb7464f2db0da4da900afa82a210f4470b89.zip |
ARM: OMAP2+: Fix realtime_counter_init warning in timer.c
In commit fa6d79d (ARM: OMAP: Add initialisation for the real-time
counter), the function realtime_counter_init() was added. However, if
the kernel configuration option CONFIG_SOC_OMAP5 is not selected then
the following compiler warning is observed.
CC arch/arm/mach-omap2/timer.o
arch/arm/mach-omap2/timer.c:489:20: warning: ‘realtime_counter_init’
defined but not used [-Wunused-function]
Commit fa6d79d also introduced the kernel configuration option
CONFIG_SOC_HAS_REALTIME_COUNTER. If this option is not selected then the
a stub function for realtime_counter_init() is defined.
For non-OMAP5 devices, there is no realtime counter and so
realtime_counter_init() function and stub function are not used for
these devices. Therefore, fix this warning by only allowing the kernel
configuration option CONFIG_SOC_HAS_REALTIME_COUNTER to be enabled for
OMAP5 devices.
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Reported-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Jon Hunter <jon-hunter@ti.com>
Acked-by Santosh Shilimkar <santosh.shilimkar@ti.com>
Diffstat (limited to 'arch/arm/mach-omap2/timer.c')
0 files changed, 0 insertions, 0 deletions