<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/i2c, branch v2.6.26</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.26</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.26'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2008-07-01T13:30:38Z</updated>
<entry>
<title>I2C: S3C2410: Add MODULE_ALIAS() for s3c2440 device.</title>
<updated>2008-07-01T13:30:38Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben-linux@fluff.org</email>
</author>
<published>2008-07-01T10:59:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d150a4bbd0e5c6427e66086b139953428680160b'/>
<id>urn:sha1:d150a4bbd0e5c6427e66086b139953428680160b</id>
<content type='text'>
Add a MODULE_ALIAS() statement for the i2c-s3c2410 controller
to ensure that it can be autoloaded on the S3C2440 systems that
we support.

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
</content>
</entry>
<entry>
<title>I2C: S3C2410: Fixup error codes returned rom a transfer.</title>
<updated>2008-07-01T13:30:37Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben-linux@fluff.org</email>
</author>
<published>2008-07-01T10:59:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=63f5c2891eae6b4dd0538ef094e5f256d6150d7b'/>
<id>urn:sha1:63f5c2891eae6b4dd0538ef094e5f256d6150d7b</id>
<content type='text'>
The driver should be returning -ENXIO for transfers that do not
pass the initial address byte stage.

Note, also small tidyups to the driver comments in the area.

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
</content>
</entry>
<entry>
<title>I2C: S3C2410: Check ACK on byte transmission</title>
<updated>2008-07-01T13:30:37Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben-linux@fluff.org</email>
</author>
<published>2008-07-01T10:59:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2709781be6141798162f1089df728fb218a590df'/>
<id>urn:sha1:2709781be6141798162f1089df728fb218a590df</id>
<content type='text'>
We should check for the reception of an ACK after transmitting each
data byte. The address send has been correctly checking this, but the
data write byte state should have also been checking for these failures.

As part of the same fix, we remove the ACK checking from the receive
path where it should not have been checking for an ACK which our hardware
was sending.

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
</content>
</entry>
<entry>
<title>i2c/max6875: Really prevent 24RF08 corruption</title>
<updated>2008-05-18T18:49:41Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-05-18T18:49:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=70455e790391dac85d9b483a9e286a40df1ecc7f'/>
<id>urn:sha1:70455e790391dac85d9b483a9e286a40df1ecc7f</id>
<content type='text'>
i2c-core takes care of the possible corruption of 24RF08 chips for
quite some times, so device devices no longer need to do it. And they
really should not, as applying the prevention twice voids it.

I thought that I had fixed all drivers long ago but apparently I had
missed that one.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Cc: Ben Gardner &lt;bgardner@wabtec.com&gt;
</content>
</entry>
<entry>
<title>i2c-amd756: Fix functionality flags</title>
<updated>2008-05-18T18:49:41Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-05-18T18:49:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=875b0a473c3ddd80bc4ae88a65cd20027428e160'/>
<id>urn:sha1:875b0a473c3ddd80bc4ae88a65cd20027428e160</id>
<content type='text'>
The i2c-amd756 driver pretends to support SMBus process call
transactions but actually does not. Fix it.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c: Kill the old driver matching scheme</title>
<updated>2008-05-18T18:49:41Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-05-18T18:49:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=eb8a79080984eb9819406a55e4dd17043c380a09'/>
<id>urn:sha1:eb8a79080984eb9819406a55e4dd17043c380a09</id>
<content type='text'>
Remove the old driver_name/type scheme for i2c driver matching. Only the
standard aliasing model will be used from now on.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-nforce2: Disable the second SMBus channel on the DFI Lanparty NF4 Expert</title>
<updated>2008-05-18T18:49:40Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-05-18T18:49:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=08851d6eb4eeb0894f4d095dfdf8ab61c435ad57'/>
<id>urn:sha1:08851d6eb4eeb0894f4d095dfdf8ab61c435ad57</id>
<content type='text'>
There is a strange chip at 0x2e on the second SMBus channel of the
DFI Lanparty NF4 Expert motherboard. Accessing the chip reboots the
system. As there's nothing interesting on this SMBus channel, the
easiest and safest thing to do is to disable it on that board.

This is a better fix to bug #5889 than the it87 driver update that was
done originally:
http://bugzilla.kernel.org/show_bug.cgi?id=5889

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>[MIPS] Alchemy: SMBus resource fix</title>
<updated>2008-05-12T15:46:50Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2008-04-05T18:16:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8e07c2c6af30dccfa573033d280980b2b5eb35fe'/>
<id>urn:sha1:8e07c2c6af30dccfa573033d280980b2b5eb35fe</id>
<content type='text'>
The Alchemy platform code registers the SMBus device using the virtual
address of its registers instead of the physical one -- fix this, taking
into account that actually the whole megabyte is decoded by any of the
programmable serial controllers (one of which is SMBus), and that all the
Alchemy peripherals are directly mappable into KSEG1 kernel space and
therefore ioremap() call would just boil down to CKSEG1ADDR() invocation.

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
</content>
</entry>
<entry>
<title>i2c: Match dummy devices by type</title>
<updated>2008-05-11T18:37:06Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2008-05-11T18:37:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=60b129d7bfa3e20450816983bd52c49bb0bc1c21'/>
<id>urn:sha1:60b129d7bfa3e20450816983bd52c49bb0bc1c21</id>
<content type='text'>
As the old driver_name/type matching scheme is going away soon, change
the dummy device mechanism to use the new matching scheme.

This has the downside that dummy i2c clients can no longer choose
their name, they'll all appear as "dummy" in sysfs and in log
messages. I don't think it is a problem in practice though, as there
is little reason to use these i2c clients to log messages.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-sibyte: Mark i2c_sibyte_add_bus() as static</title>
<updated>2008-05-11T18:37:05Z</updated>
<author>
<name>Maciej W. Rozycki</name>
<email>macro@linux-mips.org</email>
</author>
<published>2008-05-11T18:37:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b11a9d8392a698f01337232aa8c5d5603519943f'/>
<id>urn:sha1:b11a9d8392a698f01337232aa8c5d5603519943f</id>
<content type='text'>
The i2c_sibyte_add_bus() function is not called, nor meant to, from 
outside, so mark it as static; fixing a sparse warning too.

Signed-off-by: Maciej W. Rozycki &lt;macro@linux-mips.org&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
</feed>
