All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Felix Radensky <felix@embedded-sol.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: GPIO interrupt on AMCC 460EX
Date: Thu, 28 Aug 2008 17:20:13 +0200	[thread overview]
Message-ID: <200808281720.13138.sr@denx.de> (raw)
In-Reply-To: <48B6B201.2070101@embedded-sol.com>

Felix,

On Thursday 28 August 2008, Felix Radensky wrote:
> I'm writing a Linux driver for CPLD access on custom
> 460EX based board. CPLD generates interrupt, which
> is connected to GPIO pin 45. According to 460EX user
> manual, this pin, if configured as alternate function 3,
> will generate external interrupt 12, which is mapped into
> irq 20 on UIC3.  My question is - how do I get irq number
> suitable for passing to request_irq().

arch/powerpc now used virtual interrupts. You need to include this hardware 
interrupt number into your device-tree (create a new node for your CPLD) and 
extract the virtual irq number from there by calling irq_of_parse_and_map().

Best regards,
Stefan

  reply	other threads:[~2008-08-28 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 14:11 GPIO interrupt on AMCC 460EX Felix Radensky
2008-08-28 15:20 ` Stefan Roese [this message]
2008-08-28 21:47   ` Felix Radensky
2008-08-29 15:31     ` MPC8568MDS RAMDISK Problem SETTE AGOSTINO - technolabs
2008-08-29 18:03       ` Bhupender Saharan
2008-08-29 21:45       ` Anatolij Gustschin
2008-09-01  9:02         ` SETTE AGOSTINO - technolabs
2008-09-02 10:10           ` Anatolij Gustschin
2008-09-02 13:18             ` SETTE AGOSTINO - technolabs
2008-09-02 21:27               ` Anatolij Gustschin
2008-09-03  9:30                 ` SETTE AGOSTINO - technolabs

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=200808281720.13138.sr@denx.de \
    --to=sr@denx.de \
    --cc=felix@embedded-sol.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 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.