On Sat, Feb 9, 2019 at 2:25 PM Jonathan Neuschäfer <j.neuschaefer@xxxxxxx> wrote: > > On Thu, Feb 07, 2019 at 10:50:28PM -0200, Fabio Estevam wrote: > > On Thu, Feb 7, 2019 at 8:52 PM Jonathan Neuschäfer > [...] > > > I tried to compare the CCM's clocks between i.MX50 and i.MX53, but > > > unfortunately, the i.MX50 reference manual doesn't have the table called > > > "Output clocks from CCM". > > > > Please check Table 5-10. CCM_CCGR3 Gated Clock Mapping to Target > > Module from the MX50 Referene Manual. > > Ok, the tables show: > > For i.MX50: > [1:0] 0 ipg_clk_root eSDHCv2_1 and it also shows that ahb_clk_root is controlled by these same bits. That's why I added the ahb entry in my suggestion. > [3:2] 1 esdhc1_clk_root eSDHCv2_1 > > For i.MX53: > 1–0 CG0 esdhc1_ipg_hclk: affects ipg_clk and hclk inputs of ESDEHC-1 (esdhc1_clk_enable) > 3–2 CG1 esdhc1_perclk: affects ipg_clk_perclk input of ESDEHC-1 (esdhc1_serial_clk_enable) > > Table 18-3 (Output clocks from CCM) in the iMX53RM shows that > ESDHCv2-1's ipg_clk_perclk is esdhc1_clk_root, so the clock structure > does seem to be the same here, between i.MX50 and i.MX53… That's correct. The esdhc clocks seem to differ.