Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755504AbdDMTSO (ORCPT ); Thu, 13 Apr 2017 15:18:14 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:36538 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751808AbdDMTSM (ORCPT ); Thu, 13 Apr 2017 15:18:12 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170413133242.5068-1-andrew.smirnov@gmail.com> <20170413133242.5068-5-andrew.smirnov@gmail.com> From: Fabio Estevam Date: Thu, 13 Apr 2017 16:18:10 -0300 Message-ID: Subject: Re: [PATCH 4/8] ARM: dts: imx7s: Add node for GPC To: Tyler Baker Cc: Andrey Smirnov , Mark Rutland , "devicetree@vger.kernel.org" , Russell King , "linux-kernel@vger.kernel.org" , Rob Herring , Sascha Hauer , Fabio Estevam , Shawn Guo , linux-arm-kernel , yurovsky@gmail.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 947 Lines: 20 On Thu, Apr 13, 2017 at 4:03 PM, Tyler Baker wrote: > I've been testing your GPC/PCIe patch sets against v4.11-rc5 on my > imx7d-cl-som-imx7, but hit a bit of a wall. When gpc is set as the > interrupt-parent for the soc, the kernel seems to hang and not produce > any output on the serial port[0]. I tried to enable earlyprintk, but > no luck getting a trace. Reversing this change, gets the board > booting[1], but obviously isn't using the gpc which is needed for PCIe > support as I understand it. I assume you've tested these changes on a > imx7d-sdb and are not seeing a similar issue? You can find the patches > I've picked on top of v4.11-rc5 here[2], any idea what might be the > issue? Thanks for the report. It seems this series depends on the drivers/soc/imx/gpcv2.c patches that landed into linux-next. In this case, it would be better to re-send this series after 4.12-rc11 is out to avoid the breakage.