15 Dec, 2009

1 commit


07 Dec, 2009

5 commits


07 Nov, 2009

1 commit


05 Oct, 2009

2 commits


19 Sep, 2009

4 commits

  • Add new SMBus device ID for AMD SB900.

    Signed-off-by: Crane Cai
    Signed-off-by: Jean Delvare

    Crane Cai
     
  • 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

    Wolfram Sang
     
  • 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

    Wolfram Sang
     
  • 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

    Wolfram Sang
     

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

    Jean Delvare
     
  • 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

    Jean Delvare
     

16 Jun, 2009

1 commit


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

    Richard Röjfors
     

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

    Jean Delvare
     

29 Mar, 2009

3 commits


30 Oct, 2008

1 commit


23 Oct, 2008

5 commits


14 Oct, 2008

4 commits


28 Jul, 2008

1 commit


17 Jul, 2008

4 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

    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

    Jean Delvare
     
  • The new-style pcf8575 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/pcf857x.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • The new-style pcf8574 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/pcf857x.

    Signed-off-by: Jean Delvare

    Jean Delvare
     

15 Jul, 2008

4 commits

  • Add a mechanism to let new-style i2c drivers optionally autodetect
    devices they would support on selected buses and ask i2c-core to
    instantiate them. This is a replacement for legacy i2c drivers, much
    cleaner.

    Where drivers had to implement both a legacy i2c_driver and a
    new-style i2c_driver so far, this mechanism makes it possible to get
    rid of the legacy i2c_driver and implement both enumerated and
    detected device support with just one (new-style) i2c_driver.

    Here is a quick conversion guide for these drivers, step by step:

    * Delete the legacy driver definition, registration and removal.
    Delete the attach_adapter and detach_client methods of the legacy
    driver.

    * Change the prototype of the legacy detect function from
    static int foo_detect(struct i2c_adapter *adapter, int address, int kind);
    to
    static int foo_detect(struct i2c_client *client, int kind,
    struct i2c_board_info *info);

    * Set the new-style driver detect callback to this new function, and
    set its address_data to &addr_data (addr_data is generally provided
    by I2C_CLIENT_INSMOD.)

    * Add the appropriate class to the new-style driver. This is
    typically the class the legacy attach_adapter method was checking
    for. Class checking is now mandatory (done by i2c-core.) See
    for the list of available classes.

    * Remove the i2c_client allocation and freeing from the detect
    function. A pre-allocated client is now handed to you by i2c-core,
    and is freed automatically.

    * Make the detect function fill the type field of the i2c_board_info
    structure it was passed as a parameter, and return 0, on success. If
    the detection fails, return -ENODEV.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • Function i2c_smbus_write_quick has no users left, so we can delete it.

    Also update the list of these helper functions which are gone but
    could be added back if needed.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • More updates to the I2C stack's fault reporting: make the core stop
    returning "-1" (usually "-EPERM") for all faults. Instead, pass lower
    level fault code up the stack, or return some appropriate errno.

    This patch happens to touch almost exclusively SMBus calls.

    Signed-off-by: David Brownell
    Signed-off-by: Jean Delvare

    David Brownell
     
  • Create Documentation/i2c/fault-codes to help standardize
    fault/error code usage in the I2C stack. It turns out that
    returning -1 (-EPERM) for everything was not at all helpful.

    Signed-off-by: David Brownell
    Signed-off-by: Jean Delvare

    David Brownell