From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Sricharan R <r.sricharan@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linus.walleij@linaro.org,
linux@arm.linux.org.uk, tony@atomide.com, rnayak@ti.com,
marc.zyngier@arm.com, grant.likely@linaro.org,
mark.rutland@arm.com, robherring2@gmail.com, tglx@linutronix.de,
galak@codeaurora.org, rob.herring@calxeda.com, nm@ti.com,
bcousson@baylibre.com
Subject: Re: [PATCH V4 0/3] ARM: DTS: DRA7: Updates for adding crossbar device
Date: Thu, 14 Nov 2013 09:23:36 -0500 [thread overview]
Message-ID: <5284DCE8.9080800@ti.com> (raw)
In-Reply-To: <1384431928-2328-1-git-send-email-r.sricharan@ti.com>
On Thursday 14 November 2013 07:25 AM, 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.
>
> The driver support for the same was added here.
> http://marc.info/?l=linux-omap&m=138443167321614&w=2
>
> The dts file update to support the crossbar device and convert
> peripheral irq numbers to crossbar number are added here.
> This series was originally a part of the series [1] and now split
> to keep the DTS updates separately as per comments from
> Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> Applied this series on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
> for_3.13/dts
>
> [1] http://www.kernelhub.org/?msg=356470&p=2
>
> Sricharan R (3):
> ARM: DTS: DRA: Add crossbar device binding
> ARM: DTS: DRA: Replace peripheral interrupt numbers with crossbar
> inputs
> ARM: DTS: DRA7: Add routable-irqs property for gic node
>
For entire series,
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
next prev parent reply other threads:[~2013-11-14 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 12:25 [PATCH V4 0/3] ARM: DTS: DRA7: Updates for adding crossbar device Sricharan R
2013-11-14 12:25 ` [PATCH V4 1/3] ARM: DTS: DRA7: Add crossbar device binding Sricharan R
2013-11-14 12:25 ` [PATCH V4 2/3] ARM: DTS: DRA7: Replace peripheral interrupt numbers with crossbar inputs Sricharan R
2013-11-14 12:25 ` [PATCH V4 3/3] ARM: DTS: DRA7: Add routable-irqs property for gic node Sricharan R
2013-11-14 14:23 ` Santosh Shilimkar [this message]
2013-12-30 6:58 ` [PATCH V4 0/3] ARM: DTS: DRA7: Updates for adding crossbar device Sricharan R
[not found] ` <52C1197A.5010701-l0cyMroinI0@public.gmane.org>
2014-05-05 14:37 ` Sricharan R
2014-05-05 14:55 ` Nishanth Menon
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=5284DCE8.9080800@ti.com \
--to=santosh.shilimkar@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=r.sricharan@ti.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.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).