[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m360w5kg1u.fsf@t19.piap.pl>
Date: Tue, 29 Mar 2016 07:29:33 +0200
From: khalasa@...p.pl (Krzysztof Hałasa)
To: Tim Harvey <tharvey@...eworks.com>
Cc: Fabio Estevam <festevam@...il.com>,
Lucas Stach <l.stach@...gutronix.de>,
Petr Štetiar <ynezz@...e.cz>,
Richard Zhu <Richard.Zhu@...escale.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-pci\@vger.kernel.org" <linux-pci@...r.kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity
Tim Harvey <tharvey@...eworks.com> 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
Powered by blists - more mailing lists