linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: liran raz <liranrazlinux@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: which irqflag to use with request_irq
Date: Tue, 09 Dec 2008 12:23:35 -0600	[thread overview]
Message-ID: <493EB7A7.7060608@freescale.com> (raw)
In-Reply-To: <e3b3ab5c0812090800m760e2ef8p5ee2f9120fb2fce4@mail.gmail.com>

liran raz wrote:
> hi,
> 
> When using the function:
> int request_irq (unsigned int      irq,
>      irq_handler_t      handler,
>      unsigned long      irqflags,
>      const char *      devname,
>      void *      dev_id);
> 
> To connect an ISR to one of the processor's
> peripherals irq (SCC in my case).
> 
> Which value I should use for irqflags,
> from the list in: interrupt.h file.

Just pass zero (or IRQF_SHARED if the IRQ is shared, but it shouldn't be 
in this case).

-Scott

      reply	other threads:[~2008-12-09 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 16:00 which irqflag to use with request_irq liran raz
2008-12-09 18:23 ` Scott Wood [this message]

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=493EB7A7.7060608@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=liranrazlinux@gmail.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).