All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Eno 3 Compton <one@ecom.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: irq identification has changed from 2.6.10 to 2.6.23. an explanation is requested
Date: Wed, 10 Oct 2007 15:47:32 -0500	[thread overview]
Message-ID: <470D3A64.2000507@freescale.com> (raw)
In-Reply-To: <f6c0dc290710101339t30a15881t3ffbe02324006b28@mail.gmail.com>

Eno 3 Compton wrote:
> I had a driver working under 2.6.10 on a mpc8248. The kernel got changed 
> under me to 2.6.23. Now, when I call request_irq with SIU_INT_IRQ5, 
> which is defined in asm-powerpc/irq.h, and once compiled and worked 
> properly, I get compilation errors. The compiler can't find the symbol 
> definition because CONFIG_PPC_MERGE  is defined. I suspect the kernel 
> guys have migrated things to a new arrangement, which I've been unable 
> to discern.
> 
> An explanation or advice on where to find information about this would 
> be hugely appreciated.

Ideally, you should put whatever device you're trying to drive in the 
device tree, and use of_irq_to_resource() on the device node to find the 
virtual IRQ number.

Failing that, you can call irq_find_mapping(), but you'll need to either 
pass in the device node of the relevant interrupt controller, or call 
irq_set_default_host() -- but really, it's better to just use the device 
tree.

-Scott

      reply	other threads:[~2007-10-10 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 20:39 irq identification has changed from 2.6.10 to 2.6.23. an explanation is requested Eno 3 Compton
2007-10-10 20:47 ` 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=470D3A64.2000507@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=one@ecom.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 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.