linux-toradex.git/drivers/i2c/Makefile, branch v3.10.78

i2c-stub: Move to drivers/i2c

2012-10-28T20:37:00+00:00

Move the i2c-stub driver to drivers/i2c, to match the Kconfig entry.
This is less confusing that way.

I also fixed all checkpatch warnings and errors.

Signed-off-by: Jean Delvare 
Cc: Peter Huewe

i2c: Deprecate i2c_driver.attach_adapter and .detach_adapter

2011-03-20T13:50:53+00:00

The last legitimate user of i2c_driver.attach_adapter and
.detach_adapter is gone, so we can finally deprecate these callbacks.
The last few drivers which still use these will have to be updated to
make use of standard I2C device instantiation ways instead.

Signed-off-by: Jean Delvare

i2c: Change to new flag variable

2010-10-24T16:16:58+00:00

Replace EXTRA_CFLAGS with ccflags-y.

Signed-off-by: matt mooney 
Signed-off-by: Jean Delvare

i2c: I2C bus multiplexer driver pca954x

2010-08-11T16:21:03+00:00

I2C driver for PCA954x I2C multiplexer series.

Signed-off-by: Michael Lawnick 
Acked-by: Rodolfo Giometti 
Signed-off-by: Jean Delvare

i2c: Multiplexed I2C bus core support

2010-08-11T16:21:02+00:00

Add multiplexed bus core support. I2C multiplexer and switches
like pca954x get instantiated as new adapters per port.

Signed-off-by: Michael Lawnick 
Acked-by: Rodolfo Giometti 
Signed-off-by: Jean Delvare

tsl2550: Move from i2c/chips to misc

2010-03-13T19:56:54+00:00

Move the last remaining driver from i2c/chips to misc. Good ridance!

Signed-off-by: Jean Delvare 
Acked-by: Wolfram Sang 
Acked-by: Jonathan Cameron

i2c: Separate Kconfig option for i2c-smbus

2010-03-02T11:23:43+00:00

Having a separate Kconfig option for i2c-smbus makes it possible to
build that support as a module even when i2c-core itself is built-in.
Bus drivers which implement SMBus alert should select this option, so
in most cases this option is hidden and the user doesn't have to care
about it.

Signed-off-by: Jean Delvare 
Cc: David Brownell 
Cc: Trent Piepho

i2c: Add SMBus alert support

2010-03-02T11:23:42+00:00

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

i2c: Add i2c_board_info and i2c_new_device()

2007-05-01T21:26:31+00:00

This provides partial support for new-style I2C driver binding.  It builds
on "struct i2c_board_info" declarations that identify I2C devices on a given
board.  This is needed on systems with I2C devices that can't be fully probed
and/or autoconfigured, such as many embedded Linux configurations where the
way a given I2C device is wired may affect how it must be used.

There are two models for declaring such devices:

 * LATE -- using a public function i2c_new_device().  This lets modules
   declare I2C devices found *AFTER* a given I2C adapter becomes available.
   
   For example, a PCI card could create adapters giving access to utility
   chips on that card, and this would be used to associate those chips with
   those adapters.

 * EARLY -- from arch_initcall() level code, using a non-exported function
   i2c_register_board_info().  This copies the declarations *BEFORE* such
   an i2c_adapter becomes available, arranging that i2c_new_device() will
   be called later when i2c-core registers the relevant i2c_adapter.

   For example, arch/.../.../board-*.c files would declare the I2C devices
   along with their platform data, and I2C devices would behave much like
   PNPACPI devices.  (That is, both enumerate from board-specific tables.)

To match the exported i2c_new_device(), the previously-private function
i2c_unregister_device() is now exported.

Pending later patches using these new APIs, this is effectively a NOP.

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

[PATCH] hwmon: hwmon vs i2c, second round (07/11)

2005-09-05T16:14:22+00:00

The only part left in i2c-sensor is the VRM/VRD/VID handling code.
This is in no way related to i2c, so it doesn't belong there. Move
the code to hwmon, where it belongs.

Note that not all hardware monitoring drivers do VRM/VRD/VID
operations, so less drivers depend on hwmon-vid than there were
depending on i2c-sensor.

Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman