summaryrefslogtreecommitdiffstats
path: root/arch/h8300
diff options
context:
space:
mode:
authorGrygorii Strashko <grygorii.strashko@ti.com>2015-12-14 21:34:05 +0100
committerTony Lindgren <tony@atomide.com>2015-12-17 19:53:28 +0100
commit0b3e6fca4d1af4aa150d32506220f4241323a00c (patch)
tree4595639d6351eb09d49c578b0baf6dfe84b8f0ef /arch/h8300
parentARM: dts: am4372: fix clock source for arm twd and global timers (diff)
downloadlinux-0b3e6fca4d1af4aa150d32506220f4241323a00c.tar.xz
linux-0b3e6fca4d1af4aa150d32506220f4241323a00c.zip
ARM: OMAP2+: am43xx: enable GENERIC_CLOCKEVENTS_BROADCAST
System will misbehave in the following case: - AM43XX only build (UP); - CONFIG_CPU_IDLE=y - ARM TWD timer enabled and selected as clockevent device. In the above case, It's expected that broadcast timer will be used as backup timer when CPUIdle will put MPU in low power states where ARM TWD will stop and lose its context. But, the CONFIG_SMP might not be selected when kernel is built for AM43XX SoC only and, as result, GENERIC_CLOCKEVENTS_BROADCAST option will not be selected also. This will break CPUIdle and System will stuck in low power states. Hence, fix it by selecting GENERIC_CLOCKEVENTS_BROADCAST option for AM43XX SoCs always and add empty tick_broadcast() function implementation - no need to send any IPI on UP. After this change timer1 will be selected as broadcast timer the same way as for SMP, and CPUIdle will work properly. Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/h8300')
0 files changed, 0 insertions, 0 deletions