linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Jean-Christophe Dubois <jdubois@mc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH 4/4] Add support for MSI on Axon-based Cell systems
Date: Thu, 07 Jun 2007 17:58:59 +1000	[thread overview]
Message-ID: <1181203139.4166.26.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <200706050900.54022.jdubois@mc.com>

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

On Tue, 2007-06-05 at 09:00 +0200, Jean-Christophe Dubois wrote:
> On Monday 04 June 2007 15:00:05 Michael Ellerman wrote:
> > +       pr_debug("axon_msi: initialising ...\n");
> > +
> > +       for_each_compatible_node(node, NULL, "ibm,axon-msic") {
> > +               if (axon_msi_setup_one(of_node_get(node)) == 0)
> > +                       found++;
> > +       }
> > +       of_node_put(node);
> 
> 2 comments:
> 
> 1) There is no "ibm,axon-msic" compatible property in the SLOF tree provided 
> by IBM on the CAB (or other such platforms). Therefore this code will not 
> work on these platforms.

It's not clear to me if MSIs will work on CAB, with Axon in end-point
mode. But it'd be good to try it at some point.

The compatible property is new, it's only just been added to SLOF
recently by Heiko, not sure when it will be in released firmware.

> 2) you should somehow check for the Axon version. Axon 1.1 (and prior) are 
> know to be loosing MSI/MBX interrupts (but not the data part associated to 
> them). Therefore this should be enabled only on Axon 2.1 (or later).

Yep. It works some of the time on 1.1, but not enough to enable it.

I guess I'd say firmware that runs on 1.1 should just not export the msi
nodes, or not put the compatible property on them - rather than having
the kernel explicitly checking for the version.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-06-07  7:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 12:59 [PATCH 1/4] Split virq setup logic out into irq_setup_virq() Michael Ellerman
2007-06-04 13:00 ` [PATCH 2/4] Add irq_create_direct_mapping() Michael Ellerman
2007-06-04 22:44   ` Benjamin Herrenschmidt
2007-06-04 13:00 ` [PATCH 3/4] Add for_each_compatible_node() Michael Ellerman
2007-06-04 22:44   ` Benjamin Herrenschmidt
2007-06-04 13:00 ` [RFC/PATCH 4/4] Add support for MSI on Axon-based Cell systems Michael Ellerman
2007-06-04 17:09   ` Arnd Bergmann
2007-06-04 17:12   ` Arnd Bergmann
2007-06-08  2:53     ` Michael Ellerman
2007-06-08  8:47       ` Segher Boessenkool
2007-06-08 19:26         ` Arnd Bergmann
2007-06-08 19:36           ` Segher Boessenkool
2007-06-08 19:59             ` Segher Boessenkool
2007-06-08 20:06               ` Arnd Bergmann
2007-06-08 20:16                 ` Segher Boessenkool
2007-06-12  2:32                   ` Michael Ellerman
2007-06-08 20:01             ` Arnd Bergmann
2007-06-08 20:06               ` Segher Boessenkool
2007-06-12  2:30                 ` Michael Ellerman
2007-06-04 22:45   ` Benjamin Herrenschmidt
2007-06-05  7:00   ` Jean-Christophe Dubois
2007-06-05  9:16     ` Arnd Bergmann
2007-06-05  9:29       ` Jean-Christophe Dubois
2007-06-05  9:30       ` Arnd Bergmann
2007-06-07  7:58     ` Michael Ellerman [this message]
2007-06-07  8:10       ` Jean-Christophe Dubois
2007-06-07 11:55         ` Benjamin Herrenschmidt
2007-06-07 12:00           ` Jean-Christophe Dubois
2007-06-05 14:12   ` Milton Miller
2007-06-06  5:19     ` Michael Ellerman
2007-06-04 22:43 ` [PATCH 1/4] Split virq setup logic out into irq_setup_virq() 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=1181203139.4166.26.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=jdubois@mc.com \
    --cc=linuxppc-dev@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).