public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Mike Sweeney" <msweeney77@gmail.com>
To: ecos-discuss@ecos.sourceware.org, msweeney77@gmail.com
Subject: [ECOS] HAL_INTERRUPT_ACKNOWLEDGE question
Date: Thu, 07 Jun 2007 09:14:00 -0000	[thread overview]
Message-ID: <70d4f620706062016s593a05aen95aebfdad3f4ecf@mail.gmail.com> (raw)

I am a little confused about what HAL_INTERRUPT_ACKNOWLEDGE is
intended to do. The reference manual for eCos says that it is used if
the interrupt controller requires you to acknowledge an interrupt. The
reason I am confused is that an interrupt service routine for a device
may need to clear a status flag in a peripheral status register even
if there is no interrupt controller. Is the intent that each interrupt
service routine handle this clearing of the flag in the peripheral
status register on its own, in addition to calling
HAL_INTERRUPT_ACKNOWLEDGE for handling anything that has to do with
the interrupt controller? It seems this is the case, but why is there
this special function in the HAL for handling the interrupt controller
acknowledgement? Why isn't this just handled directly by each device's
interrupt service routine without going through this interface?

The hal_clock_reset() function makes it quite clear to me that each
ISR handles any status flags itself, because this is the only way the
ISR for the real time clock could be made generic as it is in the
kernel by calling hal_clock_reset() in addition to calling
HAL_INTERRUPT_ACKNOWLEDGE().

Thanks.

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2007-06-07  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  9:14 Mike Sweeney [this message]
2007-06-07 10:01 ` Daniel Helgason
2007-06-07 11:55   ` Daniel Helgason
2007-06-07 15:11 ` Nick Garnett
2007-06-07 17:02   ` Mike Sweeney

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=70d4f620706062016s593a05aen95aebfdad3f4ecf@mail.gmail.com \
    --to=msweeney77@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).