Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5302954imu; Wed, 19 Dec 2018 08:51:05 -0800 (PST) X-Google-Smtp-Source: AFSGD/XpnrmJuoI7Q9Tc10QnSlDJEcjyXu8QhSMchM81NdIROsaKjiCg/fuKpvVIKF4vf5NT6cgR X-Received: by 2002:a63:381c:: with SMTP id f28mr20015459pga.330.1545238265860; Wed, 19 Dec 2018 08:51:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545238265; cv=none; d=google.com; s=arc-20160816; b=XjAMiqdb5nb6aHTWPmwdYC7/vLaAAyASu1Og5vRPCn2r52twt9YryLTEM4jNNdWiwr SsUPONCKYRSUejlm8p8NkJN5Zov0cO/Zl6nHUuYfYG1iSlI1EKssa8zn3TeJsZPixh+s jOh9j6Gy14NmmPB3pU3QaZggiG7LRA20nw1rL7XXO0SQZlYvjchvqf2SLJEfsjOz3/wX ja2/tHNw9i1Fq5L6pgGne4tmAEduOxV/AY2WBANQztCFbnN7iWR3IG7n0jc+HEprzgJS hD7Kl7/j7PLFaTHFo282ScbZJ51fDJcZE4JBB5FWiTLyciMmc3/r/QQdoQg0Z47J9wGb w1BA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=i1J0G7Qb3L5GwrfmGAi18Vk60flEeeXwzQEPVkr55SY=; b=IycuGnBecSo129vwDBf/rLjnpxS9EIC6KHzgOVxILcG/u6QbJ5f35Axvp4pfDPC5kS wfx5il+O+u/C+IDI4qXse8p4rBUzOUiq9tiLsjX1h+eLO+50x/56SsQ5AkY/AdFtN41j Z6Q+rrCN861ybDwLF+tNE9BipTQOYLNkptc5Arjlv4n3Vwsdh2hk8ZUp3SeChO7QBE4R lw8WlVMDDrsZ51da0T9N1zEJlUNxpJZF2vTIv427jnPTxd5mdDuMtIh7wejXbDRxsf9+ dXBhkKaUMvdXGfbYqPLkWvobURDqqBQaw+CZsUY7uxCZeT5ojaRIwWamjmfiYYM4FNmS steQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="AkxOyuQ/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o2si16565684pfb.166.2018.12.19.08.50.49; Wed, 19 Dec 2018 08:51:05 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="AkxOyuQ/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729439AbeLSOgT (ORCPT + 99 others); Wed, 19 Dec 2018 09:36:19 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:34254 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728013AbeLSOgT (ORCPT ); Wed, 19 Dec 2018 09:36:19 -0500 Received: by mail-ot1-f68.google.com with SMTP id t5so19339870otk.1; Wed, 19 Dec 2018 06:36:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i1J0G7Qb3L5GwrfmGAi18Vk60flEeeXwzQEPVkr55SY=; b=AkxOyuQ/VKMUyBKMAsIpcqo3mrGqy/ybUEq99It7f+i+QeLwblefCZ83NKSCVGVXby lcy5Tbxo+Eh7BN4m63AboyDERrSkLysJ7kZJeU1TUqXLozV+93uxLlgLNpozxYayvLsZ 1HXyfzFSrmQXtrCNtG7SKD/SAA3dlZmq4xpVuskdGeKrw8pUcJEhG01BEfN2cboIeS3g oe7b2YwBiEBDYELbrIb1pjgtPQAKSPSIcD7l7qfjCAg+22qnmykKNczkkk1NoGRGYVOB 2R9UwNGXiKhUj8VL4/5wWavdNa2KbNUR1C5V2styzHvQp0oRTqvx4pkfCPjvnC3Zu2OI K3lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i1J0G7Qb3L5GwrfmGAi18Vk60flEeeXwzQEPVkr55SY=; b=LwgL8ZtH3U8Rjry9iOw9O/S4QQngexQ0LGi6J2fuJkJz2z84w4kwlpwCx5goTN8sPP ouQnNY1F3rLcAITj7xVO3oEDH0JAGpzQWT8pwAEYyCDl55yV9qqGMCQoxp1Mgt1rUP+b +vKRME30BQfDa0th76pRSFfCyBXQVMKiStwWzYZXDFmIaSH18tz52lSYycjd+HsTZ+jo Q12KM7cpYKcQuZ0U+TlddOF+nXfS7LPojvEP5YrGe0Vcs1fXJDsTBYkhgY80luMsbRV5 qToZ6C0LOeIseAECpA1G/O/iXrOCq+p+zGbg25tA+YDQuYJmOyP2eb+51KBP+35hHFL5 qH+w== X-Gm-Message-State: AA+aEWYZGzwmBmMa3dIq68EEJWBXJ6BKLjShzAdvfTj2P/9EsnT2XlWj LUzJ9t66jrpHYobwhPe51gDHUeb5CmDCe22VIkd8saDhkfk= X-Received: by 2002:a9d:74c3:: with SMTP id a3mr5481870otl.107.1545230178083; Wed, 19 Dec 2018 06:36:18 -0800 (PST) MIME-Version: 1.0 References: <20181218210444.5950-1-TheSven73@googlemail.com> <1545174393.22930.65.camel@impinj.com> In-Reply-To: <1545174393.22930.65.camel@impinj.com> From: Sven Van Asbroeck Date: Wed, 19 Dec 2018 09:36:07 -0500 Message-ID: Subject: Re: [RFC BUG] pci: Freescale i.MX6 PCIe controller: revert mainline regression To: Trent Piepho Cc: "shawn.lin@rock-chips.com" , "niklas.cassel@axis.com" , "lorenzo.pieralisi@arm.com" , "kishon@ti.com" , "bhelgaas@google.com" , "gustavo.pimentel@synopsys.com" , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , "hongxing.zhu@nxp.com" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thank you Trent ! This patch was intended as a bug report, rather than an actual solution to be merged. I chose this format so people could easily verify the change in behaviour, just by applying the patch locally. On Tue, Dec 18, 2018 at 6:06 PM Trent Piepho wrote: > > > It's actually commit f3fdfc4ac3a2 ("PCI: Remove host driver Kconfig > selection of CONFIG_PCIEPORTBUS") that made this problem apparent. > > But the real bug is not in that commit, but a problem with imx6/7 not > configuring a setting in the RC correctly without pcieportbus, which > should not be necessary. > > See "[v4] PCI: imx: make msi work without CONFIG_PCIEPORTBUS=y" by > Richard Zhu for a real fix. Awesome! I can verify this patch on our i.MX6 boards, if Richard Zhu (or anyone else) is interested. > > There another bug that makes this driver sometimes lose an MSI, but Is it the one you alerted me to before? https://patchwork.kernel.org/patch/10657987/ We are planning to use the PCIe controller in a production environment - to communicate with a tg3 based Broadcom ethernet NIC. What are the practical consequences of this bug? What is the state of the patch that fixes it? Last patch activity seems to have been in mid-November? Apologies for the trivial questions, I am by no means a PCIe expert. > that regression was in v4.14 and would not be fixed by your patch, so > this tigon3 problem is almost certainly caused by the previously > mentioned issue with pcieportbus. >