From: nm@ti•com (Nishanth Menon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] misc: Add crossbar driver
Date: Wed, 24 Jul 2013 13:51:42 -0500 [thread overview]
Message-ID: <51F0223E.4050008@ti.com> (raw)
In-Reply-To: <51F02069.3050207@ti.com>
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 :).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-07-24 18:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 16:43 [PATCH 0/3] Add crossbar driver Sricharan R
2013-07-18 16:43 ` [PATCH 1/3] misc: " Sricharan R
2013-07-18 16:55 ` Joe Perches
2013-07-18 18:25 ` Felipe Balbi
2013-07-21 16:33 ` Linus Walleij
2013-07-18 18:56 ` Nishanth Menon
2013-07-18 23:39 ` Santosh Shilimkar
2013-07-19 0:13 ` Nishanth Menon
2013-07-19 10:48 ` Sricharan R
2013-07-19 7:17 ` Tony Lindgren
2013-07-19 10:48 ` Sricharan R
2013-07-21 16:49 ` Linus Walleij
2013-07-22 12:20 ` Sricharan R
2013-07-22 16:23 ` Santosh Shilimkar
2013-07-24 16:08 ` Nishanth Menon
2013-07-24 16:38 ` Santosh Shilimkar
2013-07-24 16:47 ` Nishanth Menon
2013-07-24 18:43 ` Sricharan R
2013-07-24 18:51 ` Nishanth Menon [this message]
2013-07-24 18:59 ` Santosh Shilimkar
2013-08-13 8:10 ` Tony Lindgren
2013-08-13 9:56 ` Sricharan R
2013-08-13 13:29 ` Santosh Shilimkar
2013-08-15 20:01 ` Linus Walleij
2013-08-15 20:26 ` Santosh Shilimkar
2013-08-15 20:51 ` Linus Walleij
2013-08-15 21:14 ` Santosh Shilimkar
2013-08-21 21:10 ` Linus Walleij
2013-08-22 11:33 ` Sricharan R
2013-08-22 13:45 ` Santosh Shilimkar
2013-08-23 4:47 ` Rajendra Nayak
2013-08-23 6:11 ` Sricharan R
2013-08-23 6:17 ` Rajendra Nayak
2013-08-23 6:36 ` Sekhar Nori
2013-08-23 6:53 ` Sricharan R
2013-08-23 8:14 ` Sekhar Nori
2013-08-23 13:38 ` Santosh Shilimkar
2013-08-23 16:28 ` Sekhar Nori
2013-08-23 19:06 ` Linus Walleij
2013-08-23 19:44 ` Santosh Shilimkar
2013-08-13 13:28 ` Santosh Shilimkar
2013-08-14 7:27 ` Tony Lindgren
2013-07-18 16:43 ` [PATCH 2/3] ARM: dts: DRA: Add crossbar device binding Sricharan R
2013-07-18 19:04 ` Nishanth Menon
2013-07-18 16:43 ` [PATCH 3/3] ARM: DRA7xx: Enable crossbar driver for the soc Sricharan R
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=51F0223E.4050008@ti.com \
--to=nm@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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