From: moreau francis <francis_moreau2000@yahoo.fr>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re : [I2C] question on adapter design
Date: Sat, 20 May 2006 11:07:39 +0000 (GMT) [thread overview]
Message-ID: <20060520110739.93343.qmail@web25811.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20060519102347.GM8304@mea-ext.zmailer.org>
>The I²C (TM Philips) -bus runs at 100 kHz or (high-speed one) at 400 kHz.
>An eight bit byte goes thru it in 80 or 20 microseconds depending on used
>speed. If your interrupt processing considers it as medium level
>priority and fills the Tx fifo with as much as is available (most I²C TX
>sequences do fit inside the 8 byte fifo) and collects as much data as is
>available in the Rx fifo, you should be well set.
ok so most of I2C commands shouldn't last more than 160 us when bus
runs at 400 khz, right ? If so, I'm not sure it worth to use interrupts because
an active polling would avoid context switch that is not negligible in that case.
Interrupts can be usefull if I2C transfers would be longer than 8 bytes...
>
>Most notable detail there is, that you do have those (for I²C) huge FIFOs.
>Another thing is (I haven't verified this) that I²C master controls the
>bus clock, and can stop it temporarily, when Tx FIFO is empty, or Rx FIFO
>is full.
>
Indeed, my controller can automatically stop the bus clock when Tx fifo is
empty or Rx fifo is full.
Francis
prev parent reply other threads:[~2006-05-20 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 8:42 moreau francis
2006-05-19 10:23 ` Matti Aarnio
2006-05-20 11:07 ` moreau francis [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=20060520110739.93343.qmail@web25811.mail.ukl.yahoo.com \
--to=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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
all inboxes | Powered by JetHome®