linux.git/drivers/i2c, branch v4.9-rc3

i2c: imx: defer probe if bus recovery GPIOs are not ready

2016-10-25T10:15:00+00:00

Some SoC might load the GPIO driver after the I2C driver and
using the I2C bus recovery mechanism via GPIOs. In this case
it is crucial to defer probing if the GPIO request functions
do so, otherwise the I2C driver gets loaded without recovery
mechanisms enabled.

Signed-off-by: Stefan Agner 
Acked-by: Uwe Kleine-König 
Acked-by: Li Yang 
Signed-off-by: Wolfram Sang 
Cc: stable@kernel.org

i2c: designware: Avoid aborted transfers with fast reacting I2C slaves

2016-10-25T10:09:09+00:00

I2C DesignWare may abort transfer with arbitration lost if I2C slave pulls
SDA down quickly after falling edge of SCL. Reason for this is unknown but
after trial and error it was found this can be avoided by enabling non-zero
SDA RX hold time for the receiver.

By the specification SDA RX hold time extends incoming SDA low to high
transition by n * ic_clk cycles but only when SCL is high. However it
seems to help avoid above faulty arbitration lost error.

Bits 23:16 in IC_SDA_HOLD register define the SDA RX hold time for the
receiver. Be conservative and enable 1 ic_clk cycle long hold time in
case boot firmware hasn't set it up.

Reported-by: Jukka Laitinen 
Signed-off-by: Jarkko Nikula 
Tested-by: Jukka Laitinen 
Signed-off-by: Wolfram Sang

i2c: i801: Fix I2C Block Read on 8-Series/C220 and later

2016-10-25T10:00:01+00:00

Starting with the 8-Series/C220 PCH (Lynx Point), the SMBus
controller includes a SPD EEPROM protection mechanism. Once the SPD
Write Disable bit is set, only reads are allowed to slave addresses
0x50-0x57.

However the legacy implementation of I2C Block Read since the ICH5
looks like a write, and is therefore blocked by the SPD protection
mechanism. This causes the eeprom and at24 drivers to fail.

So assume that I2C Block Read is implemented as an actual read on
these chipsets. I tested it on my Q87 chipset and it seems to work
just fine.

Signed-off-by: Jean Delvare 
Tested-by: Jarkko Nikula 
[wsa: rebased to v4.9-rc2]
Signed-off-by: Wolfram Sang

i2c: xgene: Avoid dma_buffer overrun

2016-10-25T09:50:52+00:00

SMBus block command uses the first byte of buffer for the data length.
The dma_buffer should be increased by 1 to avoid the overrun issue.

Reported-by: Phil Endecott 
Signed-off-by: Hoan Tran 
Signed-off-by: Wolfram Sang 
Cc: stable@kernel.org

i2c: digicolor: Fix module autoload

2016-10-25T09:49:01+00:00

If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.

Export the module alias information using the MODULE_DEVICE_TABLE() macro.

Signed-off-by: Javier Martinez Canillas 
Acked-by: Baruch Siach 
Signed-off-by: Wolfram Sang

i2c: xlr: Fix module autoload for OF registration

2016-10-25T09:49:00+00:00

If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.

Export the module alias information using the MODULE_DEVICE_TABLE() macro.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Wolfram Sang

i2c: xlp9xx: Fix module autoload

2016-10-25T09:48:59+00:00

If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.

Export the module alias information using the MODULE_DEVICE_TABLE() macro.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Wolfram Sang

i2c: jz4780: Fix module autoload

2016-10-25T09:48:58+00:00

If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.

Export the module alias information using the MODULE_DEVICE_TABLE() macro.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Wolfram Sang

i2c: allow configuration of imx driver for ColdFire architecture

2016-10-25T09:48:57+00:00

The i2c controller used by Freescales iMX processors is the same
hardware module used on Freescales ColdFire family of processors.

We can use the existing i2c-imx driver on ColdFire family members.
Modify the configuration to allow it to be selected when compiling
for ColdFire targets.

Signed-off-by: Greg Ungerer 
Signed-off-by: Wolfram Sang

i2c: mark device nodes only in case of successful instantiation

2016-10-25T09:48:48+00:00

Instantiated I2C device nodes are marked with OF_POPULATE. This was
introduced in 4f001fd30145a6. On unloading, loaded device nodes will of
course be unmarked. The problem are nodes that fail during
initialisation: If a node fails, it won't be unloaded and hence not be
unmarked.

If a I2C driver module is unloaded and reloaded, it will skip nodes that
failed before.

Skip device nodes that are already populated and mark them only in case
of success.

Fixes: 4f001fd30145a6 ("i2c: Mark instantiated device nodes with OF_POPULATE")
Signed-off-by: Ralf Ramsauer 
Reviewed-by: Geert Uytterhoeven 
Acked-by: Pantelis Antoniou 
[wsa: use 14-digit commit sha]
Signed-off-by: Wolfram Sang 
Cc: stable@kernel.org