From: "Tehn Yit Chin" <tehn.yit.chin@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: interrupt handlers PowerPC via GCC
Date: Tue, 25 Mar 2008 10:03:51 +1100 [thread overview]
Message-ID: <bf04f99c0803241603v3151865eic80b58a04bce43e2@mail.gmail.com> (raw)
In-Reply-To: <47E29C60.10300@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hey Scott,
Thanks for the reply, I shall investigate further.
I wasn't talking about interrupt handlers in Linux as such, but using
powerpc-eabi-gcc to write an ISR for the MPC5516. (I guess that could be
off-topic on this mailing list, but I thought the folks on this mailing list
would probably know the answer pretty easily). I was hoping that gcc would
generate the prologue and epilogue code for me via the interrupt attributes.
Many thanks.
Tehn Yit Chin
On Fri, Mar 21, 2008 at 4:18 AM, Scott Wood <scottwood@freescale.com> wrote:
> Tehn Yit Chin wrote:
> > Hi all,
> >
> > Apologies for such a basic question. I am trying to write an ISR on a
> > MPC551x. When I tried to use the interrupt attribute with
> > powerpc-eabi-gcc such as
> >
> > _attribute_((interrupt_handler)) foobarISR(void)
> > {
> > }
>
> Assuming you're talking about an interrupt handler in Linux, you don't
> need to do anything like that. The actual interrupt entry is assembly
> code. Search existing drivers for "irqreturn_t" to find examples of
> what an interrupt handler looks like, and "request_irq" for how to hook
> the handler into the interrupt.
>
> -Scott
>
[-- Attachment #2: Type: text/html, Size: 1586 bytes --]
next prev parent reply other threads:[~2008-03-24 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 0:06 interrupt handlers PowerPC via GCC Tehn Yit Chin
2008-03-20 17:18 ` Scott Wood
2008-03-24 23:03 ` Tehn Yit Chin [this message]
2008-03-26 2:50 ` David H. Lynch Jr.
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=bf04f99c0803241603v3151865eic80b58a04bce43e2@mail.gmail.com \
--to=tehn.yit.chin@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.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 NNTP newsgroup(s).