On 07/06/13 21:39, Felipe Balbi wrote:
sounds like there's something left in FIFO which is not getting read
out, then we end up timing out.
Can you try the patch below ? It's patch of a bigger patchset which I
still need to clean a few things up, but they should be very close to
being
On 07/06/13 21:36, Tony Lindgren wrote:
Maybe check that the i2c related pins are muxed properly for your board
with pinctrl-single?
Reading the bytes individually with i2cget works fine, so I think that
tells us that the pins are configured ok.
Tomi
signature.asc
Description: OpenPGP
* Tomi Valkeinen tomi.valkei...@iki.fi [130610 02:35]:
On 07/06/13 21:36, Tony Lindgren wrote:
Maybe check that the i2c related pins are muxed properly for your board
with pinctrl-single?
Reading the bytes individually with i2cget works fine, so I think that
tells us that the pins are
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,
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
On 07/06/13 15:36, Grygorii Strashko wrote:
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
* Tomi Valkeinen tomi.valkei...@ti.com [130607 05:53]:
On 07/06/13 15:36, Grygorii Strashko wrote:
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
---
HI,
On Fri, Jun 07, 2013 at 03:36:38PM +0300, Grygorii Strashko wrote:
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
Tony Lindgren [t...@atomide.com]:
* Tomi Valkeinen tomi.valkei...@ti.com [130607 05:53]:
With that one, I don't get timeouts, but it still doesn't work (i.e.
behavior is the same as on -rc1).
When I run i2cdump the first time, I see that it (probably) manages to
read the first byte,
* Valkeinen, Tomi tomi.valkei...@ti.com [130607 11:37]:
Tony Lindgren [t...@atomide.com]:
* Tomi Valkeinen tomi.valkei...@ti.com [130607 05:53]:
With that one, I don't get timeouts, but it still doesn't work (i.e.
behavior is the same as on -rc1).
When I run i2cdump the first
Hi,
On Fri, Jun 07, 2013 at 02:53:54PM +0300, 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
11 matches
Mail list logo
