From: detheridge@ti.com (Darren Etheridge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 0/2] arm: dts: dra7: Updates for adding crossbar device
Date: Wed, 7 May 2014 09:56:56 -0500 [thread overview]
Message-ID: <20140507145656.GG2626@ti.com> (raw)
In-Reply-To: <1399464998-23216-1-git-send-email-r.sricharan@ti.com>
Sricharan R <r.sricharan@ti.com> wrote on Wed [2014-May-07 17:46:36 +0530]:
> 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 dts file update to support the crossbar device and convert
> peripheral irq numbers to crossbar number are added here.
>
> This is a rebase on top of 3.15-rc4
>
> This series depends on crossbar-driver-fixes sent below
> http://marc.info/?l=linux-omap&m=139929963420299&w=2
>
> [V6] Reordered patch 3 to patch 1 and
> squashed patch 2 and 3 from V5 in to patch 2
>
> Sricharan R (2):
> arm: dts: dra7: Add routable-irqs property for gic node
> arm: dts: dra7: Add crossbar device binding
>
Just for thoroughness I dropped the previous 3 patch series from my
build and replaced with this two patch series. Everything still works
with my test setup so I consider these patches good.
Darren
next prev parent reply other threads:[~2014-05-07 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 12:16 [PATCH V6 0/2] arm: dts: dra7: Updates for adding crossbar device Sricharan R
2014-05-07 12:16 ` [PATCH V6 1/2] arm: dts: dra7: Add routable-irqs property for gic node Sricharan R
2014-05-07 14:56 ` Darren Etheridge [this message]
2014-05-07 15:29 ` [PATCH V6 0/2] arm: dts: dra7: Updates for adding crossbar device 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=20140507145656.GG2626@ti.com \
--to=detheridge@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).