From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] Preliminary MPIC MSI backend
Date: Sat, 30 Sep 2006 10:43:20 +0200 [thread overview]
Message-ID: <65FA7A1D-5D74-4ABA-9985-2DB78ABC8685@kernel.crashing.org> (raw)
In-Reply-To: <20060929001657.6EFE667B8F@ozlabs.org>
> A pretty hackish MPIC backend, just enough to flesh out the design.
> Based on code from Segher.
It's pretty alright, and very hackish ;-) I'll sign off on it,
but some comments...
Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> +static int msi_mpic_check(struct pci_dev *pdev, int num,
> + struct msix_entry *entries, int type)
> +{
> + /* The irq allocator needs more work to support MSI-X/multi-MSI */
> + if (type == PCI_CAP_ID_MSIX || num != 1)
> + return 1;
I never tested any MSI-X, so maybe keep MSI-X disabled completely
for now?
> +static int msi_mpic_alloc(struct pci_dev *pdev, int num,
> + struct msix_entry *entries, int type)
> +{
> + irq_hw_number_t hwirq;
> + unsigned int virq;
> +
> + /* We need a smarter allocator for MSI-X/multi-MSI */
> + hwirq = irq_map[pdev->irq].hwirq;
> + hwirq += 100;
Yep, that's the main problem with this code. A sanity check to
make sure the number isn't >= 120 would be good, too.
> + set_irq_type(virq, IRQ_TYPE_EDGE_RISING);
I also had some code to show MSI IRQs as "MSI" instead of "EDGE"
in /proc/interrupts, maybe you want to add a generic version of
that? Or maybe you have, and I judt didn't see it.
> +static int msi_mpic_setup_msi_msg(struct pci_dev *pdev,
> + struct msix_entry *entry, struct msi_msg *msg, int type)
> +{
> + msg->address_lo = 0xfee00000; /* XXX What is this value? */
> + msg->address_hi = 0;
> + msg->data = pdev->irq | 0x8000;
Lose the | 0x8000 part, that was an old experiment to work around
U3/U4 MPIC brokenness (and it didn't work).
> +static int msi_mpic_init(void)
> +{
> + /* XXX Do this in mpic_init ? */
> + pr_debug("mpic_msi_init: Registering MPIC MSI ops.\n");
> + ppc_md.get_msi_ops = mpic_get_msi_ops;
It's best to do this in the platform code I think.
Segher
next prev parent reply other threads:[~2006-09-30 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:53 [RFC/PATCH 0/7] Powerpc MSI stuff Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 2/7] Make some MSIX defines generic Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 3/7] Powerpc MSI ops layer Michael Ellerman
2006-10-03 21:54 ` Jake Moilanen
2006-10-24 1:51 ` Michael Ellerman
2006-10-24 13:44 ` Jake Moilanen
2006-09-28 21:53 ` [RFC/PATCH 4/7] Allow for non-Intel MSI implementations Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 5/7] Enable MSI on Powerpc Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 6/7] RTAS MSI implementation Michael Ellerman
2006-10-03 21:53 ` Jake Moilanen
2006-10-24 2:49 ` Michael Ellerman
2006-09-28 21:53 ` [RFC/PATCH 7/7] Preliminary MPIC MSI backend Michael Ellerman
2006-09-28 23:37 ` Michael Ellerman
2006-09-29 0:16 ` [PATCH] " Michael Ellerman
2006-09-30 8:43 ` Segher Boessenkool [this message]
2006-10-24 1:46 ` 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=65FA7A1D-5D74-4ABA-9985-2DB78ABC8685@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).