From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kronos <kronos@people.it>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] radeonfb: DDC i2c fix
Date: Sat, 12 Mar 2005 10:52:17 +1100 [thread overview]
Message-ID: <1110585137.5751.122.camel@gaston> (raw)
In-Reply-To: <20050311201326.GA7379@dreamland.darkstar.lan>
On Fri, 2005-03-11 at 21:13 +0100, Kronos wrote:
> Il Fri, Mar 11, 2005 at 04:46:10PM +1100, Benjamin Herrenschmidt ha scritto:
> > The radeonfb code for DDC probing (like it's X.org counterpart) uses to
> > leave the DDC clock & data lines asserted after the probing is complete.
> > This causes problems with some Apple monitors like the new Cinema HD
> > 23", who will turn themselves off when that happens. This fixes it.
>
> Fix is correct, but comment is not ;) After the loop SCL and SDA are
> left low. Pulling them high puts the I2C bus in the stop condition.
Well, they are pull-up lines. I'm not pulling them high per-se, I'm
"releasing" them to their natural state, which is high ;) The ATI code
does some weird shit around the i2c transfer proper, and I don't know
exactly why. I don't have any spec about DDC2 though, my understand is
that it's more than just i2c EEPROM though. It used to leave the 2 lines
"assserted" at the end of the transfer (after the last stop condition)
and that sounded wrong and causes the misbehaviour on the Apple
display ...
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-11 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 5:46 [PATCH] radeonfb: DDC i2c fix Benjamin Herrenschmidt
2005-03-11 20:13 ` Kronos
2005-03-11 23:52 ` Benjamin Herrenschmidt [this message]
2005-03-12 1:06 ` Kronos
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=1110585137.5751.122.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=kronos@people.it \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).