linux.git/drivers/i2c/chips, branch v2.6.16

[PATCH] IRQ type flags

2006-01-09T04:13:46+00:00

Some ARM platforms have the ability to program the interrupt controller to
detect various interrupt edges and/or levels.  For some platforms, this is
critical to setup correctly, particularly those which the setting is dependent
on the device.

Currently, ARM drivers do (eg) the following:

	err = request_irq(irq, ...);

	set_irq_type(irq, IRQT_RISING);

However, if the interrupt has previously been programmed to be level sensitive
(for whatever reason) then this will cause an interrupt storm.

Hence, if we combine set_irq_type() with request_irq(), we can then safely set
the type prior to unmasking the interrupt.  The unfortunate problem is that in
order to support this, these flags need to be visible outside of the ARM
architecture - drivers such as smc91x need these flags and they're
cross-architecture.

Finally, the SA_TRIGGER_* flag passed to request_irq() should reflect the
property that the device would like.  The IRQ controller code should do its
best to select the most appropriate supported mode.

Signed-off-by: Russell King 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] I2C: Remove .owner setting from i2c_driver as it's no longer needed

2006-01-06T06:16:25+00:00

Now that i2c_add_driver() doesn't need the module owner to be set by
hand, we can delete it from the drivers.  This patch catches all of the
drivers that I found in the current tree (if a driver sets the .owner by
hand, it's not a problem, just not needed.)

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

[PATCH] i2c: Drop i2c_driver.{owner,name}, 2 of 11

2006-01-06T06:16:23+00:00

We should use the i2c_driver.driver's .name and .owner fields
instead of the i2c_driver's ones.

This patch updates the miscellaneaous i2c chip drivers.

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

[PATCH] i2c: Rework client usage count, 2 of 3

2006-01-06T06:16:22+00:00

Make I2C_CLIENT_ALLOW_USE the default for all i2c clients. It doesn't
hurt if the usage count is actually never used for any given driver,
and allows for nice code simplifications in i2c-core.

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

[PATCH] i2c: Drop i2c_driver.flags, 2 of 3

2006-01-06T06:16:21+00:00

Just about every i2c chip driver sets the I2C_DF_NOTIFY flag, so we
can simply make it the default and drop the flag. If any driver really
doesn't want to be notified when i2c adapters are added, that driver
can simply omit to set .attach_adapter. This approach is also more
robust as it prevents accidental NULL pointer dereferences.

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

[PATCH] i2c: Remove duplicate rtc8564 BCD macros

2006-01-06T06:16:21+00:00

Remove duplicate of BCD macros.

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

[PATCH] i2c: Extend ds1337 initialization

2006-01-06T06:16:20+00:00

Add code to handle case where board firmware does not start the
RTC.

Signed-off-by: Jean Delvare 
CC: James Chapman 
Signed-off-by: Greg Kroah-Hartman

Merge master.kernel.org:/home/rmk/linux-2.6-drvmodel

2005-11-11T17:24:26+00:00

[DRIVER MODEL] Convert platform drivers to use struct platform_driver

2005-11-09T22:32:44+00:00

This allows us to eliminate the casts in the drivers, and eventually
remove the use of the device_driver function pointer methods for
platform device drivers.

Signed-off-by: Russell King 
Acked-by: Greg Kroah-Hartman

[PATCH] i2c: ds1337 BCD conversion fix

2005-11-08T05:46:37+00:00

Fix BCD value errors when month=9, moving the increment inside the
BIN2BCD macro.
Fix similar code for the weekday value, just for consistency.

This bug was reported by Michael Burian .

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