linux.git/drivers/clk, branch v3.10-rc4

clk: mxs: Include clk mxs header file

2013-05-31T01:27:24+00:00

Fix the following sparse warnings:

drivers/clk/mxs/clk-imx28.c:72:5: warning: symbol 'mxs_saif_clkmux_select' was not declared. Should it be static?
drivers/clk/mxs/clk-imx28.c:156:12: warning: symbol 'mx28_clocks_init' was not declared. Should it be static?

Signed-off-by: Fabio Estevam 
Acked-by: Shawn Guo 
Signed-off-by: Mike Turquette 
[mturquette@linaro.org: fixed $SUBJECT line]

clk: vt8500: Fix unbalanced spinlock in vt8500_dclk_set_rate()

2013-05-29T23:13:58+00:00

With the addition of a DVO clock, a bug is now evident in the vt8500
clock code:
[    0.290000] WARNING: at init/main.c:698 do_one_initcall+0x158/0x18c()
[    0.300000] initcall wm8505fb_driver_init+0x0/0xc returned with disabled int

This is caused by an unbalanced spinlock in vt8500_dclk_set_rate().
Replace the second call to spin_lock_irqsave() with spin_unlock_irqrestore().

Signed-off-by: Tony Prisk 
Signed-off-by: Mike Turquette

clk: si5351: Set initial clkout rate when defined in platform data.

2013-05-29T22:09:24+00:00

clock-frequency property from platform data was read but never used.
Apply defined rate when clock is registered.

Signed-off-by: Marek Belisko 
Acked-by: Sebastian Hesselbarth 
Signed-off-by: Mike Turquette 
[mturquette@linaro.org: add missing changelog]
Cc: stable@kernel.org

Signed-off-by: Mike Turquette

clk: si5351: Fix clkout rate computation.

2013-05-29T22:09:15+00:00

Rate was incorrectly computed because we read from wrong divider register.

Signed-off-by: Marek Belisko 
Acked-by: Sebastian Hesselbarth 
Signed-off-by: Mike Turquette 
Cc: stable@kernel.org

clk: samsung: Add CLK_IGNORE_UNUSED flag for the sysreg clocks

2013-05-29T18:52:19+00:00

Currently no driver *) handles the sysreg clock, with an assumption
that this clock is always left in its default state (enabled).

Before commit 6e6aac7590f902d14d90bace3fd499
ARM: EXYNOS: Migrate clock support to common clock framework

the sysreg clock was not even defined and hence wasn't handled
explicitly in the kernel.

To restore the previous behaviour disable masking the sysreg clock
off in the clock core by default.

*) Except the Exynos4x12 FIMC-IS driver, which will be modified
   to not touch the sysreg clock.

Signed-off-by: Sylwester Nawrocki 
Signed-off-by: Kyungmin Park 
Signed-off-by: Mike Turquette

clk: ux500: clk-sysctrl: handle clocks with no parents

2013-05-29T18:52:18+00:00

Fix clk_reg_sysctrl() to set main clock registers of new struct
clk_sysctrl even if the registered clock has no parents.

This fixes an issue where "ulpclk" was registered with all clk->reg_*
fields uninitialized, causing a -EINVAL error from clk_prepare().

Signed-off-by: Fabio Baltieri 
Acked-by: Ulf Hansson 
Signed-off-by: Mike Turquette

clk: ux500: Provide device enumeration number suffix for SMSC911x

2013-05-29T18:52:18+00:00

First Ethernet device has a ".0" appended onto the device name. It
appears that we need this in order to obtain the correct clock.

Without this fix Ethernet does not function on Ux500 devices, which is a
regression.

Cc: Ulf Hansson 
Signed-off-by: Lee Jones 
Signed-off-by: Mike Turquette 
[mturquette@linaro.org: improved changelog]

Merge branch 'fixes' of git://git.infradead.org/users/vkoul/slave-dma

2013-05-26T03:30:31+00:00

Pull slave-dma fixes from Vinod Koul:
 "We have two patches from Andy & Rafael fixing the Lynxpoint dma"

* 'fixes' of git://git.infradead.org/users/vkoul/slave-dma:
  ACPI / LPSS: register clock device for Lynxpoint DMA properly
  dma: acpi-dma: parse CSRT to extract additional resources

clk: tegra: add ac97 controller clock

2013-05-21T06:24:34+00:00

AC97 controller clock is hardwired to pll_a_out0.

Signed-off-by: Lucas Stach 
Acked-by: Peter De Schrijver 
Reviewed-by: Prashant Gaikwad 
Acked-by: Mike Turquette 
Tested-by: Stephen Warren 
Signed-off-by: Stephen Warren 
Signed-off-by: Olof Johansson

clk: tegra: remove USB from clk init table

2013-05-21T06:24:34+00:00

The USB clocks are just clock gates, so no need to set a specific clock.
In fact trying to set a specific clock is just a NOP if the requested
clockrate is the same as those of the parent (clk_m) or will trigger a
WARN_ON() if rates don't match up.

As we are not setting a specific rate, nor activating the clocks at
init, there is no point in keeping the the usb entries in the clock init
table.

Signed-off-by: Lucas Stach 
Acked-by: Peter De Schrijver 
Reviewed-by: Prashant Gaikwad 
Acked-by: Mike Turquette 
Tested-by: Stephen Warren 
Signed-off-by: Stephen Warren 
Signed-off-by: Olof Johansson