<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/i2c, branch v2.6.23.3</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/i2c?h=v2.6.23.3</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/i2c?h=v2.6.23.3'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2007-09-09T20:29:14Z</updated>
<entry>
<title>i2c-algo-bit: Read block data bugfix</title>
<updated>2007-09-09T20:29:14Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2007-09-09T20:29:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=939bc4943d0483961edc45b63a7d27b4ffe547e3'/>
<id>urn:sha1:939bc4943d0483961edc45b63a7d27b4ffe547e3</id>
<content type='text'>
This fixes a bug in the way i2c-algo-bit handles I2C_M_RECV_LEN,
used to implement i2c_smbus_read_block_data().  Previously, in the
absence of PEC (rarely used!) it would NAK the "length" byte:

	S addr Rd [A] [length] NA

That prevents the subsequent data bytes from being read:

	S addr Rd [A] [length] { A [data] }* NA

The primary fix just reorders two code blocks, so the length used
in the "should I NAK now?" check incorporates the data which it
just read from the slave device.

However, that move also highlighted other fault handling glitches.
This fixes those by abstracting the RX path ack/nak logic, so it
can be used in more than one location.  Also, a few CodingStyle
issues were also resolved.

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-pxa: Fix adapter number</title>
<updated>2007-09-09T20:29:13Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2007-09-09T20:29:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=51e5709ad46127da9476f31336113b5401f94dba'/>
<id>urn:sha1:51e5709ad46127da9476f31336113b5401f94dba</id>
<content type='text'>
It turns out that platform_device.id is a "u32" so testing it for being
nonnegative is useless when setting up an i2c adapte.  Instead,
do what the platform_bus code does and test it against the value "-1".

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-gpio: Fix adapter number</title>
<updated>2007-09-09T20:29:13Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2007-09-09T20:29:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9a3180e70e35ff69586ada5421b5e7bad52f60e4'/>
<id>urn:sha1:9a3180e70e35ff69586ada5421b5e7bad52f60e4</id>
<content type='text'>
It turns out that platform_device.id is a "u32" so testing it for being
nonnegative is useless when setting up an i2c bitbang device.  Instead,
do what the platform_bus code does and test it against the value "-1". 

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Acked-by: Atsushi Nemoto &lt;anemo@mba.ocn.ne.jp&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-piix4: Fix SB700 PCI device ID</title>
<updated>2007-08-31T08:42:23Z</updated>
<author>
<name>Shane Huang</name>
<email>shane.huang@amd.com</email>
</author>
<published>2007-08-31T06:56:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=60693e5a9a2063b87d4dbe8029816c814b3fa84e'/>
<id>urn:sha1:60693e5a9a2063b87d4dbe8029816c814b3fa84e</id>
<content type='text'>
We find that SB700 and SB800 use the same SMBus device ID as SB600, which is
0x4385, instead of the already submitted 0x4395.

Besides removing the wrong SB700 device ID, add SB800 support to kernel, by
renaming the PCI_DEVICE_ID_ATI_IXP600_SMBUS into
PCI_DEVICE_ID_ATI_SBX00_SMBUS.

Signed-off-by: Shane Huang &lt;shane.huang@amd.com&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>i2c-s3c2410: Build fix</title>
<updated>2007-08-14T16:37:15Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben@fluff.org</email>
</author>
<published>2007-08-14T16:37:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b5d0b4ba389711183b5af71438fe21b40ee32d6d'/>
<id>urn:sha1:b5d0b4ba389711183b5af71438fe21b40ee32d6d</id>
<content type='text'>
Fixup the include files after the arch moves that
where included in 2.6.23.

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c/menelaus: Build fix</title>
<updated>2007-08-14T16:37:14Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2007-08-14T16:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c1147cc6d18389f6530bae27741b9b2665e862e6'/>
<id>urn:sha1:c1147cc6d18389f6530bae27741b9b2665e862e6</id>
<content type='text'>
Fix Menelaus build error, and remove needless "#define DEBUG".

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-mv64xxx: Reinitialize hw and driver on I2C bus hang</title>
<updated>2007-08-14T16:37:14Z</updated>
<author>
<name>Dale Farnsworth</name>
<email>dale@farnsworth.org</email>
</author>
<published>2007-08-14T16:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a07ad1cc0300931bfd76bfcd2da3ddad743f4a89'/>
<id>urn:sha1:a07ad1cc0300931bfd76bfcd2da3ddad743f4a89</id>
<content type='text'>
Under certain conditions, the mv64xxx I2C bus can hang preventing
further operation.  To make the driver more robust, we now reset
the I2C hardware and the driver state machine when such hangs are
detected.

Signed-off-by: Dale Farnsworth &lt;dale@farnsworth.org&gt;
Acked-by: Mark A. Greer &lt;mgreer@mvista.com&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-mpc: Don't disable I2C module on stop condition</title>
<updated>2007-08-14T16:37:14Z</updated>
<author>
<name>Domen Puncer</name>
<email>domen.puncer@telargo.com</email>
</author>
<published>2007-08-14T16:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5af0e07f87e7d9be2a9db514af1e338341240f6d'/>
<id>urn:sha1:5af0e07f87e7d9be2a9db514af1e338341240f6d</id>
<content type='text'>
Disabling module on stop doesn't work on some CPUs (ie. mpc8241,
as reported by Guennadi Liakhovetski), so remove that.

Disable I2C module on errors/interrupts to prevent it from
locking up on mpc5200b.

Signed-off-by: Domen Puncer &lt;domen.puncer@telargo.com&gt;
Acked-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c-iop3xx: Set I2C_CLASS_HWMON to adapter class</title>
<updated>2007-08-14T16:37:14Z</updated>
<author>
<name>Arnaud Patard</name>
<email>arnaud.patard@rtp-net.org</email>
</author>
<published>2007-08-14T16:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=432ca994bf7107e88916fd9606ca7402a4571359'/>
<id>urn:sha1:432ca994bf7107e88916fd9606ca7402a4571359</id>
<content type='text'>
In order to be able to use sensors on the IOP3xx SoCs, one needs to set
the adapter class to I2C_CLASS_HWMON.

Signed-off-by: Arnaud Patard &lt;arnaud.patard@rtp-net.org&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
<entry>
<title>i2c/isp1301_omap: Build fixes, whitespace</title>
<updated>2007-08-14T16:37:14Z</updated>
<author>
<name>David Brownell</name>
<email>david-b@pacbell.net</email>
</author>
<published>2007-08-14T16:37:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=25da383d26a1dcca4f0205769a24e5eac79c6d35'/>
<id>urn:sha1:25da383d26a1dcca4f0205769a24e5eac79c6d35</id>
<content type='text'>
Build fixes for isp1301_omap driver.  I think an earlier version
of this must have gotten lost somewhere, or maybe it only went
into the Linux-OMAP tree.

Also, some whitespace fixes to bring this more into sync with the
version of this found in the Linux-OMAP tree.  (That version has
updates for the OTG controller on the OMAP 1710 which break that
functionality on OMAP 161x boards like the H2, so merging all of
it is not currently an option.)

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
</feed>
