1. 16 9月, 2014 1 次提交
    • S
      ARM: imx: clk-vf610: introduce clks_init_on · 3b18dd7a
      Stefan Agner 提交于
      At the end of the boot process, the clock framework might disable
      required main PLL's. So far, this was no issue since drivers
      requested clocks, which are descended of the main PLL's (e.g.
      pll1_pfd1, which provides the system clock).
      
      To archive the full 500MHz system clock, DDR clock need to be a
      descendant of PLL2 rather than PLL1 (DDRC_CLK_SEL set to 0). The
      bootloader sets up the clocks accordingly before making use of
      DDR at all. However, in Linux, there is no driver using PLL2,
      which lead to PLL2 being disabled by the clock framework.
      
      With this patch, we make sure that the main system clock and the
      DDR clock are initially enabled and are kept enabled.
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Signed-off-by: NShawn Guo <shawn.guo@freescale.com>
      3b18dd7a
  2. 18 7月, 2014 2 次提交
  3. 05 3月, 2014 1 次提交
    • L
      ARM: imx: clk-vf610: Suppress duplicate const sparse warning · b78f1e80
      Liu Ying 提交于
      There should be no duplicate const specifiers for those static
      constant character string arrays defined for clock mux options.
      Also, the arrays are only taken as the 5th argument for the
      imx_clk_mux() function, which is in the type of 'const char
      **parents'.  So, let's remove the 2nd const specifier right
      after 'char'.
      
      This patch fixes these sparse warnings:
      arch/arm/mach-imx/clk-vf610.c:66:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:67:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:68:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:69:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:70:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:71:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:72:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:73:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:74:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:75:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:76:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:77:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:78:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:79:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:80:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:81:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:83:25: warning: duplicate const
      arch/arm/mach-imx/clk-vf610.c:84:25: warning: duplicate const
      Signed-off-by: NLiu Ying <Ying.Liu@freescale.com>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      b78f1e80
  4. 09 12月, 2013 1 次提交
  5. 15 7月, 2013 1 次提交
    • S
      ARM: imx: fix vf610 enet module clock selection · 4f71612e
      Shawn Guo 提交于
      The fec/enet driver calculates MDC rate with the formula below.
      
        ref_freq / ((MII_SPEED + 1) x 2)
      
      The ref_freq here is the fec internal module clock, which is missing
      from clk-vf610 clock driver right now.  And clk-vf610 driver mistakenly
      supplies RMII clock (50 MHz) as the source to fec.  This results in the
      situation that fec driver gets ref_freq as 50 MHz, while physically it
      runs at 66 MHz (fec module clock physically sources from ipg which runs
      at 66 MHz).  That's why software expects MDC runs at 2.5 MHz, while the
      measurement tells it runs at 3.3 MHz.  And this causes the PHY KSZ8041
      keeps swithing between Full and Half mode as below.
      
        libphy: 400d0000.etherne:00 - Link is Up - 100/Full
        libphy: 400d0000.etherne:00 - Link is Up - 100/Half
        libphy: 400d0000.etherne:00 - Link is Up - 100/Full
        libphy: 400d0000.etherne:00 - Link is Up - 100/Half
        libphy: 400d0000.etherne:00 - Link is Up - 100/Full
        libphy: 400d0000.etherne:00 - Link is Up - 100/Half
      
      Add the missing module clock for ENET0 and ENET1, and correct the clock
      supplying in device tree to fix above issue.
      
      Thanks to Alison Wang <b18965@freescale.com> for debugging the issue.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      4f71612e
  6. 17 6月, 2013 1 次提交