From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: i2c issue on Panda with DT boot, v3.10-rc4
Date: Fri, 7 Jun 2013 15:36:38 +0300 [thread overview]
Message-ID: <51B1D3D6.2020803@ti.com> (raw)
In-Reply-To: <51B1C9D2.6060703@ti.com>
hi Tomi,
On 06/07/2013 02:53 PM, Tomi Valkeinen wrote:
> Hi,
>
> I was testing DT boot with 3.10-rc1 and Pandaboard, and couldn't get the
> DVI output's EDID reading to work. Testing with i2cget and i2cdump, I
> see that I can read individual bytes with i2cget, but using i2cdump
> doesn't work, it just shows 'XX'es.
>
> The same issue is there with 3.10-rc4, although with that one I get
> timeouts with i2cdump, whereas there were no timeouts with -rc1.
>
> # i2cget -y 2 0x50 0x10
> 0x0a
> # i2cget -y 2 0x50 0x20
> 0x0f
> # i2cget -y 2 0x50 0x30
> 0x01
> # i2cget -y 2 0x50 0x40
> 0x36
> # i2cget -y 2 0x50 0x50
> 0x4c
> # i2cdump -y 2 0x50
> No size specified (using byte-data access)
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: 00 [ 72.814086] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 73.825134] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 74.835327] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 76.097167] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 77.160736] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 78.174682] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 79.194824] omap_i2c 48060000.i2c: timeout waiting for bus ready
> XX [ 80.242980] omap_i2c 48060000.i2c: timeout waiting for bus ready
>
> i2cdump works fine with non-DT boot (but the i2c bus number is 3).
>
> Any ideas?
>
> Tomi
>
Could you check if below change will help you, pls?
iff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 13d1eca..66a62e7 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -615,11 +615,11 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
if (dev->cmd_err & OMAP_I2C_STAT_NACK) {
if (msg->flags & I2C_M_IGNORE_NAK)
return 0;
- if (stop) {
- w = omap_i2c_read_reg(dev, OMAP_I2C_CON_REG);
- w |= OMAP_I2C_CON_STP;
- omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
- }
+
+ w = omap_i2c_read_reg(dev, OMAP_I2C_CON_REG);
+ w |= OMAP_I2C_CON_STP;
+ omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
+
return -EREMOTEIO;
}
return -EIO;
-grygorii
next prev parent reply other threads:[~2013-06-07 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:53 i2c issue on Panda with DT boot, v3.10-rc4 Tomi Valkeinen
2013-06-07 12:36 ` Grygorii Strashko [this message]
2013-06-07 12:47 ` Tomi Valkeinen
2013-06-07 17:57 ` Tony Lindgren
2013-06-07 18:31 ` Valkeinen, Tomi
2013-06-07 18:36 ` Tony Lindgren
2013-06-10 9:29 ` Tomi Valkeinen
2013-06-10 14:28 ` Tony Lindgren
2013-06-07 18:26 ` Felipe Balbi
2013-06-07 18:39 ` Felipe Balbi
2013-06-10 9:26 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51B1D3D6.2020803@ti.com \
--to=grygorii.strashko@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).