<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/drivers/i2c, branch v3.2.29</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v3.2.29</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v3.2.29'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2012-05-30T23:44:07Z</updated>
<entry>
<title>i2c: davinci: Free requested IRQ in remove</title>
<updated>2012-05-30T23:44:07Z</updated>
<author>
<name>Marcus Folkesson</name>
<email>marcus.folkesson@gmail.com</email>
</author>
<published>2012-05-03T13:56:36Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=9afc65d564540a06a81379630b91e4bc2afb57ad'/>
<id>urn:sha1:9afc65d564540a06a81379630b91e4bc2afb57ad</id>
<content type='text'>
commit 9868a060ccf769c08ec378a9829137e272e9a92c upstream.

The freed IRQ is not necessary the one requested in probe.
Even if it was, with two or more i2c-controllers it will fails anyway.

Signed-off-by: Marcus Folkesson &lt;marcus.folkesson@gmail.com&gt;
Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>i2c: tegra: notify transfer-complete after clearing status.</title>
<updated>2012-05-30T23:44:07Z</updated>
<author>
<name>Laxman Dewangan</name>
<email>ldewangan@nvidia.com</email>
</author>
<published>2012-05-07T06:46:19Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a31f2d4c2c85fdd2fb3ae84c9081b0762ea14457'/>
<id>urn:sha1:a31f2d4c2c85fdd2fb3ae84c9081b0762ea14457</id>
<content type='text'>
commit c889e91d2cc22123f20f40dde0c0a91856a20eea upstream.

The notification of the transfer complete by calling complete()
should be done after clearing all interrupt status.
This avoids the race condition of misconfigure the i2c controller
in multi-core environment.

Signed-off-by: Laxman Dewangan &lt;ldewangan@nvidia.com&gt;
Acked-by: Stephen Warren &lt;swarren@wwwdotorg.org&gt;
Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>i2c-eg20t: change timeout value 50msec to 1000msec</title>
<updated>2012-05-30T23:43:56Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya.rohm@gmail.com</email>
</author>
<published>2012-03-26T05:55:25Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=fb169a0bf61e5a11d112d99471013f62e5f9f2fb'/>
<id>urn:sha1:fb169a0bf61e5a11d112d99471013f62e5f9f2fb</id>
<content type='text'>
commit 8a52f9f347da721b199b7f9dcc0168bbe7d0baae upstream.

Currently, during i2c works alone, wait-event timeout is not occurred.
However, as CPU load increases, timeout occurs frequently.
So, I modified like this patch.
Modifying like this patch, I've never seen the timeout event with high
load test.

Signed-off-by: Tomoya MORINAGA &lt;tomoya.rohm@gmail.com&gt;
Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>i2c: pnx: Disable clk in suspend</title>
<updated>2012-05-11T12:14:53Z</updated>
<author>
<name>Roland Stigge</name>
<email>stigge@antcom.de</email>
</author>
<published>2012-04-04T08:34:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=b110a7c55ab6ad4dc953396236451ff885326e5b'/>
<id>urn:sha1:b110a7c55ab6ad4dc953396236451ff885326e5b</id>
<content type='text'>
commit 6c557cfee08751d22aed34840f389b846f0f4508 upstream.

In the driver's suspend function, clk_enable() was used instead of
clk_disable(). This is corrected with this patch.

Signed-off-by: Roland Stigge &lt;stigge@antcom.de&gt;
Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

[wsa: reworded commit header slightly]

Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>i2c-algo-bit: Fix spurious SCL timeouts under heavy load</title>
<updated>2012-03-19T16:02:35Z</updated>
<author>
<name>Ville Syrjala</name>
<email>syrjala@sci.fi</email>
</author>
<published>2012-03-15T17:11:05Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=883eb9633dcc5d3cc2389110508805d1d80c9d09'/>
<id>urn:sha1:883eb9633dcc5d3cc2389110508805d1d80c9d09</id>
<content type='text'>
commit 8ee161ce5e0cfc689eb677f227a6248191165fac upstream.

When the system is under heavy load, there can be a significant delay
between the getscl() and time_after() calls inside sclhi(). That delay
may cause the time_after() check to trigger after SCL has gone high,
causing sclhi() to return -ETIMEDOUT.

To fix the problem, double check that SCL is still low after the
timeout has been reached, before deciding to return -ETIMEDOUT.

