dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29787] [RADEON:KMS::EDID] i2c bit banging + preempt kernel -> i2c failure (random XRandR failures)
Date: Sat, 21 May 2011 04:31:35 -0700 (PDT)	[thread overview]
Message-ID: <20110521113135.F40A113004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29787-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=29787

--- Comment #18 from Ville Syrjala <syrjala@sci.fi> 2011-05-21 04:31:35 PDT ---
(In reply to comment #15)
> (In reply to comment #14)
> > Grumble. So, how will this be fixed? Sprinkle the code with
> > preempt_disable()/enable() pairs? Advise all users (well, me) to disable
> > preemption? Change the code so it no longer acts on intermittent EDID failures?
> > Ask your colleagues to design sane hardware that doesn't rely on software
> > interaction for timing-critical operations ;) ?
> > 
> > FWIW, I'm perfectly happy to disable preemption in my kernel, haven't run a
> > distro-provided kernel since 2.6.27. But your explanation sounds like this
> > could bite a lot more users than just me.
> 
> It has nothing to do with the hw, it's the nature of i2c.  All drivers that use
> bit banging i2c (hwmon, v4l, lots of embedded stuff) would potentially be
> affected.

If the EEPROM supports clock stretching I see no reason why bit banging would
fail.

I got these timeout errors on one system at some point. I had an idea for a
possible fix, but I never got around to testing it. I'll attach the patch.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-05-21 11:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 19:54 [Bug 29787] New: random XRandR failures (i2c related?) bugzilla-daemon
2010-08-28 12:39 ` [Bug 29787] " bugzilla-daemon
2010-08-29  0:14 ` bugzilla-daemon
2010-08-29 16:48 ` bugzilla-daemon
2010-08-29 16:54 ` bugzilla-daemon
2010-08-29 21:48 ` bugzilla-daemon
2010-08-30 14:45 ` bugzilla-daemon
2010-08-30 14:48 ` bugzilla-daemon
2010-09-01 21:59 ` bugzilla-daemon
2010-09-17  9:19 ` bugzilla-daemon
2010-10-05  3:38 ` bugzilla-daemon
2010-10-23 11:49 ` bugzilla-daemon
2010-11-19 11:31 ` bugzilla-daemon
2010-11-19 15:30 ` bugzilla-daemon
2010-11-20 13:13 ` bugzilla-daemon
2010-11-20 17:10 ` bugzilla-daemon
2011-02-09 16:05 ` [Bug 29787] [RADEON:KMS::EDID] i2c bit banging + preempt kernel -> i2c failure (random XRandR failures) bugzilla-daemon
2011-02-10 11:30 ` bugzilla-daemon
2011-05-21 10:35 ` bugzilla-daemon
2011-05-21 11:31 ` bugzilla-daemon [this message]
2011-05-21 11:32 ` bugzilla-daemon
2019-11-19  8:15 ` bugzilla-daemon

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=20110521113135.F40A113004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 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).