From: Segher Boessenkool <segher@kernel.crashing.org>
To: benh@kernel.crashing.org
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [kvm-ppc-devel] Bamboo PCI interrupt issues
Date: Tue, 04 Mar 2008 20:59:28 +0000 [thread overview]
Message-ID: <1a852cd10d2aab54aaa7d810649ab1b3@kernel.crashing.org> (raw)
In-Reply-To: <1204663317.21545.73.camel@pasglop>
>> More generally, the target interrupt descriptors (sense values, in
>> particular) in a device tree interrupt map describe the interrupts as
>> seen on the target interrupt controller, *not* as seen on this
>> (source)
>> interrupt domain. This should be obvious, but since the source
>> interrupt
>> descriptor for PCI doesn't have a sense value (it's always level low,
>> after all), it can be confusing. Well, interrupts always are
>> confusing
>> :-)
>
> Sure. But if your stupid bridge sticks a not gate between the PIRQ
> input
> and the UIC (interrupt controller), effectively, the UIC sees a
> reversed
> polarity. Thus you need to put in your interrupt map a reversed
> polarity
> information for the UIC interrupt specifiers.
That's what I said, isn't it? :-)
Segher
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: benh@kernel.crashing.org
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: Bamboo PCI interrupt issues
Date: Tue, 4 Mar 2008 21:59:28 +0100 [thread overview]
Message-ID: <1a852cd10d2aab54aaa7d810649ab1b3@kernel.crashing.org> (raw)
In-Reply-To: <1204663317.21545.73.camel@pasglop>
>> More generally, the target interrupt descriptors (sense values, in
>> particular) in a device tree interrupt map describe the interrupts as
>> seen on the target interrupt controller, *not* as seen on this
>> (source)
>> interrupt domain. This should be obvious, but since the source
>> interrupt
>> descriptor for PCI doesn't have a sense value (it's always level low,
>> after all), it can be confusing. Well, interrupts always are
>> confusing
>> :-)
>
> Sure. But if your stupid bridge sticks a not gate between the PIRQ
> input
> and the UIC (interrupt controller), effectively, the UIC sees a
> reversed
> polarity. Thus you need to put in your interrupt map a reversed
> polarity
> information for the UIC interrupt specifiers.
That's what I said, isn't it? :-)
Segher
next prev parent reply other threads:[~2008-03-04 20:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:02 [kvm-ppc-devel] Bamboo PCI interrupt issues Hollis Blanchard
2008-03-04 0:02 ` Hollis Blanchard
2008-03-04 0:59 ` [kvm-ppc-devel] " David Gibson
2008-03-04 0:59 ` David Gibson
2008-03-04 1:42 ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-03-04 1:42 ` Benjamin Herrenschmidt
2008-03-04 1:53 ` [kvm-ppc-devel] " David Gibson
2008-03-04 1:53 ` David Gibson
2008-03-04 2:07 ` [kvm-ppc-devel] " Segher Boessenkool
2008-03-04 2:07 ` Segher Boessenkool
2008-03-04 2:15 ` [kvm-ppc-devel] " David Gibson
2008-03-04 2:15 ` David Gibson
2008-03-04 3:37 ` [kvm-ppc-devel] " Josh Boyer
2008-03-04 3:37 ` Josh Boyer
2008-03-04 6:15 ` [kvm-ppc-devel] " Stefan Roese
2008-03-04 6:15 ` Stefan Roese
2008-03-04 6:33 ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-03-04 6:33 ` Benjamin Herrenschmidt
2008-03-04 20:39 ` [kvm-ppc-devel] " Segher Boessenkool
2008-03-04 20:39 ` Segher Boessenkool
2008-03-04 20:41 ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-03-04 20:41 ` Benjamin Herrenschmidt
2008-03-04 20:59 ` Segher Boessenkool [this message]
2008-03-04 20:59 ` Segher Boessenkool
2008-03-04 21:01 ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-03-04 21:01 ` Benjamin Herrenschmidt
2008-03-04 6:18 ` [kvm-ppc-devel] " Benjamin Herrenschmidt
2008-03-04 6:18 ` Benjamin Herrenschmidt
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=1a852cd10d2aab54aaa7d810649ab1b3@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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.