From: Thomas Gleixner <tglx@linutronix.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
"jason@lakedaemon.net" <jason@lakedaemon.net>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] Documentation: bcm7120-l2: Add Broadcom BCM7120-style L2 binding
Date: Fri, 5 Sep 2014 22:44:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1409052224211.5472@nanos> (raw)
In-Reply-To: <540A15AA.4000805@gmail.com>
On Fri, 5 Sep 2014, Florian Fainelli wrote:
> On 09/05/2014 12:21 PM, Thomas Gleixner wrote:
> > So if I understand correctly what you have is:
> >
> > /- GIC------------->
> > Device-irq ---- [routing]
> > \- BC irq chip ---->
> >
> > and you implement it as
> >
> > Device-irq ---- [BC irq chip] ---- [GIC] --->
> > |
> > ----------------->
> >
> > And the fwd mask is to tell the BC chip to use the GIC and which irq
> > of the GIC, so it can fiddle with the GIC under the hood, right?
>
> The forward mask really is to tell the BCM7120 l2 interrupt controller:
> bypass me, and output the UART interrupts directly at the GIC level, so
> I think this does match your understanding.
>
> Not setting the forward mask means you would get the UART interrupts at
> the BCM7120 l2 interrupt controller level, and have to handle them here.
>
> Hope this helps clarify what this funky piece of hardware does.
Sigh, this stacked interrupt chip nonsense is becoming a plague.
So if you set that bit then the UART driver only sees the GIC as its
interrupt controller and not the L2 thingy. So, the L2 chip only
enables its interrupt unconditionally for that line and the
enable/disable happens at the GIC level.
If that's the case, that's fine with me. It's not pretty, but at least
it does not involve L2 fiddling indirectly with the GIC.
Thanks,
tglx
next prev parent reply other threads:[~2014-09-05 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409265326-7579-1-git-send-email-f.fainelli@gmail.com>
[not found] ` <1409265326-7579-3-git-send-email-f.fainelli@gmail.com>
[not found] ` <1409265326-7579-3-git-send-email-f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-03 12:13 ` [PATCH 2/2] Documentation: bcm7120-l2: Add Broadcom BCM7120-style L2 binding Thomas Gleixner
2014-09-03 12:43 ` Mark Rutland
2014-09-03 16:59 ` Florian Fainelli
[not found] ` <5407490E.7060505-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-05 9:05 ` Mark Rutland
2014-09-05 18:01 ` Florian Fainelli
[not found] ` <5409FA82.6000703-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-05 19:21 ` Thomas Gleixner
2014-09-05 19:57 ` Florian Fainelli
2014-09-05 20:44 ` Thomas Gleixner [this message]
2014-09-05 21:15 ` Florian Fainelli
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=alpine.DEB.2.10.1409052224211.5472@nanos \
--to=tglx@linutronix.de \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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