<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/clk, branch v3.12.10</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/clk?h=v3.12.10</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/clk?h=v3.12.10'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-01-15T23:31:42Z</updated>
<entry>
<title>clk: exynos5250: fix sysmmu_mfc{l,r} gate clocks</title>
<updated>2014-01-15T23:31:42Z</updated>
<author>
<name>Andrew Bresticker</name>
<email>abrestic@chromium.org</email>
</author>
<published>2013-11-08T10:14:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=778b3b76c34292c7d27aa0faad5c9026a2cacf43'/>
<id>urn:sha1:778b3b76c34292c7d27aa0faad5c9026a2cacf43</id>
<content type='text'>
commit 97c3557c3e0413efb1f021f582d1459760e22727 upstream.

The gate clocks for the MFC sysmmus appear to be flipped, i.e.
GATE_IP_MFC[2] gates sysmmu_mfcl and GATE_IP_MFC[1] gates sysmmu_mfcr.
Fix this so that the MFC will start up.

Signed-off-by: Andrew Bresticker &lt;abrestic@chromium.org&gt;
Signed-off-by: Sachin Kamat &lt;sachin.kamat@linaro.org&gt;
Acked-by: Mike Turquette &lt;mturquette@linaro.org&gt;
Signed-off-by: Tomasz Figa &lt;t.figa@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: samsung: exynos5250: Add CLK_IGNORE_UNUSED flag for the sysreg clock</title>
<updated>2014-01-15T23:31:42Z</updated>
<author>
<name>Abhilash Kesavan</name>
<email>a.kesavan@samsung.com</email>
</author>
<published>2013-12-11T11:57:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=801e517cf190f19c5cb2e62605d92524a9396be8'/>
<id>urn:sha1:801e517cf190f19c5cb2e62605d92524a9396be8</id>
<content type='text'>
commit 2feed5aecf5f367b92bd6b6e92afe9e3de466907 upstream.

The sysreg (system register) generates control signals for various blocks
like disp1blk, i2c, mipi, usb etc. However, it gets disabled as an unused
clock at boot-up. This can lead to failures in operation of above blocks,
because they can not be configured properly if this clock is disabled.

Signed-off-by: Abhilash Kesavan &lt;a.kesavan@samsung.com&gt;
Acked-by: Mike Turquette &lt;mturquette@linaro.org&gt;
[t.figa: Updated patch description.]
Signed-off-by: Tomasz Figa &lt;t.figa@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: samsung: exynos5250: Add MDMA0 clocks</title>
<updated>2014-01-15T23:31:42Z</updated>
<author>
<name>Abhilash Kesavan</name>
<email>a.kesavan@samsung.com</email>
</author>
<published>2013-12-12T03:02:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f19053a2ddf64b1b98157e2d78c14b0cf5fb95c6'/>
<id>urn:sha1:f19053a2ddf64b1b98157e2d78c14b0cf5fb95c6</id>
<content type='text'>
commit 8fb9aeb7a71ef4f3e0613d459a2e1366a7a90469 upstream.

Adds gate clock for MDMA0 on Exynos5250 SoC. This is needed to ensure
that the clock is enabled when MDMA0 is used on systems on which
firmware gates the clockby default.

Signed-off-by: Abhilash Kesavan &lt;a.kesavan@samsung.com&gt;
Acked-by: Mike Turquette &lt;mturquette@linaro.org&gt;
[t.figa: Updated patch description.]
Signed-off-by: Tomasz Figa &lt;t.figa@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: samsung: exynos5250: Fix ACP gate register offset</title>
<updated>2014-01-15T23:31:41Z</updated>
<author>
<name>Abhilash Kesavan</name>
<email>a.kesavan@samsung.com</email>
</author>
<published>2013-12-12T03:02:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c1adda6a9b2afa13e0e26a966ca355c69192dbc9'/>
<id>urn:sha1:c1adda6a9b2afa13e0e26a966ca355c69192dbc9</id>
<content type='text'>
commit 3bf34666a0cce5234ac677ed2fbe5cea82c71329 upstream.

