linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: scottwood@freescale.com (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] irqchip/Layerscape: Add Layerscape MSI controller support
Date: Fri, 2 Oct 2015 18:57:42 -0500	[thread overview]
Message-ID: <1443830262.5336.216.camel@freescale.com> (raw)
In-Reply-To: <CADRPPNTqADaBDyW9z+BEBJBjaaL9hfW_6Lt3dRXR48+pNZjFUw@mail.gmail.com>

On Mon, 2015-09-28 at 17:19 -0500, Li Yang wrote:
> On Sun, Sep 27, 2015 at 9:48 PM, Lian M.H. <Minghuan.Lian@freescale.com> 
> wrote:
> > Hi Leo,
> > 
> > Could you tell me how to get the detailed Layerscape route map.
> > I am not sure that only Layerscape 1 series use the similar GIC and SCFG 
> > to implement MSI.
> > I am even not sure if ls1043 belongs Layerscape 1 series.
> > 
> > Could anyone tell me how to get the MSI route map?
> 
> MSI shouldn't be the key feature to determine the naming of an SoC.
> So I don't think anyone can tell if all 1 series in the future will
> use this approach. 

In the past the only thing the first number of a QorIQ chip name has meant is 
an approximate positioning on the low-end/high-end spectrum.  It cannot be 
used for grouping chips according to anything that software cares about.

> Probably it will be more generic to name it "fsl,scfg-msi"

Better would have a specific SoC in the name.

-Scott

  parent reply	other threads:[~2015-10-02 23:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:28 [PATCH 1/2] arm: Add msi.h to arch Kbuild files Minghuan Lian
2015-09-17  9:28 ` [PATCH 2/2] irqchip/Layerscape: Add Layerscape MSI controller support Minghuan Lian
2015-09-25 16:37   ` Li Yang
2015-09-28  2:48     ` Lian M.H.
2015-09-28 22:19       ` Li Yang
2015-09-29  2:57         ` Lian M.H.
2015-09-29 20:10           ` Li Yang
2015-10-02 23:57         ` Scott Wood [this message]
     [not found]   ` <CALRxmdChWu7UBK4v4fzuA3KZ5XXRQGoGxAgt_UB0zgJ0ten_uw@mail.gmail.com>
2015-10-09  0:52     ` Stuart Yoder
2015-10-09  8:46       ` Lian M.H.

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=1443830262.5336.216.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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).