All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Yosemite/440EP is there a global interrupt enable mask?
Date: Wed, 25 Jan 2006 11:28:05 +0100	[thread overview]
Message-ID: <200601251128.05370.sr@denx.de> (raw)
In-Reply-To: <43D67AF6.6070403@ovro.caltech.edu>

Hi David,

On Tuesday 24 January 2006 20:07, David Hawkins wrote:
> I'm writing a simple driver to test IRQ handling on the
> AMCC Yosemite board. The board has an 8x2 header with several
> GPIO pins, a number of which can be configured as IRQ inputs.
>
> I have setup GPIO46 as output, and GPIO47 as input, and
> selected IRQ8 on that pin.

OK. So far good.

<snip>

> So, is there a kernel wide interrupt enable mask that I really
> should be using? Or, an interrupt enable API? I initially
> thought that when I registered an interrupt using
> request_irq() that the kernel would go off an enable the
> requested IRQ, but this test shows that it did not.

Yes, the request_irq() should enable the requested IRQ. You seem to have used 
the wrong IRQ number though. Please see below.

> #include <linux/module.h>   /* kernel modules                    */
> #include <linux/interrupt.h>/* request_irq(), etc                */
> #include <asm/io.h>         /* ioremap64(), iounmap(), readl()   */
>
> static char *name = "yosemite_irq";
> static unsigned long long base = 0x0EF600C00; // 36-bit address
> static unsigned int size = 0x44;
> static char *kernel;
> static int irq = 8;

You are using the "External IRQ 8". This results in IRQ number 19 of the 2nd 
interrupt controller of the 440ep. So please try (19+32) as the IRQ number 
upon requesting the interrupt.

Best regards,
Stefan

  reply	other threads:[~2006-01-25 10:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  0:45 [Patch 3/3] Add Yellowstone Platform defconfig John Otken
2006-01-24 18:08 ` Yosemite/440EP why are readl()/ioread32() setup to read little-endian? David Hawkins
2006-01-24 19:07   ` Yosemite/440EP is there a global interrupt enable mask? David Hawkins
2006-01-25 10:28     ` Stefan Roese [this message]
2006-01-25 18:30       ` David Hawkins
2006-01-25 18:55         ` Eugene Surovegin
2006-01-25 19:46           ` David Hawkins
2006-01-25 20:13             ` Eugene Surovegin
2006-01-25 20:34               ` David Hawkins
2006-01-25  9:57   ` Yosemite/440EP why are readl()/ioread32() setup to read little-endian? Stefan Roese
2006-01-25 18:26     ` David Hawkins
2006-01-25 18:51       ` Eugene Surovegin
2006-01-25 19:36         ` David Hawkins
2006-01-25 19:48           ` Eugene Surovegin
2006-01-26 10:20           ` Stefan Roese
2006-01-27  0:10             ` David Hawkins
2006-01-27 23:29             ` David Hawkins

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=200601251128.05370.sr@denx.de \
    --to=sr@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.