From: Dmytro Bablinyuk <dmytro.bablinyuk@rftechnology.com.au>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 82xx IRQ handling
Date: Mon, 12 Dec 2005 17:00:46 +1100 [thread overview]
Message-ID: <439D120E.9010606@rftechnology.com.au> (raw)
In-Reply-To: <dc0620490d9bef30d3a4b629483cd3f9@embeddededge.com>
>
>> immap->im_intctl.ic_simrh &= ~(0x0800);
>
>
> You should not be messing around with this register
> in your code. The generic 82xx interrupt functions
> will properly manage this for you.
Thank you Dan,
It's working now!
By the way question - shall I program somewhere an edge of the IRQ or it
always triggers on the rising edge?
Also does anybody knows any source code example of using 82xx General
Purpose Timer Unit so that it triggers interrupt handler after some period.
Thank you
next prev parent reply other threads:[~2005-12-12 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 2:42 82xx IRQ handling Dmytro Bablinyuk
2005-12-12 5:01 ` Dan Malek
2005-12-12 6:00 ` Dmytro Bablinyuk [this message]
2005-12-12 14:28 ` Kumar Gala
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=439D120E.9010606@rftechnology.com.au \
--to=dmytro.bablinyuk@rftechnology.com.au \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).