BMC/Intel-BMC/linux.git/drivers/i2c, branch dev-4.6

i2c/aspeed: Do not enable SMBUS Alert IRQ

2016-07-12T09:59:33+00:00

We do not handle this in our driver, so do not enable the IRQ. TODO: Investigate why the whiterspoon board was asserting this IRQ. Signed-off-by: Joel Stanley

drivers/i2c/i2c-aspeed: Only use IRQ status for command completion notification

2016-07-12T09:59:24+00:00

We currently determine if an i2c command as complete by looking at the command register (and comparing it with the pending set of commands). While this may indicate that all pending commands have completed, we may still get a further interrupt when multiple commands (like a read + stop) have been queued. This change uses the interrupt status to indicate command completion, instead of the command register. Signed-off-by: Jeremy Kerr Signed-off-by: Joel Stanley

i2c/aspeed: Print error when failing to get clock

2016-06-03T20:52:05+00:00

This was a drv_dbg, but it's really an error. Signed-off-by: Joel Stanley

i2c: Add driver for ast2400 i2c master

2016-06-03T20:51:41+00:00

- Rip out slave mode code - Use per-adapter device - Use separate controller & bus platform devices, use an irq controller for busses - Don't send stop when we're not done Signed-off-by: Joel Stanley Signed-off-by: Jeremy Kerr Signed-off-by: Milton Miller

i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

2016-04-22T13:31:54+00:00

The exynos5 I2C controller driver always prepares and enables a clock before using it and then disables unprepares it when the clock is not used anymore. But this can cause a possible ABBA deadlock in some scenarios since a driver that uses regmap to access its I2C registers, will first grab the regmap lock and then the I2C xfer function will grab the prepare lock when preparing the I2C clock. But since the clock driver also uses regmap for I2C accesses, preparing a clock will first grab the prepare lock and then the regmap lock when using the regmap API. An example of this happens on the Exynos5422 Odroid XU4 board where a s2mps11 PMIC is used and both the s2mps11 regulators and clk drivers share the same I2C regmap. The possible deadlock is reported by the kernel lockdep: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sec_core:428:(regmap)->lock); lock(prepare_lock); lock(sec_core:428:(regmap)->lock); lock(prepare_lock); *** DEADLOCK *** Fix it by leaving the code prepared on probe and use {en,dis}able in the I2C transfer function. This patch is similar to commit 34e81ad5f0b6 ("i2c: s3c2410: fix ABBA deadlock by keeping clock prepared") that fixes the same bug in other driver for an I2C controller found in Samsung SoCs. Reported-by: Anand Moon Signed-off-by: Javier Martinez Canillas Reviewed-by: Anand Moon Reviewed-by: Krzysztof Kozlowski Signed-off-by: Wolfram Sang Cc: stable@kernel.org

i2c: cpm: Fix build break due to incompatible pointer types

2016-04-22T13:25:53+00:00

Since commit ea8daa7b9784 ("kbuild: Add option to turn incompatible pointer check into error"), assignments from an incompatible pointer types have become a hard error, eg: drivers/i2c/busses/i2c-cpm.c:545:91: error: passing argument 3 of 'dma_alloc_coherent' from incompatible pointer type Fix the build break by converting txdma & rxdma to dma_addr_t. Signed-off-by: Michael Ellerman Signed-off-by: Wolfram Sang Cc: stable@kernel.org Fixes: ea8daa7b9784

i2c: ismt: Add Intel DNV PCI ID

2016-04-12T21:44:16+00:00

Intel DNV has the same iSMT SMBus host controller than Intel Avoton. Add DNV PCI ID to the list of supported devices. Signed-off-by: Mika Westerberg Acked-by: Andy Shevchenko Acked-by: Neil Horman Signed-off-by: Wolfram Sang

i2c: xlp9xx: add support for Broadcom Vulcan

2016-04-12T21:40:11+00:00

The Broadcom Vulcan ARM64 processor uses the same I2C controller present on the Broadcom XLP9xx/5xx MIPS processor family. Updated the Kconfig by adding ARCH_VULCAN option. Signed-off-by: Tanmay Jagdale Signed-off-by: Wolfram Sang

i2c: rk3x: add support for rk3228

2016-04-12T21:34:44+00:00

Enable the I2C core for this SoC. Signed-off-by: Yakir Yang Reviewed-by: Heiko Stuebner Acked-by: Rob Herring Signed-off-by: Wolfram Sang

i2c: jz4780: really prevent potential division by zero

2016-04-09T06:36:44+00:00

Make sure we avoid a division-by-zero OOPS in case clock-frequency is set too low in DT. Add missing '\n' while we are here. Signed-off-by: Wolfram Sang Acked-by: Axel Lin