linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Jason Jin <Jason.jin@freescale.com>
Subject: Re: [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board
Date: Sat, 24 May 2008 00:31:21 +1000	[thread overview]
Message-ID: <1211553081.16348.0.camel@localhost> (raw)
In-Reply-To: <27CED929-FF61-42D3-A53C-C21B4980BF94@kernel.crashing.org>

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

On Fri, 2008-05-23 at 08:02 -0500, Kumar Gala wrote:
> On May 23, 2008, at 7:59 AM, Anton Vorontsov wrote:
> 
> > On Fri, May 23, 2008 at 04:32:46PM +0800, Jason Jin wrote:
> >> This MSI driver can be used on 83xx/85xx/86xx board.
> >> In this driver, virtual interrupt host and chip were
> >> setup. There are 256 MSI interrupts in this host, Every 32
> >> MSI interrupts cascaded to one IPIC/MPIC interrupt.
> >> The chip was treated as edge sensitive and some necessary
> >> functions were setup for this chip.
> >>
> >> Before using the MSI interrupt, PCI/PCIE device need to
> >> ask for a MSI interrupt in the 256 MSI interrupts. A 256bit
> >> bitmap show which MSI interrupt was used, reserve bit in
> >> the bitmap can be used to force the device use some designate
> >> MSI interrupt in the 256 MSI interrupts. Sometimes this is useful
> >> for testing the all the MSI interrupts. The msi-available-ranges
> >> property in the dts file was used for this purpose.
> >>
> >> Signed-off-by: Jason Jin <Jason.jin@freescale.com>
> >> ---
> >
> > Hello Jason,
> >
> > Few comments below.
> 
> Jason, I'll apply this version.  I expect some clean up based on Anton  
> and Stephen's comments.

Version 4 or 5 of this patch had my ACK for the MSI bits FWIW.

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:[~2008-05-23 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23  8:32 [PATCH 1/4 V5] booting-without-of for Freescale MSI Jason Jin
2008-05-23  8:32 ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Jason Jin
2008-05-23  8:32   ` [PATCH 3/4 V5] Enable MSI support for MPC8610HPCD board Jason Jin
2008-05-23  8:32     ` [PATCH 4/4 V5] Enable MSI support for 85xxds board Jason Jin
2008-05-23 13:06       ` Kumar Gala
2008-05-23 13:05     ` [PATCH 3/4 V5] Enable MSI support for MPC8610HPCD board Kumar Gala
2008-05-23 12:59   ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Anton Vorontsov
2008-05-23 13:02     ` Kumar Gala
2008-05-23 13:41       ` [PATCH] [POWERPC] fsl_msi: few (mostly cosmetic) fixes Anton Vorontsov
2008-05-24  4:48         ` Kumar Gala
2008-05-23 14:31       ` Michael Ellerman [this message]
2008-05-23 13:06   ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Kumar Gala
2008-05-23 13:05 ` [PATCH 1/4 V5] booting-without-of for Freescale MSI Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20  8:07 [PATCH 1/4 V4] " Jason Jin
2008-05-20  8:07 ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Jason Jin

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=1211553081.16348.0.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=Jason.jin@freescale.com \
    --cc=galak@kernel.crashing.org \
    --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).