summaryrefslogtreecommitdiff
path: root/arch/arm/vfp
diff options
context:
space:
mode:
authorJon Hunter <jon-hunter@ti.com>2012-06-05 17:35:00 (GMT)
committerTony Lindgren <tony@atomide.com>2012-06-14 09:39:47 (GMT)
commitc59b537d87068be8c357a0150f6172a2dc8cdf82 (patch)
treeffcc6f3cf259feee766dae4f7579bf457ccc37f2 /arch/arm/vfp
parent2b2d35230099613365ad6000f4d71086130b9e71 (diff)
downloadlinux-c59b537d87068be8c357a0150f6172a2dc8cdf82.tar.xz
ARM: OMAP2+: Simplify dmtimer clock aliases
The OMAP dmtimer driver allows you to dynamically configure the functional clock that drives the timer logic. The dmtimer driver uses the device name and a "con-id" string to search for the appropriate functional clock. Currently, we define a clock alias for each functional clock source each timer supports. Some functional clock sources are common to all of the timers on a device and so for these clock sources we can use a single alias with a unique con-id string. The possible functional clock sources for an OMAP device are a 32kHz clock, a system (MHz range) clock and (for OMAP2 only) an external clock. By defining a unique con-id name for each of these (timer_32k_ck, timer_sys_ck and timer_ext_ck) we can eliminate a lot of the clock aliases for timers. This reduces code, speeds-up searches and clock initialisation time. Signed-off-by: Jon Hunter <jon-hunter@ti.com> Acked-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/vfp')
0 files changed, 0 insertions, 0 deletions