From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753192AbdEJNc5 (ORCPT ); Wed, 10 May 2017 09:32:57 -0400 Received: from metis.ext.4.pengutronix.de ([92.198.50.35]:50721 "EHLO metis.ext.4.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753198AbdEJNcz (ORCPT ); Wed, 10 May 2017 09:32:55 -0400 Message-ID: <1494423139.2322.60.camel@pengutronix.de> Subject: Re: Regression: 442ec4c04d1: PCI: dwc: all: Split struct pcie_port into host-only and core structures From: Lucas Stach To: Fabio Estevam Cc: Peter Senna Tschudin , Kishon Vijay Abraham I , Bjorn Helgaas , Jingoo Han , Richard Zhu , Murali Karicheri , Minghuan Lian , Mingkai Hu , Roy Zang , Thomas Petazzoni , Niklas Cassel , Jesper Nilsson , Joao Pinto , Zhou Wang , Gabriele Paoloni , Stanimir Varbanov , Pratyush Anand , "linux-pci@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-kernel , Tim Harvey Date: Wed, 10 May 2017 15:32:19 +0200 In-Reply-To: References: <20170508150224.GA7458@collabora.com> <20170509063439.GC9791@collabora.com> <20170510131722.GA29556@collabora.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:fa0f:41ff:fe58:4010 X-SA-Exim-Mail-From: l.stach@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, den 10.05.2017, 10:27 -0300 schrieb Fabio Estevam: > On Wed, May 10, 2017 at 10:17 AM, Peter Senna Tschudin > wrote: > > On Tue, May 09, 2017 at 07:21:24AM -0300, Fabio Estevam wrote: > >> Hi Peter, > >> > >> On Tue, May 9, 2017 at 3:34 AM, Peter Senna Tschudin > >> wrote: > >> > >> > Something that ocurred to me is that u-boot is initializing the PCI, and > >> > the PCI networkd cards. Ideally this should not affect anything, but > >> > can this be related to the issue? > >> > >> Yes, in order to narrow things down: please boot 4.11 without PCI > >> support in U-Boot. > > > > Yes, removing the PCI code from u-boot makes 4.11 to boot. But latest > > next still hangs. > > Ok, good. At least we see the same behaviour now. > > We still need a fix for the mx6q hang on systems with PCI switch for > linux/next or 4.12-rc1. I will take a look at this today. > > >> The problem is that mx6q does not have a way to properly reset the PCI block. > >> > >> On the board I tested there is no PCI support in U-Boot. > >> > >> Maybe we need the following approach in U-Boot as Lucas did for Barebox: > >> https://git.pengutronix.de/cgit/barebox/commit/?id=f1da98da2760c21487bbba8f7fb957c843a22896 > > > > Maybe we do need, but the kernel is working on v4.10 for our use case, > > and it is not working any longer on v4.11. What is the way to continue > > from here? > > There is no other way other than fixing U-Boot on this case. You could also revert the change in the kernel if you are absolutely sure that this won't cause issues on your system (you are not using the internal watchdog etc.). But for the long run and to make sure that _all_ use-cases work properly, there is no way around fixing your bootloader to behave correctly. Regards, Lucas