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 C7951DDFBE for ; Thu, 9 Apr 2009 15:23:00 +1000 (EST) Message-Id: <37642F7D-7A32-43F6-A07D-D3EC1C243C8A@kernel.crashing.org> From: Kumar Gala To: michael@ellerman.id.au In-Reply-To: <1239251928.22777.2.camel@localhost> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Date: Thu, 9 Apr 2009 00:18:53 -0500 References: <49DB6914.1030107@freescale.com> <49DBE858.9040004@kernel.org> <1239156559.10104.7.camel@localhost> <49DD1154.3040106@kernel.org> <49DD11D1.7060105@freescale.com> <49DD1375.8030400@kernel.org> <49DD1465.6070001@freescale.com> <49DD17C3.7040607@kernel.org> <1239234793.6214.5.camel@localhost> <1239251928.22777.2.camel@localhost> Cc: Tejun Heo , linux-ide@vger.kernel.org, Timur Tabi , Jeff Garzik , Linux PPC Development List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Apr 8, 2009, at 11:38 PM, Michael Ellerman wrote: > On Wed, 2009-04-08 at 23:23 -0500, Kumar Gala wrote: >> On Apr 8, 2009, at 6:53 PM, Michael Ellerman wrote: >> >>> On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote: >>>> On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote: >>>>> Hmmm... for now, >>>>> I think it would be best to revert the original change. Jeff, can >>>>> you >>>>> please do that? >>>> >>>> Actually, give me a few days before you do that. A colleague >>>> gave me >>>> some suggestions to debug this. >>> >>> What device did you say it was? A "ULI M1575" ? >>> >>> Is that this one? >>> >>> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_AL, 0x1575, >>> hpcd_quirk_uli1575); >>> >>> static void __devinit hpcd_quirk_uli1575(struct pci_dev *dev) >>> { >>> u32 temp32; >>> >>> if (!machine_is(mpc86xx_hpcd)) >>> return; >>> >>> /* Disable INTx */ >>> pci_read_config_dword(dev, 0x48, &temp32); >>> pci_write_config_dword(dev, 0x48, (temp32 | 1<<26)); >>> .. >> >> It is the odd thing is the board he's running on is a mpc86xx_hpcd so >> he shouldn't be hitting the code that actually disables INTx. > > Sorry Kumar that's not parsing :) > > He is running an mpc86xx_hpcd, so he _should_ be hitting the code that > disables INTX? duh.. reading the !machine_is.. code incorrectly. - k