Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758056Ab3HMNaG (ORCPT ); Tue, 13 Aug 2013 09:30:06 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:33263 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757989Ab3HMNaC (ORCPT ); Tue, 13 Aug 2013 09:30:02 -0400 Message-ID: <520A34AD.3020806@ti.com> Date: Tue, 13 Aug 2013 09:29:17 -0400 From: Santosh Shilimkar User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sricharan R CC: Tony Lindgren , Nishanth Menon , Linus Walleij , "linux-kernel@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-doc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Linux-OMAP , Russell King - ARM Linux , Rajendra Nayak , Felipe Balbi , Thomas Gleixner , Grant Likely Subject: Re: [PATCH 1/3] misc: Add crossbar driver References: <51E83A4F.5080904@ti.com> <51ED2385.60108@ti.com> <51ED5C66.1010407@ti.com> <51EFFBE1.4090505@ti.com> <51F0031B.1050307@ti.com> <51F00530.9090703@ti.com> <51F02069.3050207@ti.com> <51F0223E.4050008@ti.com> <51F0240F.3050507@ti.com> <20130813081003.GU7656@atomide.com> <520A02BA.4090805@ti.com> In-Reply-To: <520A02BA.4090805@ti.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2998 Lines: 55 On Tuesday 13 August 2013 05:56 AM, Sricharan R wrote: > Hi Tony, > > On Tuesday 13 August 2013 01:40 PM, Tony Lindgren wrote: >> * Santosh Shilimkar [130724 12:06]: >>> On Wednesday 24 July 2013 02:51 PM, Nishanth Menon wrote: >>>> On 07/24/2013 01:43 PM, Sricharan R wrote: >>>>> On Wednesday 24 July 2013 10:17 PM, Nishanth Menon wrote: >>>>>> On 07/24/2013 11:38 AM, Santosh Shilimkar wrote: >>>>>>> On Wednesday 24 July 2013 12:08 PM, Nishanth Menon wrote: >>>>>>>> That said, maybe a intermediate pinctrl approach might be more pragmatic and less theoretically flexible. >>>>>>>> an option might be to "statically allocate" default number of interrupts to a domain - example: >>>>>>>> * GIC IRQ 72->78 allotted to UARTs >>>>>>>> * pinctrl mapping provided for those but only 6 can be used (rest are marked status="disabled" as default) at any given time (choice of pinctrl option determines GIC interrupt line to use) >>>>>>>> * All modules will have a pinctrl definition to have a mapping - to avoid bootloader overriding default cross bar setting in ways un-expected by kernel. >>>>>>>> >>>>>>>> Does that sound fair trade off? >>>>>>> This sounds better. That way we can get all the devices in the DT at least. >>>>>> Fair enough - if Linus and Tony are still ok with this approach to the problem, seeing a patch series with the effect would be beneficial. >>>>>> >>>>> Ok, i will use this idea of certain number interrupts to groups. >>>>> Yes on DRA7XX, we have about 160 gic lines and 320 irq crossbar device inputs contending for it. >>>>> 1:2 and fully arbitrary. But will we be really exhausting them ? >>>>> >>>> Depends on how we allocate :). The default arbitary allocation can be made more logical in your series ofcourse :). >>>> >>> I would just most logical peripherals rather than providing every single >>> IP connected to cross bar. Otherwise we will end up wth hwmod like >>> scenario where now started removing the unused stuff because of >>> maintenance and loc issues ;-) >> Sorry for the delay on this, I think the best way to set this up >> is as a separate drivers/irqchip controller. Then just map the >> configured interrupts for the board with interrupt-map and >> interrupt-map-mask binding. No need to stuff all the SoC specific >> maps to the .dts, just the ones used for the board. >> >> Regards, >> >> Tony >> > Initially irqchip was discussed, but we also have a DMA crossbar > to map the dma-requests. Since both irq/dma crossbars should be handled, > pinctrl was suggested as the appropriate place to handle this. > I replied on other thread. I guess Tony's point is to setup only required events for a board rather than setting up every possible event. Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/