Signed-off-by: Ville Syrjala &lt;syrjala@sci.fi&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>i2c: mxs: only flag completion when queue is completely done</title>
<updated>2012-03-12T19:31:23Z</updated>
<author>
<name>Wolfram Sang</name>
<email>w.sang@pengutronix.de</email>
</author>
<published>2012-01-13T11:14:26Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=46774e8405812c94d96d795c9f0e1750f90811e0'/>
<id>urn:sha1:46774e8405812c94d96d795c9f0e1750f90811e0</id>
<content type='text'>
commit 844990daa2e69a4258049ba9c2bae1180657dac3 upstream.

The hardware generates an interrupt for every completed command in the
queue while the code assumed that it will only generate one interrupt
when the queue is empty. So, explicitly check if the queue is really
empty. This patch fixed problems which occurred due to high traffic on
the bus. While we are here, move the completion-initialization after the
parameter error checking.

Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Cc: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Cc: Marek Vasut &lt;marek.vasut@gmail.com&gt;
Cc: Lothar Waßmann &lt;LW@KARO-electronics.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>i2c-eg20t: modified the setting of transfer rate.</title>
<updated>2012-01-26T00:13:56Z</updated>
<author>
<name>Toshiharu Okada</name>
<email>toshiharu-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-26T07:16:23Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=8d7385000114bd38bdeb6ca175262b56aecd1931'/>
<id>urn:sha1:8d7385000114bd38bdeb6ca175262b56aecd1931</id>
<content type='text'>
commit ff35e8b18984ad2a82cbd259fc07f0be4b34b1aa upstream.

This patch modified the setting value of
I2C Bus Transfer Rate Setting Counter regisrer.

Signed-off-by: Toshiharu Okada &lt;toshiharu-linux@dsn.okisemi.com&gt;
Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>I2C: OMAP: correct SYSC register offset for OMAP4</title>
<updated>2012-01-26T00:13:52Z</updated>
<author>
<name>Alexander Aring</name>
<email>a.aring@phytec.de</email>
</author>
<published>2011-12-08T14:43:53Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a92ad2dcdcb74c7813e2dd88d2635a1831894808'/>
<id>urn:sha1:a92ad2dcdcb74c7813e2dd88d2635a1831894808</id>
<content type='text'>
commit 2727b1753934e154931d6b3bdf20c9b2398457a2 upstream.

Correct OMAP_I2C_SYSC_REG offset in omap4 register map.
Offset 0x20 is reserved and OMAP_I2C_SYSC_REG has 0x10 as offset.

Signed-off-by: Alexander Aring &lt;a.aring@phytec.de&gt;
[khilman@ti.com: minor changelog edits]
Signed-off-by: Kevin Hilman &lt;khilman@ti.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>i2c: Fix error value returned by several bus drivers</title>
<updated>2012-01-26T00:13:27Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2012-01-12T19:32:03Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=69b97cf56b6b8fa15244322bc65eb6008793acaf'/>
<id>urn:sha1:69b97cf56b6b8fa15244322bc65eb6008793acaf</id>
<content type='text'>
commit 7c1f59c9d5caf3a84f35549b5d58f3c055a68da5 upstream.

When adding checks for ACPI resource conflicts to many bus drivers,
not enough attention was paid to the error paths, and for several
drivers this causes 0 to be returned on error in some cases. Fix this
by properly returning a non-zero value on every error.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>i2c-eg20t: correct the driver init order of pch_i2c_probe()</title>
<updated>2011-12-18T11:46:42Z</updated>
<author>
<name>Feng Tang</name>
<email>feng.tang@intel.com</email>
</author>
<published>2011-11-29T07:19:10Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=0d5fb5ea7d0e6bc84a523c39a666d7eb1a7e43de'/>
<id>urn:sha1:0d5fb5ea7d0e6bc84a523c39a666d7eb1a7e43de</id>
<content type='text'>
Before registering an adapter to i2c subsystem, we need make sure
driver is ready for incoming i2c xfer, becasue the i2c_add_adapter()
may trigger a i2c device driver's proble function which may start
some real i2c xfer. I met this issue when integrating a TSC2007 i2c
touch screen device with the i2c-eg20t driver.

This patch will call request_irq() and hw init before calling
i2c_add_adapter().

Signed-off-by: Feng Tang &lt;feng.tang@intel.com&gt;
Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
</content>
</entry>
</feed>
