linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tdz@users.sourceforge.net>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: Raise SDA for each received bit, if necessary
Date: Thu, 12 May 2016 18:19:12 +0200	[thread overview]
Message-ID: <5734AD00.3050904@users.sourceforge.net> (raw)
In-Reply-To: <20160512090544.GB1638@katana>

Hi

Am 12.05.2016 um 11:05 schrieb Wolfram Sang:
> Hi Thomas,
> 
> On Wed, Apr 27, 2016 at 08:11:54PM +0200, Thomas Zimmermann wrote:
>> Some I2C adapters don't raise SDA by themselves when sending a bit. This
>> behavior can be seen with the DDC channel of SiS 300 graphics cards.
> 
> I think you mean 'clients' or 'devices' here, not adapters (masters),
> right?

Yes, sorry.

> So, it seems you have a bus without a pull-up resistor (or a
> broken one?) but use now a push-pull design. This is against the I2C
> standard and for most circiuts quite dangerous as it can lead to
> shortcuts.

I see.

> Do you have any hints that the bus is designed this way? In which driver
> do you want to use the new flag?

I was playing with the DRM framework and an old SiS graphics card. I
discovered this issue while trying to read the EDID from the monitor.

I have a few other SiS cards/models here and they all expose this
behavior. So I guess it's intentional(==cheaper?), although the HW docs
don't seem mention it explicitly.

Best regards
Thomas

> 
> Thanks,
> 
>    Wolfram
> 


-- 
GnuPG:          http://tdz.users.sourceforge.net/tdz.asc
Fingerprint:    16FF F599 82F8 E5AA 18C6 5220 D9DA D7D4 4EF1 DF08

  reply	other threads:[~2016-05-12 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 18:11 [PATCH] i2c: Raise SDA for each received bit, if necessary Thomas Zimmermann
2016-05-12  9:05 ` Wolfram Sang
2016-05-12 16:19   ` Thomas Zimmermann [this message]
2016-05-13 10:33     ` Wolfram Sang
2016-05-13 16:06       ` Thomas Zimmermann

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=5734AD00.3050904@users.sourceforge.net \
    --to=tdz@users.sourceforge.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).