linux-kernel - Re: [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140626102650.GH28884@atomide.com>
Date:	Thu, 26 Jun 2014 03:26:51 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Sricharan R <r.sricharan@...com>
Cc:	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	santosh.shilimkar@...com, nm@...com, rnayak@...com,
	linux@....linux.org.uk, tglx@...utronix.de, jason@...edaemon.net,
	joe@...ches.com, Benoit Cousson <bcousson@...libre.com>
Subject: Re: [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding

* Sricharan R <r.sricharan@...com> [140626 01:36]:
> Hi Tony,
> 
> On Thursday 26 June 2014 01:14 PM, Tony Lindgren wrote:
> > * Sricharan R <r.sricharan@...com> [140626 00:29]:
> >> From: R Sricharan <r.sricharan@...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.

OK

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/