diff options
author | Tony Lindgren <tony@atomide.com> | 2020-05-07 09:59:31 -0700 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2020-05-19 09:38:04 -0700 |
commit | 036a3d42bb8f28ae3cdd7c9570135c243724fbd6 (patch) | |
tree | 2bbb6f24a8234a98e76a8b5f650582efb5f02c5f /arch/arm/boot/dts/omap3-beagle.dts | |
parent | 14b1925a721992d781f5e9d28db26b85174e3927 (diff) | |
download | lwn-036a3d42bb8f28ae3cdd7c9570135c243724fbd6.tar.gz lwn-036a3d42bb8f28ae3cdd7c9570135c243724fbd6.zip |
ARM: dts: Configure system timers for omap5 and dra7
We can now init system timers using the dmtimer and 32k counter
based on only devicetree data and drivers/clocksource timers.
Let's configure the clocksource and clockevent, and drop the old
unused platform data.
As we're just dropping platform data, and the early platform data
init is based on the custom ti,hwmods property, we want to drop
both the platform data and ti,hwmods property in a single patch.
Since the dmtimer can use both 32k clock and system clock as the
source, let's also configure the SoC specific default values. The
board specific dts files can reconfigure these with assigned-clocks
and assigned-clock-parents as needed.
Note that similar to omap_init_time_of(), we now need to call
omap_clk_init() also from omap5_realtime_timer_init().
Cc: devicetree@vger.kernel.org
Cc: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Keerthy <j-keerthy@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Rob Herring <robh@kernel.org>
Cc: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/omap3-beagle.dts')
0 files changed, 0 insertions, 0 deletions