04 May, 2010
1 commit
-
After discovering that a lot of i2c-drivers leave the pointer to their
clientdata dangling, it was decided to let the core handle this issue.
It is assumed that the core may access the private data after remove()
as there are no guarantees for the lifetime of such pointers anyhow (see
thread starting at http://lkml.org/lkml/2010/3/21/68)Signed-off-by: Wolfram Sang
Signed-off-by: Jean Delvare
02 Mar, 2010
5 commits
-
i2c_master_send & i2c_master_recv do not support more than 64 kb
transfer, since msg.len is u16.Signed-off-by: Zhangfei Gao
Signed-off-by: Jean Delvare -
Add support for the SMBus alert mechanism to the i2c-parport-light
driver. The ADM1032 evaluation board at least is properly wired for
this.Signed-off-by: Jean Delvare
Cc: David Brownell
Cc: Trent Piepho -
Add support for the SMBus alert mechanism to the i2c-parport driver.
The ADM1032 evaluation board at least is properly wired for this.Signed-off-by: Jean Delvare
Cc: David Brownell
Cc: Trent Piepho -
SMBus alert support. The SMBus alert protocol allows several SMBus
slave devices to share a single interrupt pin on the SMBus master,
while still allowing the master to know which slave triggered the
interrupt.This is based on preliminary work by David Brownell. The key
difference between David's implementation and mine is that his was
part of i2c-core, while mine is split into a separate, standalone
module named i2c-smbus. The i2c-smbus module is meant to include
support for all SMBus extensions to the I2C protocol in the future.The benefit of this approach is a zero cost for I2C bus segments which
do not need SMBus alert support. Where David's implementation
increased the size of struct i2c_adapter by 7% (40 bytes on i386),
mine doesn't touch it. Where David's implementation added over 150
lines of code to i2c-core (+10%), mine doesn't touch it. The only
change that touches all the users of the i2c subsystem is a new
callback in struct i2c_driver (common to both implementations.) I seem
to remember Trent was worried about the footprint of David'd
implementation, hopefully mine addresses the issue.Signed-off-by: Jean Delvare
Acked-by: Jonathan Cameron
Cc: David Brownell
Cc: Trent Piepho -
Add the Intel Cougar Point (PCH) SMBus controller device IDs.
Signed-off-by: Seth Heasley
Signed-off-by: Jean Delvare
15 Dec, 2009
1 commit
-
Struct i2c_client_address_data only contains one field at this point,
which makes its usefulness questionable. Get rid of it and pass simple
address lists around instead.Signed-off-by: Jean Delvare
Tested-by: Wolfram Sang
07 Dec, 2009
5 commits
-
There is nothing sensors-specific to i2c-stub.
Signed-off-by: Jean Delvare
-
Add a module parameter to override the functionality bitfield. This
lets the user disable some commands. This can be used to force a chip
driver to take different code paths.Signed-off-by: Jean Delvare
-
This is required to test some drivers, for example at24.
Signed-off-by: Jean Delvare
-
The legacy probe and force module parameters are obsolete now, the
same can be achieved using the new_device sysfs interface, which is
both more flexible and cheaper (it is implemented by i2c-core rather
than replicated in every driver module.)The legacy ignore module parameters can be dropped as well. Ignoring
can be done by instantiating a "dummy" device at the problematic
address.This is the first step of a huge cleanup to i2c-core's i2c_detect
function, i2c.h's I2C_CLIENT_INSMOD* macros, and all drivers that made
use of them.Signed-off-by: Jean Delvare
-
Superseded by tdfxfb. I2C/DDC support used to live in a separate
driver but this caused driver conflicts.Signed-off-by: Jean Delvare
Cc: Krzysztof Helt
07 Nov, 2009
1 commit
-
Change SB900 to its formal code name Hudson-2.
Signed-off-by: Crane Cai
Signed-off-by: Jean Delvare
05 Oct, 2009
2 commits
-
The sysfs path to i2c adapters has changed recently, update the
documentation to reflect that change.Signed-off-by: Jean Delvare
-
Some times ago the eeprom and max6875 drivers moved to
drivers/misc/eeprom, but their documentation did not follow. It's
finally time to get rid of Documentation/i2c/chips.Signed-off-by: Jean Delvare
Cc: Ben Gardner
Acked-by: Wolfram Sang
19 Sep, 2009
4 commits
-
Add new SMBus device ID for AMD SB900.
Signed-off-by: Crane Cai
Signed-off-by: Jean Delvare -
The pcf8574 driver in drivers/i2c/chips which just exports its register to
sysfs is superseded by drivers/gpio/pcf857x.c which properly uses the gpiolib.
As this driver has been deprecated for more than a year, finally remove it.Signed-off-by: Wolfram Sang
Cc: Aurelien Jarno
Signed-off-by: Jean Delvare -
The pca9539 driver in drivers/i2c/chips which just exports its registers to
sysfs is superseded by drivers/gpio/pca953x.c which properly uses the gpiolib.
As this driver has been deprecated for more than a year, finally remove it.Signed-off-by: Wolfram Sang
Acked-by: Ben Gardner
Signed-off-by: Jean Delvare -
The pcf8575 driver in drivers/i2c/chips which just exports its register to
sysfs is superseded by drivers/gpio/pcf857x.c which properly uses the gpiolib.
As this driver has been deprecated for more than a year, finally remove it.Signed-off-by: Wolfram Sang
Cc: Bart Van Assche
Signed-off-by: Jean Delvare
19 Jun, 2009
2 commits
-
Add a sysfs interface to instantiate and delete I2C devices. This is
primarily a replacement of the force_* module parameters implemented
by some i2c drivers. These module parameters were implemented
internally by the I2C_CLIENT_INSMOD* macros, which don't scale well.This can also be used when developing a driver on a self-soldered
board which doesn't yet have proper I2C device declaration at the
platform level, and presumably for various debugging situations.Signed-off-by: Jean Delvare
Cc: David Brownell -
We converted all the legacy i2c drivers so we can finally get rid of
the legacy binding model. Hooray!Signed-off-by: Jean Delvare
Cc: David Brownell
16 Jun, 2009
1 commit
-
The south bridge of the VIA VX855 chipset has a different PCI Device ID
so i2c-viapro.c needs to be updated with this.Signed-off-by: Harald Welte
Signed-off-by: Jean Delvare
13 Jun, 2009
1 commit
-
There is sometimes a need for the ocores driver to add devices to the
bus when installed.i2c_register_board_info can not always be used, because the I2C devices
are not known at an early state, they could for instance be connected
on a I2C bus on a PCI device which has the Open Cores IP.i2c_new_device can not be used in all cases either since the resulting
bus nummer might be unknown.The solution is the pass a list of I2C devices in the platform data to
the Open Cores driver. This is useful for MFD drivers.Signed-off-by: Richard Röjfors
Signed-off-by: Ben Dooks
31 Mar, 2009
1 commit
-
Directory drivers/i2c/chips is going away, so drivers there must find
new homes. For the pcf8591 driver, the best choice seems to be the
hwmon subsystem. While the Philips PCF8591 device isn't a typical
hardware monitoring chip, its DAC interface is compatible with the
hwmon one, so it fits somewhat.If a better subsystem is ever created for ADC/DAC chips, the driver
could be moved there.Signed-off-by: Jean Delvare
Cc: Aurelien Jarno
29 Mar, 2009
3 commits
-
Add support for the Broadcom HT1100 LD chipset (SMBus function.)
Signed-off-by: Flavio Leitner
Signed-off-by: Jean Delvare -
The MCP78S and MCP79 appear to be compatible with the previous nForce
chips as far as the SMBus controller is concerned. The MCP67 and MCP73
were not tested yet but I'd be very surprised if they weren't
compatible too.Signed-off-by: Jean Delvare
Cc: Oleg Ryjkov
Cc: Malcolm Lalkaka
Cc: Zbigniew Luszpinski -
On popular demand, here comes some documentation about how to
instantiate i2c devices in the new (standard) i2c device driver
binding model.I have also clarified how the class bitfield lets driver authors
control which buses are probed in the auto-detect case, and warned
more loudly against the abuse of this method.Signed-off-by: Jean Delvare
Acked-by: Michael Lawnick
Acked-by: Hans Verkuil
30 Oct, 2008
1 commit
-
Replace all references to the old i2c mailing list.
Signed-off-by: Jean Delvare
23 Oct, 2008
5 commits
-
* Strip trailing white space.
* Remove out-of-date or irrelevant parts.
* Insist on the fact that command is deprecated.
* Fix spelling mistakes and typos.
* Reformat code examples and function prototypes to comply with the
kernel coding style.Signed-off-by: Jean Delvare
-
The legacy i2c binding model is deprecated and will be removed soon,
so we no longer need to document it.Signed-off-by: Jean Delvare
-
i2c_get_clientdata doesn't change the i2c_client it is passed as a
parameter, so it can be constified. Same for i2c_get_adapdata.Signed-off-by: Jean Delvare
-
The document describing how to port i2c chip drivers from Linux 2.4 to
Linux 2.6 is outdated. As I suspect that most drivers that had to be
ported have already been by now, I do not want to spend time updating
it. Let's just delete it instead.Signed-off-by: Jean Delvare
-
Adds the Intel Ibex Peak (PCH) SMBus Controller Device IDs.
Signed-off-by: Seth Heasley
Signed-off-by: Jean Delvare
14 Oct, 2008
4 commits
-
Restore the i2c_smbus_process_call() as one driver (for the
Micronas MAP5401) will need it soon.[JD: Update documentation accordingly.]
Signed-off-by: Prakash Mortha
Signed-off-by: Jean Delvare -
I wrote this explanation to answer a question on the i2c mailing list,
and thought it would be good to have in the kernel documentation.Signed-off-by: Jean Delvare
-
* Clarify some points.
* Point developers to i2c-tools instead of lm_sensors.
* Fix coding style in code examples.Signed-off-by: Jean Delvare
-
Thanks to new datasheets published on http://linux.via.com.tw we can now add
support for VX800/VX820 chipsets.Signed-off-by: Rudolf Marek
Signed-off-by: Jean Delvare
28 Jul, 2008
1 commit
-
Add a document describing how i2c clients on Linux 2.6 can be
moved from the old to the new driver model.Signed-off-by: Ben Dooks
17 Jul, 2008
2 commits
-
The new-style max6875 driver implements the optional detect() callback
to cover the use cases of the legacy driver. I'm curious if anyone
really needs this though, so it might be removed in the feature.Signed-off-by: Jean Delvare
-
The new-style pca9539 driver implements the optional detect() callback
to cover the use cases of the legacy driver.Warning: users will now have to use the force module parameter to get
the driver to attach to their device. That's not a bad thing as these
devices can't be detected anyway.Note that this doesn't change the fact that this driver is deprecated
in favor of gpio/pca953x.Signed-off-by: Jean Delvare