The CLK_GATE_IP_ACP register offset is incorrectly listed making
definition of g2d clock incorrect, which may lead to system failures
when trying to use G2D on systems on which firmware gates this clock
by default. Fix this and the register ordering as well.

Signed-off-by: Abhilash Kesavan &lt;a.kesavan@samsung.com&gt;
Acked-by: Mike Turquette &lt;mturquette@linaro.org&gt;
[t.figa: Updated patch description.]
Signed-off-by: Tomasz Figa &lt;t.figa@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: samsung: exynos4: Correct SRC_MFC register</title>
<updated>2014-01-15T23:31:41Z</updated>
<author>
<name>Seung-Woo Kim</name>
<email>sw0312.kim@samsung.com</email>
</author>
<published>2013-11-22T05:21:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dda034c3ba2094dc414112706e1e3f353225ca07'/>
<id>urn:sha1:dda034c3ba2094dc414112706e1e3f353225ca07</id>
<content type='text'>
commit 5fdd1b56be51b1ec4dbde5b213d649ac717442da upstream.

The SRC_MFC register offset was incorrect, which could cause have caused
wrong calculation of rate of sclk_mfc clock, that could in turn lead to
incorrect operation of MFC. This patch corrects it.

Signed-off-by: Seung-Woo Kim &lt;sw0312.kim@samsung.com&gt;
Acked-by: Mike Turquette &lt;mturquette@linaro.org&gt;
[t.figa: Updated patch description]
Signed-off-by: Tomasz Figa &lt;t.figa@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: clk-divider: fix divisor &gt; 255 bug</title>
<updated>2014-01-15T23:31:41Z</updated>
<author>
<name>James Hogan</name>
<email>james.hogan@imgtec.com</email>
</author>
<published>2013-12-16T10:41:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ba8ccb9b88d9b8e6170fd4f7eb3b906531f05f87'/>
<id>urn:sha1:ba8ccb9b88d9b8e6170fd4f7eb3b906531f05f87</id>
<content type='text'>
commit 778037e1ccb75609846deca9e419449c1dc137fa upstream.

Commit 6d9252bd9a4bb (clk: Add support for power of two type dividers)
merged in v3.6 added the _get_val function to convert a divisor value to
a register field value depending on the flags. However it used the type
u8 for the div field, causing divisors larger than 255 to be masked
and the resultant clock rate to be too high.

E.g. in my case an 11bit divider was supposed to divide 24.576 MHz down
to 32.768KHz. The divisor was correctly calculated as 750 (0x2ee). This
was masked to 238 (0xee) resulting in a frequency of 103.26KHz.

Signed-off-by: James Hogan &lt;james.hogan@imgtec.com&gt;
Cc: Rajendra Nayak &lt;rnayak@ti.com&gt;
Cc: linux-arm-kernel@lists.infradead.org
Signed-off-by: Mike Turquette &lt;mturquette@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>clk: fixup argument order when setting VCO parameters</title>
<updated>2013-10-08T06:01:07Z</updated>
<author>
<name>Jonathan Austin</name>
<email>jonathan.austin@arm.com</email>
</author>
<published>2013-07-23T15:42:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2f9f64bc5aa31836810cd25301aa4772ad73ebab'/>
<id>urn:sha1:2f9f64bc5aa31836810cd25301aa4772ad73ebab</id>
<content type='text'>
The order of arguments in the call to vco_set() for the ICST clocks appears to
have been switched in error, which results in the VCO not being initialised
correctly. This in turn stops the integrated LCD on things like Integrator/CP
from working correctly.

