From: Sricharan R <r.sricharan@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
santosh.shilimkar@ti.com, nm@ti.com, rnayak@ti.com,
linux@arm.linux.org.uk, tglx@linutronix.de, jason@lakedaemon.net,
joe@perches.com, Benoit Cousson <bcousson@baylibre.com>
Subject: Re: [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding
Date: Thu, 26 Jun 2014 14:02:26 +0530 [thread overview]
Message-ID: <53ABDA9A.8000108@ti.com> (raw)
In-Reply-To: <20140626074417.GF28884@atomide.com>
Hi Tony,
On Thursday 26 June 2014 01:14 PM, Tony Lindgren wrote:
> * Sricharan R <r.sricharan@ti.com> [140626 00:29]:
>> From: R Sricharan <r.sricharan@ti.com>
>>
>> There is a IRQ crossbar device in the soc, which
>> maps the irq requests from the peripherals to the
>> mpu interrupt controller's inputs. The Peripheral irq
>> requests are connected to only one crossbar
>> input and the output of the crossbar is connected to only one
>> controller's input line. The crossbar device is used to map
>> a peripheral input to a free mpu's interrupt controller line.
>>
>> Here, adding a new crossbar device node and replacing all the peripheral
>> interrupt numbers with its fixed crossbar input lines.
>
> I think these two patches need to be a single patch to avoid
> breaking booting for git bisect inbetween these patches?
This does not cause booting issues. irq_desc gets allocated linearly,
but that does not create boot issues.
Regards,
Sricharan
next prev parent reply other threads:[~2014-06-26 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 7:25 [PATCH V4 0/2] arm: dts: dra7: add crossbar dt support Sricharan R
2014-06-26 7:25 ` [PATCH V4 1/2] arm: dts: dra7: add routable-irqs property for gic node Sricharan R
2014-06-26 7:25 ` [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding Sricharan R
[not found] ` <1403767532-19290-3-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2014-06-26 7:44 ` Tony Lindgren
2014-06-26 8:32 ` Sricharan R [this message]
2014-06-26 10:26 ` Tony Lindgren
2014-07-09 15:44 ` Tony Lindgren
2014-07-10 5:58 ` Lokesh Vutla
2014-07-10 6:19 ` 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=53ABDA9A.8000108@ti.com \
--to=r.sricharan@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=rnayak@ti.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).