From: r.sricharan@ti•com (Sricharan R)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V5 0/3] arm: dts: dra7: Updates for adding crossbar device
Date: Wed, 7 May 2014 10:10:27 +0530 [thread overview]
Message-ID: <5369B93B.5060203@ti.com> (raw)
In-Reply-To: <20140506214526.GF2626@ti.com>
On Wednesday 07 May 2014 03:15 AM, Darren Etheridge wrote:
> Sricharan R <r.sricharan@ti•com> wrote on Tue [2014-May-06 19:26:16 +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 of V4 series 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
>>
>> Sricharan R (3):
>> arm: dts: dra7: Add crossbar device binding
>> arm: dts: dra7: Replace peripheral interrupt numbers with crossbar
>> inputs
>> arm: dts: dra7: Add routable-irqs property for gic node
>>
>
> OK, assuming the bisectability issues discussed earlier on this thread
> are addressed. I have tested the earlier crossbar patch series in
> conjunction with this dts series with VIP capture and DSS display
> running together on DRA7. Looks good with this combination of
> devices. VIP is one of the modules that must have a crossbar mapping as
> there is no default interrupt mapping for it, therefore VIP makes a good
> test case.
>
> So please feel free to add:
>
> Tested-by: Darren Etheridge <detheridge@ti•com>
Thanks for the testing. Will reorder and repost.
Regards,
Sricharan
next prev parent reply other threads:[~2014-05-07 4:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 13:56 [PATCH V5 0/3] arm: dts: dra7: Updates for adding crossbar device Sricharan R
2014-05-06 13:56 ` [PATCH V5 1/3] arm: dts: dra7: Add crossbar device binding Sricharan R
2014-05-06 19:40 ` Felipe Balbi
2014-05-06 19:46 ` Nishanth Menon
2014-05-06 19:58 ` Darren Etheridge
2014-05-06 20:07 ` Darren Etheridge
2014-05-06 13:56 ` [PATCH V5 2/3] arm: dts: dra7: Replace peripheral interrupt numbers with crossbar inputs Sricharan R
2014-05-06 14:41 ` Tony Lindgren
2014-05-06 13:56 ` [PATCH V5 3/3] arm: dts: dra7: Add routable-irqs property for gic node Sricharan R
2014-05-06 21:45 ` [PATCH V5 0/3] arm: dts: dra7: Updates for adding crossbar device Darren Etheridge
2014-05-07 4:40 ` Sricharan R [this message]
2014-05-08 8:13 ` Archit Taneja
2014-05-07 12:06 ` Roger Quadros
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=5369B93B.5060203@ti.com \
--to=r.sricharan@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