This patch fixes the order and restores the expected functionality.

Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Jonathan Austin &lt;jonathan.austin@arm.com&gt;
Signed-off-by: Mike Turquette &lt;mturquette@linaro.org&gt;
Cc: stable@vger.kernel.org
</content>
</entry>
<entry>
<title>clk: socfpga: Fix incorrect sdmmc clock name</title>
<updated>2013-10-08T01:37:49Z</updated>
<author>
<name>Dinh Nguyen</name>
<email>dinguyen@altera.com</email>
</author>
<published>2013-09-17T16:23:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=79a2e998895ae3e75d6d3d9fdeec2be94bfcf6c8'/>
<id>urn:sha1:79a2e998895ae3e75d6d3d9fdeec2be94bfcf6c8</id>
<content type='text'>
The SD/MMC clock is named "sdmmc_clk", and NOT "mmc_clk". Because of this,
the SD driver was getting the incorrect clock value. This prevented the
SD driver from initializing correctly.

Signed-off-by: Dinh Nguyen &lt;dinguyen@altera.com&gt;
CC: Arnd Bergmann &lt;arnd@arndb.de&gt;
CC: Olof Johansson &lt;olof@lixom.net&gt;
Reviewed-by: Pavel Machek &lt;pavel@denx.de&gt;
Cc: linux-arm-kernel@lists.infradead.org
Signed-off-by: Mike Turquette &lt;mturquette@linaro.org&gt;
</content>
</entry>
<entry>
<title>clk: armada-370: fix tclk frequencies</title>
<updated>2013-10-07T00:39:46Z</updated>
<author>
<name>Simon Guinot</name>
<email>simon.guinot@sequanux.org</email>
</author>
<published>2013-10-03T10:05:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1022c75f5abd3a3b25e679bc8793d21bedd009b4'/>
<id>urn:sha1:1022c75f5abd3a3b25e679bc8793d21bedd009b4</id>
<content type='text'>
This patch fixes the tclk frequency array for the Armada-370 SoC.
This bug has been introduced by commit 6b72333d
("clk: mvebu: add Armada 370 SoC-centric clock init").

A wrong tclk frequency affects the following drivers: mvsdio, mvneta,
i2c-mv64xxx and mvebu-devbus. This list may be incomplete.

About the mvneta Ethernet driver, note that the tclk frequency is used
to compute the Rx time coalescence. Then, this bug harms the coalescence
configuration and also degrades the networking performances with the
default values.

Signed-off-by: Simon Guinot &lt;simon.guinot@sequanux.org&gt;
Cc: Andrew Lunn &lt;andrew@lunn.ch&gt;
Cc: Gregory CLEMENT &lt;gregory.clement@free-electrons.com&gt;
Cc: Sebastian Hesselbarth &lt;sebastian.hesselbarth@gmail.com&gt;
Acked-by: Jason Cooper &lt;jason@lakedaemon.net&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Michael Turquette &lt;mturquette@deferred.io&gt;
</content>
</entry>
<entry>
<title>clk: nomadik: set all timers to use 2.4 MHz TIMCLK</title>
<updated>2013-10-02T04:39:56Z</updated>
<author>
<name>Linus Walleij</name>
<email>linus.walleij@linaro.org</email>
</author>
<published>2013-09-13T19:45:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b9b5ab11ea221a9f2d5af41da639e0898675c34c'/>
<id>urn:sha1:b9b5ab11ea221a9f2d5af41da639e0898675c34c</id>
<content type='text'>
This fixes a regression for the Nomadik on the main system
timers.

The Nomadik seemed a bit slow and its heartbeat wasn't looking
healthy. And it was not strange, because it has been connected
to the 32768 Hz clock at boot, while being told by the clock driver
that it was 2.4MHz. Actually connect the TIMCLK to 2.4MHz by
default as this is what we want for nice scheduling, clocksource
and clock event.

Cc: stable@vger.kernel.org
Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Mike Turquette &lt;mturquette@linaro.org&gt;
</content>
</entry>
</feed>
