From: Scott Wood <scottwood@freescale.com>
To: "Muller, Ralf (NSN - FI/Espoo)" <ralf.muller@nsn.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Virtual IRQs on 82xx
Date: Thu, 28 Aug 2008 11:27:00 -0500 [thread overview]
Message-ID: <48B6D1D4.7020202@freescale.com> (raw)
In-Reply-To: <F9730D1BBC18E749AE72728B74D189E968356A@FIESEXC006.nsn-intra.net>
Muller, Ralf (NSN - FI/Espoo) wrote:
> I'm using a 8247 custom board and kernl 2.6.21.7
I strongly recommend using something newer. There was a lot of 82xx
work going on around that time.
> on the arch/powerpc
> branch. Here the irq are virtualized in the irq map functions now I'm
> facing several problems.
>
> * I have to manually call irq_create_of_mapping for each CPM interrupt
What's wrong with irq_of_parse_and_map()?
> And the major problem is:
> Now the kernel mixes virtual- and HW-IRQs, e.g. request_irq works with
> HW_IRQs but the interrupt handler with virtual interrupts, which can't work.
No, request_irq works with virtual interrupts as well.
> For some reason even on a powerpc the first 16 interrupts are reserved
> for legacy (PC) IRQs,
Right, there are powerpc systems with the same legacy interrupts and the
same ISA drivers that expect to be able to use ISA IRQs directly as virqs.
> so the easiest mapping HW-IRQ0 -> VIRQ16 a.s.o
The "easiest mapping" is whatever the IRQ subsystem gives you. This
isn't something that should be hardcoded.
-Scott
prev parent reply other threads:[~2008-08-28 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 6:37 Virtual IRQs on 82xx Muller, Ralf (NSN - FI/Espoo)
2008-08-28 16:27 ` 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=48B6D1D4.7020202@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ralf.muller@nsn.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 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).