Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp123160imj; Thu, 14 Feb 2019 16:48:20 -0800 (PST) X-Google-Smtp-Source: AHgI3IZivjRVkoGx1duXs8MBoQnxGe0cO3NLU87CdA04TSvZTISuxLZbHZ/rBuUEj6BsQHnSl90i X-Received: by 2002:a62:1d8c:: with SMTP id d134mr7041254pfd.96.1550191700844; Thu, 14 Feb 2019 16:48:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550191700; cv=none; d=google.com; s=arc-20160816; b=mJsaqJ+SeyGV9M1vFlpqcXZuhZJnHpmtZIVx62o5oWl2w7d74ZWnYWTOBoPDaUnC+J vZ6/gaMDUP5F4OU9cJ3iptvCDBWIWA5Gz8QqmLWM6II7Y6nNzDK5DHlxtedhjhfTqBta btYzIARqLPZX/mzUhV/UbRUnroy+lDn4JhB88oEFndC8fI0zsXrii63RHCPOAqkUZ3Ev oteSe2zR00060FkxlkK6z6A2kI2EWB9PL1P20GyBEfOVlRV8blDLM29GOw9ieqpAnJFD rkQjyuLvio2zxJRz0WMS2OBaYFbNnw7CVSuUBcr+vdMRXjOboMxLUAcem4BefX1Lyh2W u3tQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:dkim-signature; bh=SWbjt7N+fuLatSJZuwFXNRLPTls6kh3fKl9oyFHKZFo=; b=v8L04oFyQ52XikheE5c2/iFaJHDoIiZi9fUuSYfyFFhaDe3UDWwokJxDGm97RrZIBf Q7HFiJqJbx/OeKjQfnHy4f9aX6XSiIJ/hcWoiYdD336xjEB24U+IYdPPN68R7BYHFKvO CxmBySO21mFbTD1V1IXLPZTgV7QFXNPn6cwJpUwTB1CaE/gE4/pya0gDh6if69E4SWik Xdz+yzRdFLbOPKN/x8+GyPhsrVSf4QkG3pjGhaD5SO5d11ATwnp5sfslaOKpUX3Gxwsr 9N9/dPaLM99dmSZy+ArGpj7K6J2q3GIpQNpTKmNZej2CBqCO11Qq3WLcvps3qc1135fo iA1g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=a9XdmbKW; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h20si3929847pgm.366.2019.02.14.16.48.04; Thu, 14 Feb 2019 16:48:20 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=a9XdmbKW; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2502254AbfBNPth (ORCPT + 99 others); Thu, 14 Feb 2019 10:49:37 -0500 Received: from lelv0143.ext.ti.com ([198.47.23.248]:41558 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2395384AbfBNPth (ORCPT ); Thu, 14 Feb 2019 10:49:37 -0500 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id x1EFmieR122687; Thu, 14 Feb 2019 09:48:44 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1550159324; bh=SWbjt7N+fuLatSJZuwFXNRLPTls6kh3fKl9oyFHKZFo=; h=Subject:To:References:CC:From:Date:In-Reply-To; b=a9XdmbKWaAIzGh4JqaZ/0B8f1RZrIGqlj9AJS5YExyNAmwSp7zq6K9wjU+RTR+e5g STBkxR3hj08AFqPdgn8BwDc600FB9jV5NIVjgsmobN0oTvNrHeZC6VsaOn2tnLmWoI n3fAk9fMe2KPivRTnPcxxnzXaeuBR4YpLJ8b5Pa8= Received: from DFLE105.ent.ti.com (dfle105.ent.ti.com [10.64.6.26]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x1EFmiLo064810 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 14 Feb 2019 09:48:44 -0600 Received: from DFLE110.ent.ti.com (10.64.6.31) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Thu, 14 Feb 2019 09:48:43 -0600 Received: from dlep32.itg.ti.com (157.170.170.100) by DFLE110.ent.ti.com (10.64.6.31) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1591.10 via Frontend Transport; Thu, 14 Feb 2019 09:48:43 -0600 Received: from [192.168.2.6] (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id x1EFmdeP015098; Thu, 14 Feb 2019 09:48:39 -0600 Subject: Re: [PATCH v2 01/14] dt-bindings: remoteproc: Add TI PRUSS bindings To: Marc Zyngier , Suman Anna , "Davis, Andrew" , Lokesh Vutla References: <1549290167-876-1-git-send-email-rogerq@ti.com> <1549290167-876-2-git-send-email-rogerq@ti.com> <9c58bc48-90bf-8ac5-7fbd-0f6443e3fc5e@ti.com> <5C65490E.6000800@ti.com> <86ef8asfap.wl-marc.zyngier@arm.com> <5C658CE4.5030307@ti.com> CC: Linus Walleij , ext Tony Lindgren , Ohad Ben-Cohen , Bjorn Andersson , David Lechner , "Nori, Sekhar" , Tero Kristo , , , Murali Karicheri , , Linux-OMAP , , "linux-kernel@vger.kernel.org" , DTML From: Roger Quadros Message-ID: <5C658DD6.8080309@ti.com> Date: Thu, 14 Feb 2019 17:48:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <5C658CE4.5030307@ti.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org fixed DTML id. On 14/02/19 17:44, Roger Quadros wrote: > On 14/02/19 14:52, Marc Zyngier wrote: >> On Thu, 14 Feb 2019 10:55:10 +0000, >> Roger Quadros wrote: >>> >>> >>> On 14/02/19 10:37, Linus Walleij wrote: >>>> On Thu, Feb 14, 2019 at 4:13 AM Suman Anna wrote: >>>>> [Me] >>>> >>>>>> To be able to use hierarchical interrupt domain in the kernel, the top >>>>>> interrupt controller must use the hierarchical (v2) irqdomain, so >>>>>> if this is anything else than the ARM GIC it will be an interesting >>>>>> undertaking to handle this. >>>>> >>>>> These are interrupt lines coming towards the host processor running >>>>> Linux and are directly connected to the ARM GIC. This INTC module is >>>>> actually an PRUSS internal interrupt controller that can take in 64 (on >>>>> most SoCs) external events/interrupt sources and multiplexing them >>>>> through two layers of many-to-one events-to-intr channels & >>>>> intr-channels-to-host interrupts. Couple of the host interrupts go to >>>>> the PRU cores themselves while the remaining ones come out of the IP to >>>>> connect to other GICs in the SoC. >>>> >>>> If the muxing is static (like set up once at probe) so that while >>>> the system is running, there is one and one only event mapped to >>>> the GIC from the component below it, then it is hierarchical. >>> >>> This is how it looks. >>> >>> [GIC]<---8---[INTC]<---64---[events from peripherals] >>> >>> The 8 interrupt lines from INTC to the GIC are 1:1 mapped and fixed >>> per SoC. The muxing between 64 inputs to INTC and its 8 outputs are >>> programmable and might not necessarily be static per boot/probe as >>> it depends on what firmware is loaded on the PRU. >> >> But the point is that at any given time, there are at most 8 out of 64 >> inputs that are used, right? You *never* end-up with two (or more) of >> these "events" being multiplexed on a single output line. >> > > Since the INTC's internal logic allows assigning more than one event each outputs, > at most all 64 events can be assigned to one output or distributed among the 8 outputs. > >> If these assertions do hold, then your design is typical of a >> hierarchy, for which we have countless examples in the tree (including >> for some TI HW). > > OK. > Suman, Andrew, Lokesh, thoughts? > -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki