From: "H. Peter Anvin" <hpa@zytor.com>
To: Andreas Block <andreas.block@esd-electronics.com>
Cc: Xavier Bestel <xavier.bestel@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Bugfixes: PCI devices get assigned redundant IRQs
Date: Sun, 28 Jan 2007 00:04:41 -0800 [thread overview]
Message-ID: <45BC5919.8030004@zytor.com> (raw)
In-Reply-To: <op.tmrh5hxp8n9ctc@pc-block.esd>
Andreas Block wrote:
>>
>> Aren't there platforms for which irq = 0 is a valid irq ?
>
> As far as I understand the PCI spec, the answer to your question seems
> to be: no
> (or I'm missing something).
>
> Don't get me wrong. I'm not talking about system IRQs, but about the
> value of the Interrupt Pin Register in PCI configuration space.
>
> The PCI Local Bus Specification in Revision 3.0 from 3rd February 2004
> says on page 223 about the content of Interrupt Pin register:
>
> Value 0x00: _No_ interrupt
> Values 0x01 to 0x04: Interrupt lines A to D
> And values 5 to 0xFF are reserved.
>
> So I'd say, the "correction" of greater values than four to a value of
> one seems discussable, too. Because it will break any future changes of
> the PCI spec.
>
I think you're confusing the Interrupt Line register and the Interrupt
Pin register. The Interrupt Line register is platform-dependent, but on
x86 platforms it generally contains the IRQ number (and IRQ 0 is valid,
although in practice it is never used since IRQ 0 is the system timer
and is never connected to the PCI bus), or 255 meaning "none" -- see the
footnote on page 223 of the PCI 3.0 spec.
-hpa
next prev parent reply other threads:[~2007-01-28 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 10:50 Bugfixes: PCI devices get assigned redundant IRQs Andreas Block
2007-01-26 11:00 ` Xavier Bestel
2007-01-26 12:54 ` Andreas Block
2007-01-28 8:04 ` H. Peter Anvin [this message]
2007-01-28 15:35 ` Andreas Block
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=45BC5919.8030004@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.block@esd-electronics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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