linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Sethi Varun-B16395 <B16395@freescale.com>
Cc: "Linuxppc-dev@lists.ozlabs.org" <Linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/4] powerpc/mpic: Move internal interrupt source vector allocation to a separate function.
Date: Tue, 27 Mar 2012 09:02:05 -0500	[thread overview]
Message-ID: <BA2352CD-6C54-4D33-86DB-F55DBDBA6E5F@kernel.crashing.org> (raw)
In-Reply-To: <C5ECD7A89D1DC44195F34B25E172658D0B11BA@039-SN2MPN1-013.039d.mgd.msft.net>


On Mar 27, 2012, at 8:52 AM, Sethi Varun-B16395 wrote:

>=20
>=20
>> -----Original Message-----
>> From: Kumar Gala [mailto:galak@kernel.crashing.org]
>> Sent: Tuesday, March 27, 2012 6:55 PM
>> To: Sethi Varun-B16395
>> Cc: Linuxppc-dev@lists.ozlabs.org
>> Subject: Re: [PATCH 3/4] powerpc/mpic: Move internal interrupt source
>> vector allocation to a separate function.
>>=20
>>=20
>> On Mar 27, 2012, at 7:16 AM, Varun Sethi wrote:
>>=20
>>> Allocate vector numbers for MPIC internal interrupt sources (IPIs =
and
>>> Timers) in a separate function.
>>>=20
>>=20
>> Explain why you are making this change.
>=20
>=20
> [Sethi Varun-B16395] With the current code it becomes fairly difficult =
to
> add new internal interrupt sources. In my case I had to add 32 =
additional
> interrupt sources corresponding to the MPIC error interrupts. It's =
more
> convenient doing the internal interrupt source allocation using a =
loop.

I think that is more due to how you added the MPIC error interrupts and =
issues w/that code.  If you are treating the MPIC error interrupts as a =
cascade than they should have a distinct linux IRQ space from the =
standard MPIC interrupts.  This is how the MSIs work (as an example).

- k=

  reply	other threads:[~2012-03-27 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 12:16 [PATCH 3/4] powerpc/mpic: Move internal interrupt source vector allocation to a separate function Varun Sethi
2012-03-27 13:24 ` Kumar Gala
2012-03-27 13:52   ` Sethi Varun-B16395
2012-03-27 14:02     ` Kumar Gala [this message]
2012-04-04 19:09       ` Sethi Varun-B16395
2012-04-04 23:29         ` 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=BA2352CD-6C54-4D33-86DB-F55DBDBA6E5F@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=B16395@freescale.com \
    --cc=Linuxppc-dev@lists.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).