linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 6/9] MPIC MSI allocator
Date: Wed, 13 Dec 2006 12:23:53 -0600	[thread overview]
Message-ID: <20061213122353.7498a25e@pb15> (raw)
In-Reply-To: <20061213104007.4B8F967DA9@ozlabs.org>

On Wed, 13 Dec 2006 21:40:03 +1100 Michael Ellerman <michael@ellerman.id.au> wrote:

> To support MSI on MPIC we need a way to reserve and allocate hardware irq
> numbers, this patch implements an allocator for that. It looks like we'll
> end up with several backends based on the MPIC, so the allocator is attached
> to the struct mpic, not the msi backend.
> 
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>

> +static void mpic_msi_auto_reserve_hwirqs(struct mpic *mpic)
> +{
> +	irq_hw_number_t hwirq;
> +	struct irq_host_ops *ops = mpic->irqhost->ops;
> +	struct device_node *np;
> +	int flags, index, i;
> +	struct of_irq oirq;
> +
> +	/* Reserve source numbers we know are reserved in the HW */

How do we know? Reserved on what HW? Sure looks system/platform
dependent to me.

> +	for (i = 0;   i < 8;   i++)
> +		__mpic_msi_reserve_hwirq(mpic, i);
> +	for (i = 42;  i < 26;  i++)
             ^^^^^^^^^^^^^^^

Is this some sort of check to see if we're awake? :)

> +		__mpic_msi_reserve_hwirq(mpic, i);
> +	for (i = 100; i < 105; i++)
> +		__mpic_msi_reserve_hwirq(mpic, i);




-Olof

  reply	other threads:[~2006-12-13 18:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 10:39 [PATCH 0/9] Powerpc MSI Implementation (.. again) Michael Ellerman
2006-12-13 10:39 ` [PATCH 1/9] Add #defines for Hypertransport MSI fields Michael Ellerman
2006-12-13 10:39 ` [PATCH 2/9] Rip out the existing powerpc msi stubs Michael Ellerman
2006-12-13 10:39 ` [PATCH 3/9] Powerpc MSI implementation Michael Ellerman
2006-12-13 10:39 ` [PATCH 4/9] Enable MSI on Powerpc Michael Ellerman
2006-12-13 10:39 ` [PATCH 5/9] RTAS MSI implementation Michael Ellerman
2006-12-13 10:40 ` [PATCH 6/9] MPIC MSI allocator Michael Ellerman
2006-12-13 18:23   ` Olof Johansson [this message]
2006-12-13 23:25     ` Benjamin Herrenschmidt
2006-12-14  0:09       ` Olof Johansson
2006-12-14  0:32         ` Benjamin Herrenschmidt
2006-12-14  0:59           ` Michael Ellerman
2006-12-14  1:02             ` Benjamin Herrenschmidt
2006-12-14  1:06               ` Michael Ellerman
2006-12-14 14:46                 ` Segher Boessenkool
2006-12-14 19:44                   ` Benjamin Herrenschmidt
2006-12-15  1:47                     ` Segher Boessenkool
2006-12-15  1:51                       ` Michael Ellerman
2006-12-15  2:28                       ` Benjamin Herrenschmidt
2006-12-15  2:58                         ` Segher Boessenkool
2006-12-15  6:42                           ` Olof Johansson
2006-12-14  1:06             ` Olof Johansson
2006-12-14  0:34     ` Michael Ellerman
2006-12-13 10:40 ` [PATCH 7/9] MPIC MSI backend Michael Ellerman
2006-12-13 10:40 ` [PATCH 8/9] Activate MSI on Powerpc Michael Ellerman
2006-12-13 10:40 ` [PATCH 9/9] Enable MSI mappings for MPIC Michael Ellerman

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=20061213122353.7498a25e@pb15 \
    --to=olof@lixom.net \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=paulus@samba.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).