linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: anders.berg@lsi.com (Anders Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: dts: Device tree for AXM55xx.
Date: Tue, 15 Apr 2014 16:56:21 +0200	[thread overview]
Message-ID: <20140415145621.GA32285@swsaberg01> (raw)
In-Reply-To: <534D294D.7000201@arm.com>

On Tue, Apr 15, 2014 at 01:42:53PM +0100, Marc Zyngier wrote:
> Hi Anders,
> 
> On 15/04/14 13:06, Anders Berg wrote:
> > Add device tree for the Amarillo validation board with an AXM5516 SoC.
> > 
> > Signed-off-by: Anders Berg <anders.berg@lsi.com>
> > ---
> >  arch/arm/boot/dts/Makefile             |   1 +
> >  arch/arm/boot/dts/axm5516-amarillo.dts |  51 ++++++
> >  arch/arm/boot/dts/axm5516-cpus.dtsi    | 204 ++++++++++++++++++++++
> >  arch/arm/boot/dts/axm55xx.dtsi         | 306 +++++++++++++++++++++++++++++++++
> >  4 files changed, 562 insertions(+)
> >  create mode 100644 arch/arm/boot/dts/axm5516-amarillo.dts
> >  create mode 100644 arch/arm/boot/dts/axm5516-cpus.dtsi
> >  create mode 100644 arch/arm/boot/dts/axm55xx.dtsi
> > 
> 
> [...]
> 
> > +       gic: interrupt-controller at 2001001000 {
> > +               compatible = "arm,cortex-a15-gic";
> > +               #interrupt-cells = <3>;
> > +               #address-cells = <0>;
> > +               interrupt-controller;
> > +               reg = <0x20 0x01001000 0 0x1000>,
> > +                     <0x20 0x01002000 0 0x1000>,
> > +                     <0x20 0x01004000 0 0x2000>,
> > +                     <0x20 0x01006000 0 0x2000>;
> > +               interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) |
> > +                               IRQ_TYPE_LEVEL_HIGH)>;
> > +       };
> 
> Given how many CPUs this system has, what's the catch regarding the GIC?
> Is there a second one shadowing this one at the same address for another
> set of 8 CPUs? Is there an additional mechanism to IPI the other CPUs?
> 

There is actually one GIC per cluster and SPIs are used to hook the clusters
together for use as IPIs, so with this patch one cluster may be booted (using
the standard SGIs still works within each cluster).

Have a modified GIC driver to run all clusters, but this patch is a bit to
invasive to submit at the moment...

/Anders

  reply	other threads:[~2014-04-15 14:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 12:06 [PATCH 0/5] Add platform support for LSI AXM55xx Anders Berg
2014-04-15 12:06 ` [PATCH 1/5] ARM: Add platform support for LSI AXM55xx SoC Anders Berg
2014-04-15 12:30   ` Arnd Bergmann
2014-04-24  8:58     ` Anders Berg
2014-04-24  9:04   ` Russell King - ARM Linux
2014-04-15 12:06 ` [PATCH 2/5] ARM: dts: Device tree for AXM55xx Anders Berg
2014-04-15 12:42   ` Marc Zyngier
2014-04-15 14:56     ` Anders Berg [this message]
2014-04-15 12:45   ` Arnd Bergmann
2014-04-15 15:20     ` Anders Berg
2014-04-15 15:23       ` Arnd Bergmann
2014-04-22 21:21         ` Linus Walleij
2014-04-22 21:31     ` Linus Walleij
2014-04-22 21:39     ` Russell King - ARM Linux
2014-04-15 12:06 ` [PATCH 3/5] ARM: axxia: Adding defconfig " Anders Berg
2014-04-15 12:06 ` [PATCH 4/5] power: reset: Add Axxia system reset driver Anders Berg
2014-04-15 12:06 ` [PATCH 5/5] ARM: dts: axxia: Add reset controller Anders Berg

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=20140415145621.GA32285@swsaberg01 \
    --to=anders.berg@lsi.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).