From: Steven Newbury <steve@snewbury.org.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Reset GMBUS controller after NAK
Date: Sat, 02 Apr 2011 22:50:12 +0100 [thread overview]
Message-ID: <1301781012.1996.2.camel@Nokia-N900> (raw)
In-Reply-To: <1301585609.2051.5.camel@Nokia-N900>
----- Original message -----
> ----- Original message -----
> > On Thu, 31 Mar 2011 16:16:27 +0100, Steven Newbury
> > <steve@snewbury.org.uk> wrote:
> > > ----- Original message -----
> > > > On Wed, 30 Mar 2011 17:07:11 +0100
> > > > Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > > >
> > > > > Once a NAK has been asserted by the slave, we need to reset the
> > > > > GMBUS controller in order to continue. This is done by asserting
> > > > > the Software Clear Interrupt bit and then clearing it again to
> > > > > restore operations.
> > > > >
> > > > > If we don't clear the NAK, then all future GMBUS xfers will fail,
> > > > > including DDC probes and EDID retrieval.
> > > > >
> > > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=35781
> > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > > ---
> > > >
> > > > This one fixes the issue I was seeing on my HP test machine; LVDS
> > > > DDC probing seems to work ok once this fix is applied.
> > > >
> > > > --
> > > Could this be related to my inability to successfully probe the
> > > ch7036 with the ChromeOS Chrontel driver? Is it worth me testing it
> > > again with this patch applied? (I'm currently waiting to hear back
> > > from Zotac, my board supplier)
> >
> > Hmm. Depends, but unlikely. I would have thought the nm10_gpio driver
> > you were using used it's only bitbanging on the GPIO lines rather than
> > GMBUS. If in doubt, disable the use of GMBUS by
> >
> The GPIO is only used for HDMI hotplug detection, chip communication
> goes via i2c, or at least would if I could get it working... :-(
Since I pulled in drm-fixes I get different behaviour when probing for the ch7036, in my kernel log I now get:
[drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[drm] GMBUS timed out, falling back to bit banging on pin 4 [i915 gmbus dpc]
[drm] GMBUS timed out, falling back to bit banging on pin 5 [i915 gmbus dpb]
[drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[drm] GMBUS timed out, falling back to bit banging on pin 7 [i915 gmbus dpd]
The probe still fails, on some i2c buses I get as before:
XAUTHORITY=/home/mythtv/.Xauthority ./ch7036_monitor -v -p -d/dev/i2c-2
./ch7036_monitor: starts
Found device ID 0xff
./ch7036_monitor: Fatal: Device ID 0xff not the expected 0x56
whilst on others:
XAUTHORITY=/home/mythtv/.Xauthority ./ch7036_monitor -v -p -d/dev/i2c-4
./ch7036_monitor: starts
Write byte fail (3, 03, 04): No such device or addressFound device ID 0xffffffff
./ch7036_monitor: Fatal: Device ID 0xffffffff not the expected 0x56
prev parent reply other threads:[~2011-04-02 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 16:07 [PATCH] drm/i915: Reset GMBUS controller after NAK Chris Wilson
2011-03-30 16:48 ` Keith Packard
2011-03-30 16:59 ` Chris Wilson
2011-03-30 17:22 ` Keith Packard
2011-03-30 17:42 ` Chris Wilson
2011-03-30 17:56 ` Keith Packard
2011-03-30 20:05 ` Jesse Barnes
2011-03-31 15:16 ` Steven Newbury
2011-03-31 15:20 ` Chris Wilson
2011-03-31 15:33 ` Steven Newbury
2011-04-02 21:50 ` Steven Newbury [this message]
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=1301781012.1996.2.camel@Nokia-N900 \
--to=steve@snewbury.org.uk \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.