From: ramdaspi@gmail.com
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] cyg_hal_interrupt_acknowledge function for MPC8xxx HAL
Date: Mon, 27 Aug 2007 07:40:00 -0000 [thread overview]
Message-ID: <20c673620708270040t431a2d81v16d0179daf1df5f7@mail.gmail.com> (raw)
Hi,
It seems there is a problem in clearing interrupts in function
cyg_hal_interrupt_acknowledge of the MPC8xxx HAL that would result in
simultaneous interrupts being missed.
If there were multiple interrupts being reported, all of them would
get cleared when only one is being acknowledged because we read the
value, OR it with the mask for acknowledged vector and then write this
value.
The documentation says we should write 1's to locations that need to
be cleared. So I believe there is no need for the read or 'OR'
operation. Just write the mask for the vector.
I our board we were missing one of the interrupts with the original
code. With the modification it is working correctly.
Cheers,
Ramdas
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-08-27 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 7:40 ramdaspi [this message]
2007-08-27 7:50 ` Andrew Lunn
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=20c673620708270040t431a2d81v16d0179daf1df5f7@mail.gmail.com \
--to=ramdaspi@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).