summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/omap_hwmod.c
diff options
context:
space:
mode:
authorGrygorii Strashko <grygorii.strashko@ti.com>2016-12-05 04:57:44 +0100
committerTony Lindgren <tony@atomide.com>2016-12-27 18:38:04 +0100
commitf86a2c875fd146d9b82c8fdd86d31084507bcf4c (patch)
treebf64062ee6c23761c5cc910b9d6cc2db60e30f9d /arch/arm/mach-omap2/omap_hwmod.c
parentARM: dts: omap3: Add DTS for Logic PD SOM-LV 37xx Dev Kit (diff)
downloadlinux-f86a2c875fd146d9b82c8fdd86d31084507bcf4c.tar.xz
linux-f86a2c875fd146d9b82c8fdd86d31084507bcf4c.zip
ARM: omap2+: am437x: rollback to use omap3_gptimer_timer_init()
The commit 55ee7017ee31 ("arm: omap2: board-generic: use omap4_local_timer_init for AM437x") unintentionally changes the clocksource devices for AM437x from OMAP GP Timer to SyncTimer32K. Unfortunately, the SyncTimer32K is starving from frequency deviation as mentioned in commit 5b5c01359152 ("ARM: OMAP2+: AM43x: Use gptimer as clocksource") and, as reported by Franklin [1], even its monotonic nature is under question (most probably there is a HW issue, but it's still under investigation). Taking into account above facts It's reasonable to rollback to the use of omap3_gptimer_timer_init(). [1] http://www.spinics.net/lists/linux-omap/msg127425.html Fixes: 55ee7017ee31 ("arm: omap2: board-generic: use omap4_local_timer_init for AM437x") Reported-by: Cooper Jr., Franklin <fcooper@ti.com> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by: Keerthy <j-keerthy@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/omap_hwmod.c')
0 files changed, 0 insertions, 0 deletions