From: Sricharan R <r.sricharan@ti.com>
To: Sricharan R <r.sricharan@ti.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, nm@ti.com,
linux@arm.linux.org.uk, linux-doc@vger.kernel.org,
tony@atomide.com, linus.walleij@linaro.org, rnayak@ti.com,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
marc.zyngier@arm.com, bcousson@baylibre.com,
galak@codeaurora.org, grant.likely@linaro.org,
santosh.shilimkar@ti.com, tglx@linutronix.de,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 0/4] DRIVERS: IRQCHIP: Add support for crossbar IP
Date: Thu, 26 Dec 2013 10:22:36 +0530 [thread overview]
Message-ID: <52BBB614.5010707@ti.com> (raw)
In-Reply-To: <52B168A5.4010202@ti.com>
Hi Thomas,
On Wednesday 18 December 2013 02:49 PM, Sricharan R wrote:
> Hi Thomas,
>
> On Tuesday 03 December 2013 03:57 PM, Sricharan R wrote:
>> Some socs have a large number of interrupts requests to service
>> the needs of its many peripherals and subsystems. All of the interrupt
>> requests lines from the subsystems are not needed at the same
>> time, so they have to be muxed to the controllers appropriately.
>> In such places a interrupt controllers are preceded by an
>> IRQ CROSSBAR that provides flexibility in muxing the device interrupt
>> requests to the controller inputs.
>>
>> This series models the peripheral interrupts that can be routed through
>> the crossbar to the GIC as 'routable-irqs'. The routable irqs are added
>> in a separate linear domain inside the GIC. The registered routable domain's
>> callback are invoked as a part of the GIC's callback, which in turn should
>> allocate a free irq line and configure the IP accordingly. So every peripheral
>> in the dts files mentions the fixed crossbar number as its interrupt. A free
>> gic line for that gets allocated and configured when the peripheral interrupts
>> are mapped.
>>
>> The minimal crossbar driver to track and allocate free GIC lines and configure the
>> crossbar is added here, along with the DT bindings.
>>
>> V5:
>> Addressed a comment from Mark Rutland <mark.rutland@arm.com>,
>> updated tags and rebased on 3.13-rc2
>>
>> V4:
>> Addressed a couple of comments and split the DTS file updates in to
>> a separate series.
>>
>> V3:
>> Addressed few more comments from Thomas Gleixner <tglx@linutronix.de>
>>
>> Rebased patches 3,4,5,7 which updates the DTS file on top of below branch
>> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>> for_3.13/dts
>>
>> Rebased patches 1,2,6 on top of 3.12 mainline
>> Updated Commit tags
>>
>> V2:
>> Addressed Thomas Gleixner <tglx@linutronix.de> comments and
>> Kumar Gala <galak@codeaurora.org>
>>
>> Split updating the DRA7.dtsi file for adding the routable-irqs
>>
>> Previous discussions that led to this is at
>> https://lkml.org/lkml/2013/9/18/540
>>
>> The V1,V2,V3,V4 post of these patches is at
>> [V1] https://lkml.org/lkml/2013/9/30/283
>> [V2] http://www.spinics.net/lists/linux-omap/msg99540.html
>> [V3] http://www.kernelhub.org/?msg=356470&p=2
>> [V4] http://www.spinics.net/lists/linux-doc/msg16726.html
>>
>> Sricharan R (4):
>> DRIVERS: IRQCHIP: IRQ-GIC: Add support for routable irqs
>> DRIVERS: IRQCHIP: CROSSBAR: Add support for Crossbar IP
>> ARM: OMAP4+: Correct Wakeup-gen code to use physical irq number
>> ARM: DRA: Enable Crossbar IP support for DRA7XX
>>
>> Documentation/devicetree/bindings/arm/gic.txt | 6 +
>> .../devicetree/bindings/arm/omap/crossbar.txt | 27 +++
>> arch/arm/mach-omap2/Kconfig | 1 +
>> arch/arm/mach-omap2/omap-wakeupgen.c | 4 +-
>> arch/arm/mach-omap2/omap4-common.c | 2 +
>> drivers/irqchip/Kconfig | 8 +
>> drivers/irqchip/Makefile | 1 +
>> drivers/irqchip/irq-crossbar.c | 208 ++++++++++++++++++++
>> drivers/irqchip/irq-gic.c | 81 +++++++-
>> include/linux/irqchip/arm-gic.h | 7 +-
>> include/linux/irqchip/irq-crossbar.h | 11 ++
>> 11 files changed, 343 insertions(+), 13 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/omap/crossbar.txt
>> create mode 100644 drivers/irqchip/irq-crossbar.c
>> create mode 100644 include/linux/irqchip/irq-crossbar.h
>>
>
> I have addressed all the comments on this series, can this be merged now ?
>
Ping..
Regards,
Sricharan
next prev parent reply other threads:[~2013-12-26 4:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:27 [PATCH V5 0/4] DRIVERS: IRQCHIP: Add support for crossbar IP Sricharan R
2013-12-03 10:27 ` [PATCH V5 1/4] DRIVERS: IRQCHIP: IRQ-GIC: Add support for routable irqs Sricharan R
2013-12-03 10:27 ` [PATCH V5 2/4] DRIVERS: IRQCHIP: CROSSBAR: Add support for Crossbar IP Sricharan R
2013-12-26 20:01 ` Felipe Balbi
2013-12-27 8:37 ` Sricharan R
2014-01-16 10:22 ` Sricharan R
2014-02-03 11:29 ` Sricharan R
2014-02-04 16:14 ` Thomas Gleixner
2014-02-05 13:11 ` Sricharan R
2014-02-05 14:11 ` Sricharan R
2014-02-26 4:56 ` Sricharan R
[not found] ` <52F24683.9060200-l0cyMroinI0@public.gmane.org>
2014-02-28 21:36 ` Tony Lindgren
[not found] ` <1386066445-28245-1-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2013-12-03 10:27 ` [PATCH V5 3/4] ARM: OMAP4+: Correct Wakeup-gen code to use physical irq number Sricharan R
2013-12-03 10:27 ` [PATCH V5 4/4] ARM: DRA: Enable Crossbar IP support for DRA7XX Sricharan R
2013-12-18 9:19 ` [PATCH V5 0/4] DRIVERS: IRQCHIP: Add support for crossbar IP Sricharan R
2013-12-26 4:52 ` Sricharan R [this message]
2013-12-26 17:44 ` Santosh Shilimkar
2013-12-27 13:49 ` Sricharan R
2013-12-30 6:28 ` Sricharan R
2014-01-07 23:07 ` Tony Lindgren
[not found] ` <20140107230733.GD5074-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-01-07 23:55 ` Tony Lindgren
2014-01-08 13:18 ` Sricharan R
[not found] ` <52CD5010.6030309-l0cyMroinI0@public.gmane.org>
2014-01-08 19:18 ` Tony Lindgren
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=52BBB614.5010707@ti.com \
--to=r.sricharan@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).