From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ni.piap.pl ([195.187.100.4]:51954 "EHLO ni.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752247AbcC2F3g (ORCPT ); Tue, 29 Mar 2016 01:29:36 -0400 From: khalasa@piap.pl (Krzysztof =?utf-8?Q?Ha=C5=82asa?=) To: Tim Harvey Cc: Fabio Estevam , Lucas Stach , Petr =?utf-8?Q?=C5=A0tetiar?= , Richard Zhu , Bjorn Helgaas , "linux-pci\@vger.kernel.org" , "linux-arm-kernel\@lists.infradead.org" , linux-kernel Subject: Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity References: Date: Tue, 29 Mar 2016 07:29:33 +0200 In-Reply-To: (Tim Harvey's message of "Mon, 28 Mar 2016 15:06:53 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-pci-owner@vger.kernel.org List-ID: Tim Harvey writes: > It's not too easy to tell how many IMX6 boards incorrectly specify > their reset-gpio polarity. I don't know what the best way to determine > what boards use the IMX6 pcie host controller. Is there a dtc usage > that will display the compiled dtb's then we grep out 'compatible = > "fsl,imx6q-pcie"' to at least get the list of boards to inspect? I'm > curious if its just one or two boards that incorrectly specify the > polarity of their PCI reset. I guess, maybe 8 of them. Not counting those with out-of-tree DTS/DTB files. Something like: $ grep reset-gpio arch/arm/boot/dts/imx6* | grep -v phy-reset > I figured out it was the change to enable CONFIG_PCI_MSI in v4.5 that > is causing interrupts to fail for me. Right, a long standing issue. MSI never worked for me on i.MX6. -- Krzysztof Halasa Industrial Research Institute for Automation and Measurements PIAP Al. Jerozolimskie 202, 02-486 Warsaw, Poland