summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2018-06-05 17:08:02 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2018-06-07 11:23:30 +0200
commit4108c6d049eea8acaafdf7842c16fdac0589c96c (patch)
tree4dbced5f98e6203cdb846129918c06dc77019b5a
parentd5c94e7a482e92ae5fe2f81b4fc148b517506e89 (diff)
downloadbarebox-4108c6d049eea8acaafdf7842c16fdac0589c96c.tar.gz
ARM: imx6sx: use correct clocks for GPT
This is a stop gap solution until the upstream DT is fixed. In Linux this isn't an issue as the driver prefers the "osc_per" clock, falling back to "per" and then doing different things based on the SoC type and if the input clock rate matches 3MHz. As this isn't really how the hardware works, but a fragile mix of the clock driver exposing a clock with a faked frequency and system knowledge in the GPT driver I prefer not to replicate this horrors in the Barebox driver, but instead just use the system clock source. Fixes: 2ebda864f837 (ARM: imx: clocksource: Use per clock for determining parent freq) Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--arch/arm/dts/imx6sx.dtsi4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm/dts/imx6sx.dtsi b/arch/arm/dts/imx6sx.dtsi
index 5a8ee46..5242419 100644
--- a/arch/arm/dts/imx6sx.dtsi
+++ b/arch/arm/dts/imx6sx.dtsi
@@ -10,3 +10,7 @@
pwm7 = &pwm8;
};
};
+
+&gpt {
+ clocks = <&clks IMX6SX_CLK_GPT_BUS>, <&clks IMX6SX_CLK_GPT_SERIAL>;
+};