summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap2/clock2430_data.c
diff options
context:
space:
mode:
authorJon Hunter <jon-hunter@ti.com>2012-06-05 17:34:59 (GMT)
committerTony Lindgren <tony@atomide.com>2012-06-14 09:39:47 (GMT)
commit2b2d35230099613365ad6000f4d71086130b9e71 (patch)
tree6ac2f7db9822cb94949f6822ff327139d7c4f155 /arch/arm/mach-omap2/clock2430_data.c
parentbca4580845cbffb455d77783fc7e58a94b3904e0 (diff)
downloadlinux-fsl-qoriq-2b2d35230099613365ad6000f4d71086130b9e71.tar.xz
ARM: OMAP2+: Move dmtimer clock set function to dmtimer driver
OMAP1 uses an architecture specific function for setting the dmtimer clock source, where as the OMAP2+ devices use the clock framework. Eventually OMAP1 device should also use the clock framework and hence we should not any architecture specific functions. For now move the OMAP2+ function for configuring the clock source into the dmtimer driver. Therefore, we do no longer need to specify an architecture specific function for setting the clock source for OMAP2+ devices. This will simplify device tree migration of the dmtimers for OMAP2+ devices. From now on, only OMAP1 devices should specify an architecture specific function for setting the clock source via the platform data set_dmtimer_src() function pointer. Signed-off-by: Jon Hunter <jon-hunter@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/clock2430_data.c')
0 files changed, 0 insertions, 0 deletions