Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757345AbcC2PZT (ORCPT ); Tue, 29 Mar 2016 11:25:19 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:59120 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752307AbcC2PZR (ORCPT ); Tue, 29 Mar 2016 11:25:17 -0400 From: Arnd Bergmann To: Tim Harvey Cc: Lucas Stach , "linux-arm-kernel@lists.infradead.org" , "linux-pci@vger.kernel.org" , Richard Zhu , linux-kernel , Krzysztof =?utf-8?B?SGHFgmFzYQ==?= , Bjorn Helgaas , Petr =?utf-8?B?xaB0ZXRpYXI=?= , Fabio Estevam Subject: Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity Date: Tue, 29 Mar 2016 17:24:31 +0200 Message-ID: <3827347.i8fIQs6jUv@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <5741237.2X2Q0sCFQj@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:UUNi2cEvjLZWpArAc79JHtZ5OGAIgLzI0kwj8GEmBMNM2TZIp8N sNmqfF4OEKHzz21rJhcKoFu6Jt4mgxk9f2x0Ob4Rxh236TsANziQ/LZMBANqQcMqS/pm7dn RyZJSIn6nqo0DpAb3YM4cWTqhVa5cvnzVY6XvH1UeQWrAPNefilLhIjPVy7CqeNuCsjtVoM ykNz922Pq9uzMIclxpfEg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Mh5jeda7JHQ=:22Dr61LhYqtqgxEZCFqxY4 w3yykzrLfyidcIPGrFIrBVPbXlCamzeriAdANxiJpKGuO2RgUIr9/bzik03KZYC17yJPOIW/w +zzbKudG+YFYnK09A3NQchCAewe09rT7nKHyMm3KwPzKyapLJTqKXk7qFNzOXCD4ZKegvo/QS qYgdcADO9A7AzE5EHFEIrL9qGghhGtqC7SG7tmuwRFHKR9OwpzGF1u27iMKghZu6neSu1D/dU 1BWzgD2BL1YjoT+l1lgk9ECE5FCHb59EfMKw/+BTX82qn6Eut1ar1HoHqwLvVnTqzwHKhF7p5 85FBj0jCkDLCBDr6KEqEFi3zDvWR9cv8rFg1JafODwlI3Ml3h3+w2zZkv21ql81ajoqBhFNLd Fyu3OoZWaNRiNZjzBx52d8b9aVm7/7HvY++Uec8s/fT4LtaFqEmXTXUqioeeFOx/aYvnajB2m QXD4syRAeW7AjGpe+QFAwF4bfkLEaSi1d6g9jr0TjyXKy6wcQphkP68OXYYF0t7m2CVHVCaTs 6Q3sISdxIPo1ujQw7W5kNNbPB4aN20fl4qwfjfIlL4vv4X2+2H5U8emmrK93VNbJjhipZAsDK ULccKlHQLjhcQCCNA4rNlw3/gq/KAtZWij/yTsSiH/xE/OgMjJAoCPnSAR8F8yr7AX+gnDUhQ vKPNamEC7GE7A0yEN/m2lDO8GTUUwEKLbZwoqYB5k3FA1uMT156mH0Ge/ayZGcpjSoA5BVch8 r3t/xmYGjnTx2FUX Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1376 Lines: 31 On Tuesday 29 March 2016 08:10:08 Tim Harvey wrote: > Arnd, > > Right, on the IMX the MSI interrupt is GIC-120 which is also the > legacy INTD and I do see that if I happen to put a radio in a slot > where due to swizzling its pin1 becomes INTD (GIC-120) the interrupt > does fire and the device works. Any other slot using GIC-123 (INTA), > GIC-122 (INTB), or GIC-121 (INTC) never fires so its very possible > that something in the designware core is masking out the legacy irqs. Interesting. I was actually expecting the opposite here, having the IRQs only work if they are not IntD. > I typically advise our users to 'not' enable MSI because > architecturally you can spread 4 distinct legacy irq's across CPU's > better than a single shared irq. That is a very good point, I never understood why we want to enable MSI support on any PCI host bridge that just forwards all MSIs to a single IRQ line. Originally MSI was meant as a performance feature, but there is nothing in this setup that makes things go faster, and several things that make it go slower. I would still hope that with disabling MSI support in just the i.MX driver (as in the trivial patch I suggested trying, or by reverting Lucas' d1dc9749a5b8 patch) will make things just work. If not, we may need to change the pcie-designware driver as well, so it doesn't try to enable MSI on its own. Arnd