From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 22 Feb 2007 12:18:11 +1100 From: David Gibson To: Kumar Gala Subject: Re: [PATCH] powerpc: document new interrupt-array property Message-ID: <20070222011811.GA18364@localhost.localdomain> References: <200702212325.l1LNPBwL007793@ld0164-tx32.am.freescale.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: Stuart Yoder , paulus@samba.org, linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Feb 21, 2007 at 06:29:22PM -0600, Kumar Gala wrote: > > On Feb 21, 2007, at 5:25 PM, Stuart Yoder wrote: > > > > > Added description of an interrupt-array property. This > > is needed to cleanly describe the interrupt properties > > of devices with interrupts routed to multiple > > interrupt controllers. > > > > Created a new section VII to describe interrupt > > representation in general and moved Section VI #2 > > ('Specifiying interrupt information for SOC devices') > > to this new section. > > > > Signed-off-by: Stuart Yoder > > --- > > what problem is this trying to solve? As he says, it's for devices with interrupts routed to multiple controllers. The normal interrupts property assumes a single interrupt parent for a device. This is needed on most 4xx boards, where the MAL has 5 interrupts, some of which are on UIC0 and some of which are on UIC1. At the moment the Ebony port deals with this using an "interesting" hack, treating the MAL as an interrupt nexus for itself, using an interrupt-map to remap its interrupts to the two controllers. The interrupt-array proposal does the same thing much more neatly and compactly. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson