From: anders.berg@lsi.com (Anders Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/6] ARM: dts: Device tree for AXM55xx.
Date: Thu, 24 Apr 2014 19:47:41 +0200 [thread overview]
Message-ID: <20140424174741.GA23444@swsaberg01> (raw)
In-Reply-To: <CACRpkdbU6UashxCuPMDjEB_nbB=mXicGpjJy=HGC6r3qfxCtVQ@mail.gmail.com>
On Thu, Apr 24, 2014 at 03:24:14PM +0200, Linus Walleij wrote:
> On Thu, Apr 24, 2014 at 12:44 PM, Anders Berg <anders.berg@lsi.com> wrote:
>
> > Add device tree for the Amarillo validation board with an AXM5516 SoC.
> >
> > Signed-off-by: Anders Berg <anders.berg@lsi.com>
> (...)
>
> > + timer0: timer at 2010091000 {
> > + compatible = "arm,sp804", "arm,primecell";
> > + reg = <0x20 0x10091000 0 0x1000>;
> > + interrupts = <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 47 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 51 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 52 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
> > + clocks = <&clk_per>;
> > + clock-names = "apb_pclk";
> > + status = "okay";
> > + };
> > +
> > + gpio0: gpio at 2010092000 {
> > + #gpio-cells = <2>;
> > + compatible = "arm,pl061", "arm,primecell";
> > + gpio-controller;
> > + reg = <0x20 0x10092000 0x00 0x1000>;
> > + interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 12 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 14 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>;
> > + clocks = <&clk_per>;
> > + clock-names = "apb_pclk";
> > + status = "disabled";
> > + };
>
> One interrupt per CPU core?
>
> The drivers for these blocks will really just grab the first IRQ and
> then I guess they
> will only be able to execute on CPU0.
>
> It's definately correct to list all the IRQs here, but how do you envision
> the drivers making use of them in the long run?
It's one interrupt line per input pin (so with the current driver only the first pin
is usable as interrupt source).
/Anders
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2014-04-24 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 10:44 [PATCH v2 0/6] Add platform support for LSI AXM55xx Anders Berg
2014-04-24 10:44 ` [PATCH v2 1/6] ARM: Add platform support for LSI AXM55xx SoC Anders Berg
2014-04-24 10:52 ` Russell King - ARM Linux
2014-04-24 10:44 ` [PATCH v2 2/6] clk: Add clock driver for " Anders Berg
2014-05-08 9:54 ` Anders Berg
2014-04-24 10:44 ` [PATCH v2 3/6] ARM: dts: Device tree for AXM55xx Anders Berg
2014-04-24 13:24 ` Linus Walleij
2014-04-24 17:47 ` Anders Berg [this message]
2014-04-25 9:16 ` Linus Walleij
2014-04-25 9:43 ` Anders Berg
2014-04-25 11:50 ` Linus Walleij
2014-04-25 11:54 ` Russell King - ARM Linux
2014-04-28 9:41 ` Anders Berg
2014-04-24 10:44 ` [PATCH v2 4/6] ARM: axxia: Adding defconfig " Anders Berg
2014-04-24 10:44 ` [PATCH v2 5/6] power: reset: Add Axxia system reset driver Anders Berg
2014-04-24 10:44 ` [PATCH v2 6/6] ARM: dts: axxia: Add reset controller Anders Berg
2014-05-05 8:35 ` [PATCH v2 0/6] Add platform support for LSI AXM55xx Anders Berg
2014-05-13 8:50 ` Linus Walleij
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=20140424174741.GA23444@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).