u-boot.git/drivers/i2c, branch v2015.01-rc2

linux/kernel.h: sync min, max, min3, max3 macros with Linux

2014-11-23T11:48:30+00:00

U-Boot has never cared about the type when we get max/min of two
values, but Linux Kernel does.  This commit gets min, max, min3, max3
macros synced with the kernel introducing type checks.

Many of references of those macros must be fixed to suppress warnings.
We have two options:
 - Use min, max, min3, max3 only when the arguments have the same type
   (or add casts to the arguments)
 - Use min_t/max_t instead with the appropriate type for the first
   argument

Signed-off-by: Masahiro Yamada 
Acked-by: Pavel Machek 
Acked-by: Lukasz Majewski 
Tested-by: Lukasz Majewski 
[trini: Fixup arch/blackfin/lib/string.c]
Signed-off-by: Tom Rini

blackfin: convert to use CONFIG_SYS_I2C framework

2014-11-17T07:10:37+00:00

Signed-off-by: Scott Jiang

adi_i2c: convert to use general io accessors.

2014-11-17T07:10:15+00:00

Signed-off-by: Scott Jiang

blackfin: rename bfin-twi_i2c driver to adi_i2c

2014-11-17T07:10:04+00:00

Signed-off-by: Scott Jiang

i2c: rcar_i2c: Fix order of restart and clear status

2014-11-10T05:47:37+00:00

In case of repeated START condition, the restart has to be kicked
before clear status (MSR register). If it is kicked after clear status,
R-Car I2C may transfer data (TXD register) or receive data (RXD register)
instead of transferring slave address (MAR register).

Signed-off-by: Ryo Kataoka 
Signed-off-by: Nobuhiro Iwamatsu

drivers/i2c/fsl_i2c: Change CONFIG_I2C_TIMEOUT to 100ms

2014-11-10T05:47:36+00:00

Some slow I2C devices like Power Monitor(ZM7304) at times
do not work well with low timeout value, so I2C bus get stuck
during read cycle with this device, changing it to 100ms from
10ms works fine

A lot of other i2c drivers like mxc and i2c drivers of BOOTROM
also use relax timeouts to give sufficient ticks to work well
with slower devices

Signed-off-by: Shaveta Leekha 
Signed-off-by: Poonam Aggrwal

ppc4xx: Handle i2c stuck on combined xfer

2014-11-10T05:44:30+00:00

ppc4xx i2c master gets stuck on errors while repeated start is
active. Can be easily reproduced by "i2c md" on an unpopulated
i2c address. There is not stop condition given, scl remains
pulled low.
The only way out seems to be doing a stop manually and then a
soft reset.

Signed-off-by: Dirk Eibach 
Reviewed-by: Stefan Roese

ppc4xx: Fix i2c repeated start

2014-11-10T05:44:15+00:00

Debugging some i2c trouble I saw on my scope that repeated
start is not working properply. The 4xx even held clock pulled down
after transfers. Having a look in the driver I realized
that IIC_CNTL_RPST is set on that part of the transfer that should
begin with a repeated start. But repeated start is about not sending a
stop condition, so IIC_CNTL_RPST has to be set on the last transfer
before the repeated start happens.

Signed-off-by: Dirk Eibach 
Reviewed-by: Stefan Roese

i2c: use __weak

2014-11-04T20:00:55+00:00

Cc: Heiko Schocher 
Signed-off-by: Jeroen Hofstee

i2c: designware: Convert driver to multibus/multiadapter framework

2014-10-29T07:56:23+00:00

In preparation for the SoCFPGA support of the designware I2C driver,
convert this driver to the common CONFIG_SYS_I2C framework.

This patch converts all users of this driver, this is:

- ST spearxxx boards
- AXS101 (ARC700 platform)

I couldn't test this patch on those boards. Only compile tested for all
spear boards. And tested on SoCFPGA.

Signed-off-by: Stefan Roese 
Reviewed-by: Marek Vasut 
Acked-by: Alexey Brodkin 
Tested-by: Alexey Brodkin 
Cc: Heiko Schocher 
Cc: Vipin Kumar 
Cc: Jeroen Hofstee