From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH] pata_of_platform: fix no irq handling Date: Tue, 12 Aug 2008 08:00:32 +1000 Message-ID: <1218492032.8041.11.camel@pasglop> References: <48A05152.7020508@harris.com> <20080811151913.GA14690@oksana.dev.rtsoft.ru> <48A0676E.5020308@harris.com> <20080811170756.GA29827@oksana.dev.rtsoft.ru> Reply-To: benh@kernel.crashing.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080811170756.GA29827@oksana.dev.rtsoft.ru> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linuxppc-dev-bounces+glppd-linuxppc64-dev=m.gmane.org@ozlabs.org Errors-To: linuxppc-dev-bounces+glppd-linuxppc64-dev=m.gmane.org@ozlabs.org To: avorontsov@ru.mvista.com Cc: linuxppc-dev@ozlabs.org, Jeff Garzik , "Sparks, Sam" , linux-ide@vger.kernel.org List-Id: linux-ide@vger.kernel.org > 1. IDE status read does not work. (But am I understand correctly > that IDE works well if IRQ is unspecified? Then this is hardly > an issue.) > 2. IDE interrupt comes when it should not. I'd recommend to use > oscilloscope to find out what is happening there, that is, if > the drive actually deasserts its irq line after status read. > If so, than this could be a PIC problem. > > What is the platform on which you're observing the issue, btw? Another possibility is that you got the wrong interrupt number in the device-tree... Ben.