The Allwinner A10 compatibles were following a slightly different compatible
patterns than the rest of the SoCs for historical reasons. Move to the other
pattern for consistency across all Allwinner Socs.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
Hi,
This is the third version of the i2c compatible changes.
Changes from v2:
- rebased on top of current i2c/for-next
Maxime Ripard (2):
i2c: sunxi: Change i2c compatibles
ARM: sunxi: dt: Convert to the new i2c compatibles
Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt | 2 +-
When using device-tree and the i2c-gpio driver is called before the
GPIO node has been probed then it needs to correctly defer the probe
instead of returning a permanent error that the gpio numbers are not
valid.
This fixes the following error:
/i2c@2: invalid GPIO pins, sda=-517/scl=-517
On Thu, Mar 13, 2014 at 11:37:22AM +, Maxime Ripard wrote:
The Allwinner A10 compatibles were following a slightly different compatible
patterns than the rest of the SoCs for historical reasons. Move to the other
pattern for consistency across all Allwinner Socs.
Dropping support for the
On Thu, Mar 06, 2014 at 01:36:06PM +, David Howells wrote:
The SMBUS tracepoints can be enabled thusly:
echo 1 /sys/kernel/debug/tracing/events/i2c/enable
and will dump messages that can be viewed in /sys/kernel/debug/tracing/trace
that look like:
... smbus_read:
On Thu, Mar 13, 2014 at 02:37:38PM +, Ben Dooks wrote:
When using device-tree and the i2c-gpio driver is called before the
GPIO node has been probed then it needs to correctly defer the probe
instead of returning a permanent error that the gpio numbers are not
valid.
This fixes the
On Tue, Mar 11, 2014 at 10:21:57AM +0900, Jingoo Han wrote:
Add CONFIG_PM_SLEEP to suspend/resume functions to fix the following
build warning when CONFIG_PM_SLEEP is not selected. This is because
sleep PM callbacks defined by SIMPLE_DEV_PM_OPS are only used when
the CONFIG_PM_SLEEP is
On Tue, Mar 11, 2014 at 10:22:59AM +0900, Jingoo Han wrote:
Remove unnecessary cast of void pointer, because 'algo_data' of
'struct i2c_adapter' is a void pointer. Casting the void pointer
is redundant. The conversion from void pointer to any other
pointer type is guaranteed by the C
Hi Wolfram,
On Mon, Mar 10, 2014 at 08:55:58AM +0100, Wolfram Sang wrote:
+#include linux/platform_data/efm32-i2c.h
Shouldn't a new platform like efm32 be DT only?
it is, at least in mainline. My (not very strong) POV is that it's not
much effort/code size to support both. I dropped the
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi
b/arch/arm/boot/dts/sun7i-a20.dtsi
index 4cc2f5f2ecad..c1fd510fd2c4 100644
--- a/arch/arm/boot/dts/sun7i-a20.dtsi
+++ b/arch/arm/boot/dts/sun7i-a20.dtsi
@@ -762,7 +762,7 @@
};
i2c0: i2c@01c2ac00 {
-
On Sun, Feb 09, 2014 at 07:47:40PM +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger rich...@nod.at
BTW I updated the commit message to be more proper IMO (you didn't
actually remove the symbol, no?)
===
i2c: Remove usage of orphaned
Linus,
here is a Kconfig fix for the I2C subsystem. Please pull.
Thanks,
Wolfram
The following changes since commit fa389e220254c69ffae0d403eac4146171062d08:
Linux 3.14-rc6 (2014-03-09 19:41:57 -0700)
are available in the git repository at:
Hi,
I'll be away from the net and emails from March, 14th until March, 23rd.
For urgent matters, I'll trust the I2C mailing list to take care.
Kind regards,
Wolfram
signature.asc
Description: Digital signature
it is, at least in mainline. My (not very strong) POV is that it's not
much effort/code size to support both. I dropped the non-DT part, it's
easily readded if need should arise.
Thanks, I think it simplifies the review for this first (public)
iteration of the driver.
+ break;
Hi Wolfram,
On Thu, Mar 13, 2014 at 11:14:33PM +0100, Wolfram Sang wrote:
Huh? Is this an accepted binding? Doesn't look like it because of a
generic name and IMO a specific use-case. BTW the binding documentation
for this driver is missing.
Regarding the generic name: I don't care
This bus driver supports the QUP i2c hardware controller in the Qualcomm SOCs.
The Qualcomm Universal Peripheral Engine (QUP) is a general purpose data path
engine with input/output FIFOs and an embedded i2c mini-core. The driver
supports FIFO mode (for low bandwidth applications) and block mode
From: Ivan T. Ivanov iiva...@mm-sol.com
The Qualcomm Universal Peripherial (QUP) wraps I2C mini-core and
provide input and output FIFO's for it. I2C controller can operate
as master with supported bus speeds of 100Kbps and 400Kbps.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
[bjorn:
This fifth revision of the QUP I2C driver comes with minor fixes, as per review
comments on the second third revision.
Regards,
Bjorn
Changes from second v3:
- Reformat device tree binding description related to clocks
- Minor cleanup related to dt parsing of clock frequency
- Properly return
18 matches
Mail list logo
