u-boot.git/drivers/i2c, branch v2013.10

drivers: s3c44b0_i2c: delete an unused driver

2013-09-19T07:51:52+00:00

Since commit 5dc5f36 removed B2 board support,
there are no boards enabling s3c44b0_i2c.

Signed-off-by: Masahiro Yamada 
Cc: Wolfgang Denk 
Cc: Andrea Scian 
Acked-by: Heiko Schocher

fsl_i2c: add workaround for the erratum I2C A004447

2013-08-20T09:15:31+00:00

This workaround is for the erratum I2C A004447. Device reference
manual provides a scheme that allows the I2C master controller
to generate nine SCL pulses, which enable an I2C slave device
that held SDA low to release SDA. However, due to this erratum,
this scheme no longer works. In addition, when I2C is used as
a source of the PBL, the state machine is not able to recover.

At the same time, delete the reduplicative definition of SVR_VER
and SVR_REV. The SVR_REV is the low 8 bits rather than the low 16
bits of svr. And we use the CONFIG_SYS_FSL_A004447_SVR_REV macro
instead of hard-code value 0x10, 0x11 and 0x20.

The CONFIG_SYS_FSL_A004447_SVR_REV = 0x00 represents that one
version of platform has this I2C errata. So enable this errata
by IS_SVR_REV(svr, maj, min) function.

Signed-off-by: Zhao Chenhui 
Signed-off-by: Chunhe Lan 
Cc: Scott Wood 
Cc: Heiko Schocher

fsl_i2c: generate nine pulses on SCL if the I2C bus is hung

2013-08-20T09:15:31+00:00

When the code detected that the bus is hung (e.g. SDA stuck low),
send 9 pulses on SCL to try to fixup the bus.

Signed-off-by: Zhao Chenhui 
Signed-off-by: Chunhe Lan 
Cc: Scott Wood 
Cc: Heiko Schocher

tegra: Avoid using I2C prior to relocation

2013-08-13T21:11:25+00:00

Tegra recently moved to the new I2C framework, which sets up I2C prior to
relocation, and prior to calling i2c_init_board(). This causes a crash on
Tegra boards.

Tested-by: Stephen Warren 
Signed-off-by: Simon Glass

i2c: soft: Fix typo in CONFIG_SYS_I2C_SOFT_SPEED

2013-08-03T04:01:18+00:00

In case only the CONFIG_SYS_I2C_SPEED is set in configuration file,
the CONFIG_SYS_I2C_SOFT_SPEED is defined as CONFIG_SYS_I2C_SPEED.
The CONFIG_SYS_I2C_SOFT_SPEED is then used throughout the driver.

Unfortunatelly, due to a typo in the driver, instead of defining
CONFIG_SYS_I2C_SOFT_SPEED, an CONFIG_SYS_SOFT_I2C_SPEED was defined
and therefore the driver failed to compile. The same applies for
CONFIG_SYS_I2C_SOFT_SLAVE , where the swap happens as well.

This patch fixes the issue.

Signed-off-by: Marek Vasut 
Cc: Heiko Schocher

drivers/i2c: Update fti2c010.[ch], i2c_core.c to use SPDX identifiers

2013-07-25T12:51:42+00:00

Acked-by: Heiko Schocher 
Signed-off-by: Tom Rini

Merge branch 'master' of git://git.denx.de/u-boot-i2c

2013-07-24T13:50:24+00:00

The sandburst-specific i2c drivers have been deleted, conflict was just
over the SPDX conversion.

Conflicts:
	board/sandburst/common/ppc440gx_i2c.c
	board/sandburst/common/ppc440gx_i2c.h

Signed-off-by: Tom Rini

Add GPL-2.0+ SPDX-License-Identifier to source files

2013-07-24T13:44:38+00:00

Signed-off-by: Wolfgang Denk 
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini

i2c: add Faraday FTI2C010 I2C controller support

2013-07-23T06:34:58+00:00

Faraday FTI2C010 is a multi-function I2C controller
which supports both master and slave mode.
This patch simplily implements the master mode only.

Signed-off-by: Kuo-Jung Su 
CC: Heiko Schocher

I2C: mxc_i2c: Add support for Vybrid VF610 platform

2013-07-23T06:34:57+00:00

This patch adds support for Vybrid VF610 platform.

There are some differences between i.MX6 and Vybrid for I2C controller.
(1) The registers' offset are different.
(2) The I2C clock divider values are different.
(3) In I2C control register, the enable/disable/reset bit is inverted for Vybrid comparing to i.MX6.
(4) In I2C status register, the interrupt flag bit is cleared by writing "1" for Vybrid.
For i.MX6, this bit is cleared by writing "0".
(5) In I2C status register, the arbitration lost flag bit is cleared by writing "1" for Vybrid.
For i.MX6, this bit is cleared by writing "0".

Signed-off-by: Alison Wang