Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 01 Nov 2018 09:00:49 +0000
Message-ID: <86bm792mv2.wl-marc.zyngier@arm.com>
From:   Marc Zyngier <marc.zyngier@arm.com>
To:     Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc:     Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
        Device Tree Mailing List <devicetree@vger.kernel.org>,
        Grygorii Strashko <grygorii.strashko@ti.com>,
        <jason@lakedaemon.net>, Sekhar Nori <nsekhar@ti.com>,
        <linux-kernel@vger.kernel.org>, Tero Kristo <t-kristo@ti.com>,
        Rob Herring <robh+dt@kernel.org>,
        Santosh Shilimkar <ssantosh@kernel.org>, <tglx@linutronix.de>,
        Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 09/10] irqchip: ti-sci-inta: Add support for Interrupt Aggregator driver
In-Reply-To: <49029695-79a0-141b-a9da-9764cb0ed60f@ti.com>
References: <20181018154017.7112-1-lokeshvutla@ti.com>
        <20181018154017.7112-10-lokeshvutla@ti.com>
        <b20127dc-be43-3b00-9960-663738df0069@arm.com>
        <9969f24c-cdb0-1f5c-d0f4-b1c1f587325c@ti.com>
        <86va5ssrfm.wl-marc.zyngier@arm.com>
        <b3a71622-7734-04be-0b0c-38e9dc6542d4@ti.com>
        <63ba5353-8470-b4c1-64a8-a1df5bf48614@ti.com>
        <86va5myz7t.wl-marc.zyngier@arm.com>
        <81136b74-4b45-f44b-0168-23d191a4fb5e@ti.com>
        <49029695-79a0-141b-a9da-9764cb0ed60f@ti.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.1
 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)
Organization: ARM Ltd
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 01 Nov 2018 07:55:12 +0000,
Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> 
> Lokesh,
> 
> On 10/29/18 3:04 PM, Lokesh Vutla wrote:
> >>> With the above information, linux should send a message to
> >>> system-controller using TISCI protocol. After policing the given
> >>> information, system-controller does the following:
> >>> - Attaches the interrupt(INTA input) to the device resource index
> >>> - Muxes the interrupt(INTA input) to corresponding vint(INTA output)
> >>> - Muxes the vint(INTR input) to GIC irq(INTR output).
> >>
> >> Isn't there a 1:1 mapping between *used* INTR inputs and outputs?
> >> Since INTR is a router, there is no real muxing. I assume that the
> >> third point above is just a copy-paste error.
> > 
> > Right, my bad. INTR is just a router and no read muxing.
> 
> INTR can mux M interrupt inputs to N interrupt outputs.
> One selects which interrupt input is outputted on the given interrupt
> output.
> It is perfectly valid (but not sane) to select the same interrupt input
> to be routed to _all_ interrupt output for example.
> 
> Not sure if we are going to use this for anything but 1:1 mapping, but
> might worth keeping in mind...

It's not obvious how you'd use this "feature". Interrupt replicator,
should one of the output be tied to another part of the system? Or
maybe that's just the result of reusing some generic block...

	M.

-- 
Jazz is not dead, it just smell funny.