From: Stefan Roese <ml@stefan-roese.de>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems
Date: Mon, 20 Nov 2006 12:54:32 +0100 (MET) [thread overview]
Message-ID: <200611201255.37754.ml@stefan-roese.de> (raw)
In-Reply-To: <20061120114248.60bb0869@localhost.localdomain>
On Monday 20 November 2006 12:42, Alan wrote:
> On Mon, 20 Nov 2006 12:00:36 +0100
>
> Stefan Roese <ml@stefan-roese.de> wrote:
> > This patch fixes a problem seen on multiple 4xx platforms, where
> > the UART0 interrupt number is 0. The macro "is_real_interrupt" lead
> > on those systems to not use an real interrupt but the timer based
> > implementation.
>
> NAK.
I knew it. ;-)
> Zero means "no interrupt" in the Linux space. If you have a physical IRQ
> 0 remap it to a convenient number (eg map IRQ's + 1, or stick it on the
> end). The logical and physical IRQ numbering in Linux don't have to match
> up - and given some platforms have IRQ numbering per bus and the like
> clearly doesn't in many cases.
Let's see, if I got this right. You mean that on such a platform, where 0 is a
valid physical IRQ, we should assign another value as virtual IRQ number (not
0 and not -1 of course). And then the platform "pic" implementation should
take care of the remapping of these virtual IRQ numbers to the physical
numbers.
Correct?
Best regards,
Stefan
next prev parent reply other threads:[~2006-11-20 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 11:00 [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems Stefan Roese
2006-11-20 11:24 ` Peter Korsgaard
2006-11-20 11:42 ` Alan
2006-11-20 11:54 ` Stefan Roese [this message]
2006-11-20 12:10 ` Alan
2006-11-20 13:04 ` Russell King
2006-11-20 21:21 ` Guennadi Liakhovetski
2006-11-20 13:28 ` Sergei Shtylyov
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=200611201255.37754.ml@stefan-roese.de \
--to=ml@stefan-roese.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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).