From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: enforce bitbanging for i2c
Date: Tue, 21 Aug 2012 11:07:54 +0200 [thread overview]
Message-ID: <20120821090754.GD5156@phenom.ffwll.local> (raw)
In-Reply-To: <87txvwboqy.fsf@intel.com>
On Tue, Aug 21, 2012 at 12:03:49PM +0300, Jani Nikula wrote:
> On Tue, 21 Aug 2012, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > Now that we have also have a workaround for crt to fallback to
> > bitbanging in some cases and then restore gmbus again, we need to
> > ensure that we don't try to enable gmbus on broken hw (like i830M).
> > Previously only sdvo had a bit-banging fallback, and sdvo is gen3+
> > only, so no issue with that.
> >
> > Enforce this by tracking separately whether gmbus even could work.
> >
> > This issue has been introduced in
> >
> > commit f1a2f5b7c5f0941d23eef0a095c0b99bf8d051e6
> > Author: Jani Nikula <jani.nikula@intel.com>
> > Date: Mon Aug 13 13:22:35 2012 +0300
> >
> > drm/i915: fall back to bit-banging if GMBUS fails in CRT EDID
> > reads
> >
> > Found by code-inspection, no bug report afaik.
>
> I don't see how my patch could enable or try GMBUS if force_bit has been
> set to true. On i830 the first attempt will be bit-banging, as before,
> and there will be no fallback because bit-banging is already enabled.
>
> I don't think this patch is necessary, but by all means prove me
> wrong. ;)
Right, I've missed the is_force_bit check in intel_crt_get_edid, patch is
not required.
/me hides
Cheers, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
prev parent reply other threads:[~2012-08-21 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 8:37 [PATCH] drm/i915: enforce bitbanging for i2c Daniel Vetter
2012-08-21 9:03 ` Jani Nikula
2012-08-21 9:07 ` Daniel Vetter [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=20120821090754.GD5156@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.kernel.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.