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: Mon, 28 Apr 2014 11:41:04 +0200 [thread overview]
Message-ID: <20140428094104.GA21191@swsaberg01> (raw)
In-Reply-To: <CACRpkdaqPx3=qvUtsg44rBk+ZiscUg54HmNgETcei0LzfE9uOQ@mail.gmail.com>
On Fri, Apr 25, 2014 at 01:50:25PM +0200, Linus Walleij wrote:
> On Fri, Apr 25, 2014 at 11:43 AM, Anders Berg <anders.berg@lsi.com> wrote:
> > On Fri, Apr 25, 2014 at 11:16:18AM +0200, Linus Walleij wrote:
> >> On Thu, Apr 24, 2014 at 7:47 PM, Anders Berg <anders.berg@lsi.com> wrote:
> >> > On Thu, Apr 24, 2014 at 03:24:14PM +0200, Linus Walleij wrote:
> >>
> >> >> 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).
> >>
> >> Hm I'm not sure I understand what a "pin" is in this concept ...
> >> being maintainer of the pin control subsystem and all that really
> >> triggers my interest.
> >>
> >
> > Ok, maybe should replace "pin" with "GPIO" in my previous comment.
> >
> > So, a clarification. In one of the PL061 blocks (named gpio0 in the dts) there
> > is a separate interrupt per GPIO (I assume the motivation here is to enable to
> > control irq affinity per GPIO), where as the other block has a more standard
> > configuration with a single interrupt for all 8 GPIOs in that block.
>
> OK! I get it. Thus this is not a stock PL061, but a version modified to
> generate a separate IRQ line per GPIO line.
>
I believe it's an unmodified PL061. Looking at the TRM, the PL061 interface
signals include a GPIOMIS[7:0] in addition to the GPIOINTR. So I guess by
hooking up the GPIOMIS[7:0] signals to the interrupt controller, you can get
this one-irq-per-gpio setup.
> This means that you can only get a proper, working IRQ from the
> first line on gpio0 right? All other IRQs will be ignored.
Right.
/Anders
next prev parent reply other threads:[~2014-04-28 9:41 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
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 [this message]
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=20140428094104.GA21191@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).