<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/misc/eeprom, branch v3.4-rc2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/misc/eeprom?h=v3.4-rc2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/misc/eeprom?h=v3.4-rc2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-01-25T00:31:49Z</updated>
<entry>
<title>MISC: convert drivers/misc/* to use module_spi_driver()</title>
<updated>2012-01-25T00:31:49Z</updated>
<author>
<name>Axel Lin</name>
<email>axel.lin@gmail.com</email>
</author>
<published>2012-01-22T07:38:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a3dc3c9eb0a7bcf17604ee444c48b94e2591812d'/>
<id>urn:sha1:a3dc3c9eb0a7bcf17604ee444c48b94e2591812d</id>
<content type='text'>
This patch converts the drivers in drivers/misc/* to use the
module_spi_driver() macro which makes the code smaller and a bit
simpler.

Signed-off-by: Axel Lin &lt;axel.lin@gmail.com&gt;
Cc: Michael Hennerich &lt;hennerich@blackfin.uclinux.org&gt;
Cc: Anatolij Gustschin &lt;agust@denx.de&gt;
Cc: Daniel Mack &lt;zonque@gmail.com&gt;
Acked-by: Michael Hennerich &lt;michael.hennerich@analog.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>MISC: convert drivers/misc/* to use module_i2c_driver()</title>
<updated>2012-01-25T00:31:49Z</updated>
<author>
<name>Axel Lin</name>
<email>axel.lin@gmail.com</email>
</author>
<published>2012-01-22T07:36:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a64fe2ed76614d37abb6966a67f4f39d10efba3c'/>
<id>urn:sha1:a64fe2ed76614d37abb6966a67f4f39d10efba3c</id>
<content type='text'>
This patch converts the drivers in drivers/misc/* to use the
module_i2c_driver() macro which makes the code smaller and a bit
simpler.

Signed-off-by: Axel Lin &lt;axel.lin@gmail.com&gt;
Cc: Michael Hennerich &lt;hennerich@blackfin.uclinux.org&gt;
Cc: Anantha Narayanan &lt;Anantha.Narayanan@intel.com&gt;
Cc: Hemanth V &lt;hemanthv@ti.com&gt;
Cc: Christoph Mair &lt;christoph.mair@gmail.com&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Cc: Ben Gardner &lt;bgardner@wabtec.com&gt;
Cc: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
Cc: Kalhan Trisal &lt;kalhan.trisal@intel.com&gt;
Cc: Darrick J. Wong &lt;djwong@us.ibm.com&gt;
Cc: Daniel Mack &lt;zonque@gmail.com&gt;
Cc: Rodolfo Giometti &lt;giometti@linux.it&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>eeprom_93cx6: Add write support</title>
<updated>2011-11-26T19:59:39Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben@simtec.co.uk</email>
</author>
<published>2011-11-21T08:57:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=072bc80156729f853e8bcafe1b17c48c74462887'/>
<id>urn:sha1:072bc80156729f853e8bcafe1b17c48c74462887</id>
<content type='text'>
Add support for writing data to EEPROM.

Signed-off-by: Ben Dooks &lt;ben@simtec.co.uk&gt;
Cc: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Cc: Jean Delvare &lt;khali@linux-fr.org&gt;
Cc: Linux Kernel &lt;linux-kernel@vger.kernel.org&gt;
Signed-off-by: Stephen Boyd &lt;sboyd@codeaurora.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>eeprom_93cx6: Add data direction control.</title>
<updated>2011-11-26T19:59:38Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben@simtec.co.uk</email>
</author>
<published>2011-11-21T08:57:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b30f8bdcfa7dd05f4268348f3388ff903132f28e'/>
<id>urn:sha1:b30f8bdcfa7dd05f4268348f3388ff903132f28e</id>
<content type='text'>
Some devices need to know if the data is to be output or read, so add a
data direction into the eeprom structure to tell the driver whether the
data line should be driven.

The user in this case is the Micrel KS8851 which has a direction
control for the EEPROM data line and thus needs to know whether
to drive it (writing) or to tristate it for receiving.

Signed-off-by: Ben Dooks &lt;ben@simtec.co.uk&gt;
Cc: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Cc: Jean Delvare &lt;khali@linux-fr.org&gt;
Signed-off-by: Stephen Boyd &lt;sboyd@codeaurora.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>drivers/misc/eeprom: fix dependecy on 'PPC_MPC5200_GPIO'</title>
<updated>2011-11-16T00:41:51Z</updated>
<author>
<name>Paul Bolle</name>
<email>pebolle@tiscali.nl</email>
</author>
<published>2011-11-15T22:36:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=001ef5e4554b851cf50fe03bc4c266c28ed8e62d'/>
<id>urn:sha1:001ef5e4554b851cf50fe03bc4c266c28ed8e62d</id>
<content type='text'>
The driver for the DigsyMTC display configuration EEPROMs device got
added by commit 469dded183 ("misc/eeprom: add eeprom access driver for
digsy_mtc board").  Its Kconfig symbol depends on PPC_MPC5200_GPIO.  But
at the time that driver got added PPC_MPC5200_GPIO was already renamed
to GPIO_MPC5200, by commit 6eae1ace68 ("gpio: Move mpc5200 gpio driver
to drivers/gpio").

So make this driver depend on GPIO_MPC5200.  And since GPIO_MPC5200
itself implies that GPIOLIB is set, that dependency can be dropped.

Signed-off-by: Paul Bolle &lt;pebolle@tiscali.nl&gt;
Acked-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&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>misc/eeprom: add eeprom access driver for digsy_mtc board</title>
<updated>2011-07-26T03:57:16Z</updated>
<author>
<name>Anatolij Gustschin</name>
<email>agust@denx.de</email>
</author>
<published>2011-07-26T00:13:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=469dded1839105cfbfc265376e23e24dbc48d2a7'/>
<id>urn:sha1:469dded1839105cfbfc265376e23e24dbc48d2a7</id>
<content type='text'>
Both displays on digsy_mtc board obtain their configuration from microwire
EEPROMs which are connected to the SoC over GPIO lines.  We need an easy
way to access the EEPROMs to write the needed display configuration or to
read out the currently programmed configuration.  The generic
eeprom_93xx46 SPI driver added by previous patch allows EEPROM access over
sysfs.  Using the simple driver added by this patch we provide used GPIO
interface and access control description on the board for generic
eeprom_93xx46 driver and spi_gpio driver.

Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Cc: Jonathan Cameron &lt;jic23@cam.ac.uk&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&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>misc/eeprom: add driver for microwire 93xx46 EEPROMs</title>
<updated>2011-07-26T03:57:16Z</updated>
<author>
<name>Anatolij Gustschin</name>
<email>agust@denx.de</email>
</author>
<published>2011-07-26T00:13:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=06b4501e88ad10f02849a3f9d7408ed6ae15a53f'/>
<id>urn:sha1:06b4501e88ad10f02849a3f9d7408ed6ae15a53f</id>
<content type='text'>
Add EEPROM driver for 93xx46 chips.  It can also be used with spi_gpio
driver to access 93xx46 EEPROMs connected over GPIO lines.  This driver
supports read/write/erase access to the EEPROM chips over sysfs files.

[rdunlap@xenotime.net: fix printk format]
Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Cc: Jonathan Cameron &lt;jic23@cam.ac.uk&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Signed-off-by: Randy Dunlap &lt;rdunlap@xenotime.net&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>misc/at24: add more sanity checks for parameters</title>
<updated>2010-12-24T09:14:17Z</updated>
<author>
<name>Wolfram Sang</name>
<email>w.sang@pengutronix.de</email>
</author>
<published>2010-11-17T12:00:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=45efe847971e6274a04eea75a0745d8015b54d37'/>
<id>urn:sha1:45efe847971e6274a04eea75a0745d8015b54d37</id>
<content type='text'>
Side-effects happen when passing 0 to either io_limit or page_size. Give
an error in case of this misconfiguration.

Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>misc/at24: parse device tree data</title>
<updated>2010-12-24T09:13:36Z</updated>
<author>
<name>Wolfram Sang</name>
<email>w.sang@pengutronix.de</email>
</author>
<published>2010-11-17T12:00:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9ed030d728f3bd03b6e869357da02725afda19a7'/>
<id>urn:sha1:9ed030d728f3bd03b6e869357da02725afda19a7</id>
<content type='text'>
Information about the pagesize and read-only-status may also come from
the devicetree. Parse this data, too, and act accordingly. While we are
here, change the initialization printout a bit. write_max is useful to
know to detect performance bottlenecks, the rest is superfluous.

Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>i2c: Remove all i2c_set_clientdata(client, NULL) in drivers</title>
<updated>2010-06-03T09:33:58Z</updated>
<author>
<name>Wolfram Sang</name>
<email>w.sang@pengutronix.de</email>
</author>
<published>2010-06-03T09:33:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fbae3fb1546e199ab0cd185348f8124411a1ca9d'/>
<id>urn:sha1:fbae3fb1546e199ab0cd185348f8124411a1ca9d</id>
<content type='text'>
I2C drivers can use the clientdata-pointer to point to private data. As I2C
devices are not really unregistered, but merely detached from their driver, it
used to be the drivers obligation to clear this pointer during remove() or a
failed probe(). As a couple of drivers forgot to do this, it was agreed that it
was cleaner if the i2c-core does this clearance when appropriate, as there is
no guarantee for the lifetime of the clientdata-pointer after remove() anyhow.
This feature was added to the core with commit
e4a7b9b04de15f6b63da5ccdd373ffa3057a3681 to fix the faulty drivers.

As there is no need anymore to clear the clientdata-pointer, remove all current
occurrences in the drivers to simplify the code and prevent confusion.

Signed-off-by: Wolfram Sang &lt;w.sang@pengutronix.de&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Acked-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Acked-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
Acked-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
</content>
</entry>
</feed>
