From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix QEIC->MPIC cascading
Date: Thu, 20 Sep 2007 13:44:16 -0500 [thread overview]
Message-ID: <46F2BF80.5030502@freescale.com> (raw)
In-Reply-To: <46F2B8FD.7040501@freescale.com>
Timur Tabi wrote:
> Anton Vorontsov wrote:
>
>> I don't know (didn't look) why this works for 83xx w/o ack()...
>> maybe IPIC don't need this. Or maybe there is a bug hiding.
>
> Scott W told me that me that the IPIC doesn't have the concept of EOI ack. It
> just has IRQ masks.
And the IRQ will be masked at the QEIC while being processed. Doing it
this way allows another QE interrupt to come through while the first is
being serviced.
It might make sense on MPIC to ack after masking at the QEIC, for this
reason.
-Scott
next prev parent reply other threads:[~2007-09-20 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 13:02 [PATCH] [POWERPC] Fix QEIC->MPIC cascading Anton Vorontsov
2007-09-20 17:03 ` Timur Tabi
2007-09-20 17:41 ` Anton Vorontsov
2007-09-20 18:16 ` Timur Tabi
2007-09-20 18:44 ` Scott Wood [this message]
2007-09-20 19:03 ` Haiying Wang
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=46F2BF80.5030502@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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).