From: Tony Lindgren <tony@atomide.com>
To: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Cc: "Strashko, Grygorii" <grygorii.strashko@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: i2c issue on Panda with DT boot, v3.10-rc4
Date: Fri, 7 Jun 2013 11:36:29 -0700 [thread overview]
Message-ID: <20130607183628.GD3331@atomide.com> (raw)
In-Reply-To: <42EC710806A55841BBE342FAEBBEF172D26A1F@DNCE04.ent.ti.com>
* Valkeinen, Tomi <tomi.valkeinen@ti.com> [130607 11:37]:
> Tony Lindgren [tony@atomide.com]:
>
> > * Tomi Valkeinen <tomi.valkeinen@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, as that's "00". Everything after that are 'XX'es.
> >
> > Hmm I suggest git bisect, I'm pretty sure I was using my panda es
> > with my omap4 DT conversion patches against v3.10-rc1.
>
> As I mentioned, it doesn't work on v3.10-rc1 either. Note that DVI output
> itself works fine, it's the EDID read that fails. So if you force the
> videomode, you won't notice anything.
OK, that's probably I had it working.
> I didn't try with v3.9 (does DT boot work on that one?), though. So I don't
> know if reading EDID has ever worked with DT boot.
Yes but requires several fixes. Without fixes, v3.10-rc4 is your
best bet. Of course that won't help much with git bisect.
Maybe check that the i2c related pins are muxed properly for your board
with pinctrl-single?
Regards,
Tony
next prev parent reply other threads:[~2013-06-07 18:36 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
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 [this message]
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=20130607183628.GD3331@atomide.com \
--to=tony@atomide.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).