Skip to contentSkip to conversation

move ieee5000 ti,gate-clock to a ti,clkctrl?

am33xx-clocks.dtsi Oskar Holmlund 2 participants 2 messages Dec 30, 2020 – Jan 18, 2021

lore
Share & tools
lore
#0 lore raw

Hi,

Is it possible to move
&prcm_clocks {
...

	ieee5000_fck: ieee5000_fck@e4 {
		#clock-cells = <0>;
		compatible = "ti,gate-clock";
		clocks = <&dpll_core_m4_div2_ck>;
		ti,bit-shift = <1>;
		reg = <0x00e4>;
	};

to something like this to better correlate to the TRM 8.1.12.1.40 CM_PER_IEEE5000_CLKCTRL Register(offset= E4h) ? Or is there any reason the ieee5000 is a ti,gate-clock?

&prcm {
	per_cm: per-cm@0 {
		compatible = "ti,omap4-cm";
		reg = <0x0 0x400>;
		#address-cells = <1>;
		#size-cells = <1>;
		ranges = <0 0x0 0x400>;
...
                ieee5000_clkctrl: ieee5000_clkctrl@e4 {
                        compatible = "ti,clkctrl";
                        reg = <0xe4 0x4>;
                        #clock-cells = <2>;
                };

		pruss_ocp_clkctrl: pruss-ocp-clkctrl@e8 {
			compatible = "ti,clkctrl";
			reg = <0xe8 0x4>;
			#clock-cells = <2>;
		};
Signature · 3 lines
Bästa Hälsningar
Oskar Holmlund
Tel 070-3220292
#1 lore raw

Hi,

Quoted 13 lines · Oskar Holmlund

Hi,

Is it possible to move
&prcm_clocks {
...

	ieee5000_fck: ieee5000_fck@e4 {
		#clock-cells = <0>;
		compatible = "ti,gate-clock";
		clocks = <&dpll_core_m4_div2_ck>;
		ti,bit-shift = <1>;
		reg = <0x00e4>;
	};
Quoted 3 lines

to something like this to better correlate to the TRM 8.1.12.1.40 CM_PER_IEEE5000_CLKCTRL Register(offset= E4h) ?
Or is there any reason the ieee5000 is a ti,gate-clock?

For the clkctrl clocks, we should just use cm base + offset. But somehow we don't have this for ieee5000_clkctrl defined in the include/dt-bindings/clock/am3.h.

Regards,

Tony