linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: AMCC PPC460EX Canyonlands Hardwired interrupt
Date: Tue, 26 Aug 2008 10:00:27 +0200	[thread overview]
Message-ID: <200808261000.27333.sr@denx.de> (raw)
In-Reply-To: <02f101c9074f$26d2cd90$0109220a@deltatau.local>

On Tuesday 26 August 2008, Henry Bausley wrote:
> How do I go about using one of the gpio pins for my own interrupt with the
> Canyonlands board.  Previously I used a yosemite (ppc) board and modified
> the yosemite.c file so that IRQ0 and IRQ1 were edge sensitive and and stole
> the ETH0/1 phy hardware interrupts for my own purposes and everything
> worked.
>
> I am trying to do the same with the Canyonlands (powerpc) board.but cannot
> seem to enable the interrupt.

arch/powerpc now uses virtual interrupts instead of the physical interrupts 
used in arch/ppc. So you can't just use the physical interrupt number in your 
request_irq() anymore. You need an of-platform driver to generate the virtual 
interrupt from the physical interrupt in the device-tree 
(irq_of_parse_and_map()). And you need to add this new node with the 
interrupt property to your device-tree of course.

Best regards,
Stefan

      reply	other threads:[~2008-08-26  8:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22  4:53 [PATCH] AMCC PPC460GT/EX PCI-E de-emphasis adjustment fix fkan
2008-08-22 13:30 ` Josh Boyer
2008-08-22 15:33   ` Feng Kan
2008-08-22 19:44   ` Stefan Roese
2008-08-26  7:41     ` AMCC PPC460EX Canyonlands Hardwired interrupt Henry Bausley
2008-08-26  8:00       ` Stefan Roese [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=200808261000.27333.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 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).