Commit 2c2ff0a2 authored by Vignesh R's avatar Vignesh R Committed by Greg Kroah-Hartman

ARM: dts: am33xx-clocks: Fix ehrpwm tbclk data on am33xx

commit 6e22616e upstream.

ehrpwm tbclk is wrongly modelled as deriving from dpll_per_m2_ck.
The TRM says tbclk is derived from SYSCLKOUT. SYSCLKOUT nothing but the
functional clock of pwmss (l4ls_gclk).
Fix this by changing source of ehrpwmx_tbclk to l4ls_gclk.

Fixes: 9e100eba: ("Fix ehrpwm tbclk data")
Signed-off-by: default avatarVignesh R <vigneshr@ti.com>
Acked-by: default avatarTero Kristo <t-kristo@ti.com>
Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 0ad91e9c
...@@ -99,7 +99,7 @@ rng_fck: rng_fck { ...@@ -99,7 +99,7 @@ rng_fck: rng_fck {
ehrpwm0_tbclk: ehrpwm0_tbclk@44e10664 { ehrpwm0_tbclk: ehrpwm0_tbclk@44e10664 {
#clock-cells = <0>; #clock-cells = <0>;
compatible = "ti,gate-clock"; compatible = "ti,gate-clock";
clocks = <&dpll_per_m2_ck>; clocks = <&l4ls_gclk>;
ti,bit-shift = <0>; ti,bit-shift = <0>;
reg = <0x0664>; reg = <0x0664>;
}; };
...@@ -107,7 +107,7 @@ ehrpwm0_tbclk: ehrpwm0_tbclk@44e10664 { ...@@ -107,7 +107,7 @@ ehrpwm0_tbclk: ehrpwm0_tbclk@44e10664 {
ehrpwm1_tbclk: ehrpwm1_tbclk@44e10664 { ehrpwm1_tbclk: ehrpwm1_tbclk@44e10664 {
#clock-cells = <0>; #clock-cells = <0>;
compatible = "ti,gate-clock"; compatible = "ti,gate-clock";
clocks = <&dpll_per_m2_ck>; clocks = <&l4ls_gclk>;
ti,bit-shift = <1>; ti,bit-shift = <1>;
reg = <0x0664>; reg = <0x0664>;
}; };
...@@ -115,7 +115,7 @@ ehrpwm1_tbclk: ehrpwm1_tbclk@44e10664 { ...@@ -115,7 +115,7 @@ ehrpwm1_tbclk: ehrpwm1_tbclk@44e10664 {
ehrpwm2_tbclk: ehrpwm2_tbclk@44e10664 { ehrpwm2_tbclk: ehrpwm2_tbclk@44e10664 {
#clock-cells = <0>; #clock-cells = <0>;
compatible = "ti,gate-clock"; compatible = "ti,gate-clock";
clocks = <&dpll_per_m2_ck>; clocks = <&l4ls_gclk>;
ti,bit-shift = <2>; ti,bit-shift = <2>;
reg = <0x0664>; reg = <0x0664>;
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment