From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Marco Stornelli <marco.stornelli@coritel•it>
Cc: Linuxppc Embedded Mailing List <linuxppc-embedded@ozlabs•org>
Subject: Re: External Interrupt
Date: Fri, 01 Feb 2008 17:29:08 +0300 [thread overview]
Message-ID: <47A32CB4.6010309@ru.mvista.com> (raw)
In-Reply-To: <47A2D424.3090903@coritel.it>
Hello.
Marco Stornelli wrote:
> I used the linux kernel 2.6.10 with a processor MPC8548E. I wrote a
> driver for a device connected with the local bus. This device has an
> external interrupt. In the local bus driver I have used the macro
> MPC85xx_IRQ_EXT<X> to get the interrupt number and pass it to the
> driver and after that register the ISR. Now with a kernel 2.6.21 this
> macro isn't available because in the header file irq.h there is the
> option CONFIG_PPC_MERGE that disable those options. I think this
> problem is related to the migration of ppc code towards powerpc. I
> know that now there is the new device tree source file where I can add
> a device and its interrupt number but I think in this file I should
> describe only the platform device, and this device is not a platform
> device.
How comes that it's not platform device if it hangs off the local bus?
> Then, how can I get now this value? Is there some function to
> call? How can I perform this operation?
Probably irq_alloc_virt()...
WBR, Sergei
next prev parent reply other threads:[~2008-02-01 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 8:11 External Interrupt Marco Stornelli
2008-02-01 14:28 ` Sergei Shtylyov
2008-02-01 15:15 ` Marco Stornelli
2008-02-01 15:35 ` Sergei Shtylyov
2008-02-01 16:22 ` Marco Stornelli
2008-02-01 19:43 ` Scott Wood
2008-02-01 19:55 ` Jon Loeliger
2008-02-01 14:29 ` Sergei Shtylyov [this message]
2008-02-01 14:52 ` AW: " Lehmann, Hans (Ritter Elektronik)
-- strict thread matches above, loose matches on Subject: below --
2008-01-30 13:31 Marco Stornelli
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=47A32CB4.6010309@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=marco.stornelli@coritel$(echo .)it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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