From: Jean Delvare <khali@linux-fr.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Paused I/O versus regular I/O
Date: Sat, 26 Nov 2005 16:40:25 +0100 [thread overview]
Message-ID: <20051126164025.66aae4f4.khali@linux-fr.org> (raw)
Hi all,
Could anyone tell me what the difference is between "paused" I/O
(inb_p, oub_p and friends) and regular I/O (inb, oub and friends)? I
understand that the former includes some delays here and there, but how
do I know when to use the paused variant, and when the non-paused
variant is OK?
The driver I am currently working on involves combined I/O access on
the Super-I/O ports (0x2e and 0x2f being the address and data ports,
respectively) and chip-specific combined I/O access (typically 0x295 and
0x296 being the address and data ports, respectively). I am using
regular (non-paused) I/O and it seems to work well, but I was wondering
if maybe combined I/O (when you write to a port to select an internal
address, then read the data from another port) was supposed to be done
using paused I/O.
Can anyone clarify the situation? I couldn't find any documentation
explaining *when* paused I/O must be used.
Thanks,
--
Jean Delvare
next reply other threads:[~2005-11-26 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 15:40 Jean Delvare [this message]
[not found] <5dato-1qR-9@gated-at.bofh.it>
2005-11-27 0:52 ` Bodo Eggert
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=20051126164025.66aae4f4.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.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®