public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: petr.jakes-VOAeGBCOg48@public.gmane.org
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: parport (i2c bus) maximum speed
Date: Fri, 13 Jun 2008 16:02:05 +0200	[thread overview]
Message-ID: <20080613160205.60b719c3@hyperion.delvare> (raw)
In-Reply-To: <c193ec310806130644p22c1e466g9cd6e6711d4b691b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Petr,

On Fri, 13 Jun 2008 15:44:12 +0200, Petr Jakeš wrote:
> I am thinking about to build an I2C-parport HW adapter. I would like to
> know, what is the maximum speed one can get on the I2C bus using parport HW
> adapter. I expect 100kbps is a standard speed but if it possible to go to
> 400k it will be great.
> If it is not possible to get 400kbps speed using the parport, other hints
> are appreciated of course :-)

Our current i2c-algo-bit implementation can't go faster than 250 kbps
by design. I think I remember trying it and it was working fine. But if
memory serves the actual speed ended up being significantly less than
250 kpbs, maybe 160 kbps. Just like you don't actually get 100 kbps
when you ask for 100 kbps. I guess that there's latency in switching
the parport pins, which becomes visible as the speed increases.

If you plan on doing fast I2C over parport, then I think you want to
give up on bit-banging and instead control an I2C master beyond the
parallel port. That way you take benefit of the parallel aspect of
parport and you should be able to reach 400 kbps. Using a chip we
already have abstracted support for (PCF8584 or PCA9564) this shouldn't
be too difficult.

-- 
Jean Delvare

_______________________________________________
i2c mailing list
i2c@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-06-13 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 13:44 parport (i2c bus) maximum speed Petr Jakeš
     [not found] ` <c193ec310806130644p22c1e466g9cd6e6711d4b691b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 14:02   ` Jean Delvare [this message]
     [not found]     ` <20080613160205.60b719c3-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 15:55       ` Petr Jakeš
     [not found]         ` <c193ec310806130855s2227f429pd151466a88539c90-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 17:17           ` Jean Delvare
     [not found]             ` <20080613191707.13731136-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 18:04               ` Petr Jakeš
     [not found]                 ` <c193ec310806131104wcbba767g602db89266492f31-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 20:56                   ` Jean Delvare
     [not found]                     ` <20080613225624.11ad3ece-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 22:32                       ` Petr Jakeš
     [not found]                         ` <c193ec310806131532o1e7a8bdasc4856aa09b90e9ae-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 20:37                           ` Jean Delvare
2008-06-23 19:51           ` Cyrille Derory

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=20080613160205.60b719c3@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=petr.jakes-VOAeGBCOg48@public.gmane.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