From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 682CDDE054 for ; Wed, 28 Jan 2009 01:58:37 +1100 (EST) Message-Id: <0D5BDAF5-E5FD-42FC-977C-B83664FE4C78@kernel.crashing.org> From: Kumar Gala To: tglx@linutronix.de, mingo@elte.hu Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v929.2) Subject: sharing an interrupt between a cascaded/chained pic and another device Date: Tue, 27 Jan 2009 08:57:54 -0600 Cc: linuxppc-dev list , linux-kernel Kernel , Peters Ted List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Thomas, Ingo, Do we have any support in the kernel today to deal with a IRQ on the root PIC being used for both a chained PIC and shared with another HW device. We have a board that guys went and did it and as I look at the kernel code it doesn't seem like this crazy situation is currently supported. - k