From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How to make a Interrupt driven serial port driver?
Date: Sun, 29 Oct 2000 18:28:00 -0000 [thread overview]
Message-ID: <007701c04219$5ab4d530$0301a8c0@leopard> (raw)
In-Reply-To: <39FC9A15.8DBAA00C@redhat.com>
> Look at the end of the serial driver, above the DSR. Here's what it says:
>
> // Note: This device presents a single interrupt for both channels. Thus
> the
> // interrupt handler has to query the device and decide which channel
needs
> service.
>
> and indeed in the code:
>
>
> stat = scc_read_ctl(port, R3);
> if (stat & (RR3_AExt | RR3_ATxIP | RR3_ARxIP)) {
> chan = vrc4373_chans[0]; // Hardware channel A
> vrc4373_int(chan, stat>>3); // Handle interrupt
> } else if (stat & (RR3_BExt | RR3_BTxIP | RR3_BRxIP)) {
> chan = vrc4373_chans[1]; // Hardware channel A
> vrc4373_int(chan, stat); // Handle interrupt
> } else {
>
> Although the second comment is wrong (it should be channel A then channel
> B, not two channel A's obviously) - I'll fix that now.
>
> So in fact it should already be interrupt driven.
>
> Or instead are you asking for some sort of automatic notification to your
> application when data arrives?
>
Yeah, exactly, what I am asking is how to make a kind of automatic
notification to my application, so that my own serial port handler can
continue process that data when data arrives. Any clue? Thanks!
Rgds,
-Ling
next prev parent reply other threads:[~2000-10-29 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 17:53 Ling Su
2000-10-29 13:43 ` Jonathan Larmour
2000-10-29 18:28 ` Ling Su [this message]
2000-10-29 19:02 ` Jonathan Larmour
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='007701c04219$5ab4d530$0301a8c0@leopard' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).