Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2776716imm; Mon, 24 Sep 2018 09:43:09 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZ1cal903pmheiJLhGc/FctYIXdogkcNJhTaKQaRioJVisDCLy5fkfd1traAROqbi44B+RM X-Received: by 2002:a62:5a01:: with SMTP id o1-v6mr11250141pfb.0.1537807389126; Mon, 24 Sep 2018 09:43:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537807389; cv=none; d=google.com; s=arc-20160816; b=ZKHZMpGP7b4I7blpIVYWGGPYgIXsVHovrUMVONSFm+BVG4RBgD0oPSCW76zea2V5X/ CTxEcu/JANUmXrxGPLLLYQ9H2/NbbuAwrhh/kgclGDo6jh4yJ/Gn1b/HzQcQj7RtpBAQ wUXjaBcZwNt0dKYDW+wax1I4fKUTiDl5nT2JeI1P9nNSBvfLaX1ll17AFwp+td++K8aU MBZujOVJsJ0VM9ZmOEGsQmeTgzKVt5jU2PnGZwHuxsmtViZPTnT28NCisFaUs5fYQ/tC /iznTT162+T5xYaaObsjL3zBDmY+7+kMOmu+ReC0AxmizpOCC7FSyBpy2KX8ygSQ/Sng 5HXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=4/MEPwm3iRnct0UMjqYQ0A6+zWbbpVImC9oB4PPRwLU=; b=xnl6W7Lxodw/oem1Wn1JiRPYX1NRC1bNXDiiv0dyGswL4J/guhVBPPQ2edmxZvzliZ 9IHkN9JfR9wgJw1+CHsQ4opv/anzm9E0mCiJ6ZXgdb3W1c9TT9OIcQhgcvKa0SMlvgJP Js51LxnLtz4HFe/Ql+w9U9g5BYwlfzwfbTkL/XqnqlpX0vYXCcTYN7jqmrGjMdwKGxOS hUnTWKhYPQuFqOPWmvYiGIwUyK/rp3lAOmSUSiXtsg53/60n12+GiuNmRe19dj7Utkxe z41JBfWxjaIPzZOO4fqVWX7ZCz5X93DFMCjwcMojSACGCOh+oHweRKR0XiksIQWJ6bas wESA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o30-v6si4304493pgb.386.2018.09.24.09.42.52; Mon, 24 Sep 2018 09:43:09 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731368AbeIXWpW (ORCPT + 99 others); Mon, 24 Sep 2018 18:45:22 -0400 Received: from foss.arm.com ([217.140.101.70]:38560 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726400AbeIXWpW (ORCPT ); Mon, 24 Sep 2018 18:45:22 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 440C780D; Mon, 24 Sep 2018 09:42:21 -0700 (PDT) Received: from red-moon (red-moon.emea.arm.com [10.4.13.120]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9BB9F3F5BD; Mon, 24 Sep 2018 09:42:19 -0700 (PDT) Date: Mon, 24 Sep 2018 17:42:58 +0100 From: Lorenzo Pieralisi To: Thomas Petazzoni Cc: Russell King - ARM Linux , Jan =?iso-8859-1?Q?Kundr=E1t?= , Baruch Siach , Jason Cooper , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Helgaas , linux-arm-kernel@lists.infradead.org Subject: Re: [BISECTED] Regression: Solidrun Clearfog Base won't boot since "PCI: mvebu: Only remap I/O space if configured" Message-ID: <20180924164258.GA19513@red-moon> References: <5ad46fec-a71a-477a-b23f-d20aacfb481d@cesnet.cz> <20180913104241.65db8243@windsurf> <20180924101213.GO30658@n2100.armlinux.org.uk> <20180924122614.70738b5c@windsurf> <20180924111341.GP30658@n2100.armlinux.org.uk> <20180924141203.3df9707a@windsurf> <20180924124620.GA10322@e107981-ln.cambridge.arm.com> <20180924151040.5e57462b@windsurf> <20180924141512.GA11875@e107981-ln.cambridge.arm.com> <20180924165218.26c7c418@windsurf> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180924165218.26c7c418@windsurf> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 24, 2018 at 04:52:18PM +0200, Thomas Petazzoni wrote: > Hello, > > On Mon, 24 Sep 2018 15:15:12 +0100, Lorenzo Pieralisi wrote: > > > I understand that, I wanted to make sure we come up with a fix asap > > and what I put forward would cover everything discussed in this thread, > > at least temporarily, giving us time to check ISA related issues while > > unmapping IO space. > > Something like this should implemented what you suggest I guess: > > diff --git a/drivers/pci/controller/pci-mvebu.c b/drivers/pci/controller/pci-mvebu.c > index 50eb0729385b..a41d79b8d46a 100644 > --- a/drivers/pci/controller/pci-mvebu.c > +++ b/drivers/pci/controller/pci-mvebu.c > @@ -1145,7 +1145,6 @@ static int mvebu_pcie_parse_request_resources(struct mvebu_pcie *pcie) > { > struct device *dev = &pcie->pdev->dev; > struct device_node *np = dev->of_node; > - unsigned int i; > int ret; > > INIT_LIST_HEAD(&pcie->resources); > @@ -1179,13 +1178,58 @@ static int mvebu_pcie_parse_request_resources(struct mvebu_pcie *pcie) > resource_size(&pcie->io) - 1); > pcie->realio.name = "PCI I/O"; > > + pci_add_resource(&pcie->resources, &pcie->realio); > + } > + > + return devm_request_pci_bus_resources(dev, &pcie->resources); > +} > + > +/* > + * This is a copy of pci_host_probe(), except that it does the I/O > + * remap as the last step, once we are sure we won't fail. > + * > + * It should be removed once the I/O remap error handling issue has > + * been sorted out. > + */ > +static int mvebu_pci_host_probe(struct pci_host_bridge *bridge) > +{ > + struct mvebu_pcie *pcie; > + struct pci_bus *bus, *child; > + int ret; > + > + ret = pci_scan_root_bus_bridge(bridge); > + if (ret < 0) { > + dev_err(bridge->dev.parent, "Scanning root bridge failed"); > + return ret; > + } > + > + pcie = pci_host_bridge_priv(bridge); > + if (resource_size(&pcie->io) != 0) { > + unsigned int i; > + > for (i = 0; i < resource_size(&pcie->realio); i += SZ_64K) > pci_ioremap_io(i, pcie->io.start + i); > + } > > - pci_add_resource(&pcie->resources, &pcie->realio); > + bus = bridge->bus; > + > + /* > + * We insert PCI resources into the iomem_resource and > + * ioport_resource trees in either pci_bus_claim_resources() > + * or pci_bus_assign_resources(). > + */ > + if (pci_has_flag(PCI_PROBE_ONLY)) { > + pci_bus_claim_resources(bus); > + } else { > + pci_bus_size_bridges(bus); > + pci_bus_assign_resources(bus); > + > + list_for_each_entry(child, &bus->children, node) > + pcie_bus_configure_settings(child); > } > > - return devm_request_pci_bus_resources(dev, &pcie->resources); > + pci_bus_add_devices(bus); > + return 0; > } > > static int mvebu_pcie_probe(struct platform_device *pdev) > @@ -1268,7 +1312,7 @@ static int mvebu_pcie_probe(struct platform_device *pdev) > bridge->align_resource = mvebu_pcie_align_resource; > bridge->msi = pcie->msi; > > - return pci_host_probe(bridge); > + return mvebu_pci_host_probe(bridge); > } > > static const struct of_device_id mvebu_pcie_of_match_table[] = { > > If that's what you meant, I'll go ahead and test on actual hardware and > submit as a proper patch. Yes, that's what I meant, I hope that you will have some bandwidth to discuss a way forward for v4.21, when this fix is merged (I think that v4.20 is a tall order but we can try if you will have time to post the patches - I suspect your fix will go in -rc6 if Bjorn can pull it this week). Lorenzo