The dma_mapping_error() function returns true if there is an error, it
doesn't return an error code. We should return -ENOMEM.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/i2c/busses/i2c-xgene-slimpro.c
b/drivers/i2c/busses/i2c-xgene-slimpro.c
index
Instead of having each i2c driver individually parse device tree data in
case it or platform supports separate wakeup interrupt, and handle
enabling and disabling wakeup interrupts in their power management
routines, let's have i2c core do that for us.
Platforms wishing to specify separate wakeup
From: Uwe Kleine-König mailto:u.kleine-koe...@pengutronix.de Sent: Thursday,
August 13, 2015 4:15 PM
To: Gao Pan-B54642
Cc: w...@the-dreams.de; linux-i2c@vger.kernel.org; Li Frank-B20596; Duan
Fugang-B38611
Subject: Re: [Patch v2] i2c: imx: implement bus recovery
Hello,
On Fri, Jul 17,
2015-08-18 17:12 GMT+08:00 Dan Carpenter dan.carpen...@oracle.com:
The dma_mapping_error() function returns true if there is an error, it
doesn't return an error code. We should return -ENOMEM.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Reviewed-by: Axel Lin axel@ingics.com
--
HI,
On Mon, Aug 17, 2015 at 06:28:11PM -0700, Matt Reimer wrote:
This doesn't seem to work for higher speeds, like 2.6 MHz. hssclh and
hsscll end up going negative.
My case is an OMAP3 trying to configure i2c1 at 2.6 MHz, on which it talks
to TPS65950. I end up with the following values:
unused-but-set-variable by default. How did you enable this warning without
being flooded by the warnings? (I tried W=1)
I use W=1. To prevent flooding, I used to replace all -I with -isystem
in the Kernel Makefile, but sadly this doesn't work anymore. And I had
no time to investigate why.
From: Ryo Kataoka ryo.kataoka...@renesas.com
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