From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] misc: Add crossbar driver
Date: Wed, 14 Aug 2013 00:27:44 -0700 [thread overview]
Message-ID: <20130814072744.GV7656@atomide.com> (raw)
In-Reply-To: <520A3464.10406@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti•com> [130813 06:35]:
> On Tuesday 13 August 2013 04:10 AM, Tony Lindgren wrote:
> > * Santosh Shilimkar <santosh.shilimkar@ti•com> [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.
> >
> Interrupt mask/unmask, really ? Thats like abusing those irqchip
> hooks completely. Your point is to just setup events which we need
> and thats what I also suggested. But the use of irqchip hooks is
> certainly not the right idea since they are for masking/unmasking
> interrupts in running system and not for joining the interrupt
> line which needs to happen once during probe.
Well if it's an interrupt controller. Doing a chained IRQ pinctrl
driver might work too. But yes, the idea with interrupt-map was
to only map what's used rather than have data for each SoC.
Regards,
Tony
next prev parent reply other threads:[~2013-08-14 7:27 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
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 [this message]
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=20130814072744.GV7656@atomide.com \
--to=tony@atomide$(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