Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp7563pxb; Tue, 26 Oct 2021 19:51:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5nbQ2dzflrZvvZZaKpHdJEZcVjvyIIaFSWjC3bgeKb/6jMEpp/T6ZMh7D0fgPgvJRmfkx X-Received: by 2002:a17:90b:380d:: with SMTP id mq13mr2806452pjb.131.1635303091836; Tue, 26 Oct 2021 19:51:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635303091; cv=none; d=google.com; s=arc-20160816; b=nRCMIfmErJ5OU6oZIiq3GYVU2d9pzWvdFxCj0L7RyJh3UEfdTeADh2GBYQ4+OohdD9 kalO2UPPY3oNv6c/9xmMu9CpOuLvm1iEMPWxjs3qGxFV4+k3WyXNJhoB7gc8oJks5+zb gIy5uMvuT4XHigelaw9HnTxQPfVyRDj5Ey8SFGEprVsMZvSY+0Zlg24LMG+xdqcXyq68 5A+V+qkpEe+Sw2PxTHz+TwOPdc21Dgv3dPOnMphwyoaOHoWxasA88IcRg2niJLnqWkUn G5aSL6H6yDc1SMsySr8lZkRcV83VyyESAiok0H4s41BAmMXPLPvhFGm5OVNtu+FQz9ht 9+FA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=JKFqHvAUj/swhKiZ6xQUsULS++WB08Ji5K/b1oMWQZY=; b=BVzQOCH6eZB/a5+XzwPs2eTdVb7YK/axHjOUG4NL6HodWn5ia28bmR/Ruk5W3K5nVQ lgC7cmUBkz4YrXntVxfsVGJtqwurnXrspiKKw2mjfl0mvY4erq7XJpEbrXt90cJW53BM peIV1hkpa+Qfh204QMkNsGYVl3XGl188wh38tyQ8SqjXr6KrNbBKISNSDQF+ybs7GlZ/ oKdhxDE7PFMqqOHF5ONTDaVJntviMt0jdkpdzK9aM6d0J+nKT+OqiGpQCnVDYRoULeZH ORcynUgWG6zl1e82A+eExkmD/WvEoklPhIwdamoWMOYHjzR7xW9xS8wPurrUkajwvqBa EHog== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 140si6880775pfy.240.2021.10.26.19.50.47; Tue, 26 Oct 2021 19:51:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235250AbhJZRJO (ORCPT + 99 others); Tue, 26 Oct 2021 13:09:14 -0400 Received: from foss.arm.com ([217.140.110.172]:35102 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234147AbhJZRJN (ORCPT ); Tue, 26 Oct 2021 13:09:13 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7246F1FB; Tue, 26 Oct 2021 10:06:49 -0700 (PDT) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id F07683F70D; Tue, 26 Oct 2021 10:06:47 -0700 (PDT) Date: Tue, 26 Oct 2021 18:06:41 +0100 From: Lorenzo Pieralisi To: Mauro Carvalho Chehab Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , linuxarm@huawei.com, mauro.chehab@huawei.com, Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Songxiaowei , Binghui Wang , Bjorn Helgaas , Rob Herring , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH v14 05/11] PCI: kirin: give more time for PERST# reset to finish Message-ID: <20211026170641.GA20573@lpieralisi> References: <9a365cffe5af9ec5a1f79638968c3a2efa979b65.1634622716.git.mchehab+huawei@kernel.org> <20211022151624.mgsgobjsjgyevnyt@pali> <20211023103059.6add00e6@sal.lan> <20211025102511.GA10529@lpieralisi> <20211025114011.0eca7ccc@sal.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20211025114011.0eca7ccc@sal.lan> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 25, 2021 at 11:40:11AM +0100, Mauro Carvalho Chehab wrote: > Em Mon, 25 Oct 2021 11:25:11 +0100 > Lorenzo Pieralisi escreveu: > > > On Sat, Oct 23, 2021 at 10:30:59AM +0100, Mauro Carvalho Chehab wrote: > > > Hi Pali, > > > > > > Em Fri, 22 Oct 2021 17:16:24 +0200 > > > Pali Roh?r escreveu: > > > > > > > On Tuesday 19 October 2021 07:06:42 Mauro Carvalho Chehab wrote: > > > > > Before code refactor, the PERST# signals were sent at the > > > > > end of the power_on logic. Then, the PCI core would probe for > > > > > the buses and add them. > > > > > > > > > > The new logic changed it to send PERST# signals during > > > > > add_bus operation. That altered the timings. > > > > > > > > > > Also, HiKey 970 require a little more waiting time for > > > > > the PCI bridge - which is outside the SoC - to finish > > > > > the PERST# reset, and then initialize the eye diagram. > > > > > > > > Hello! Which PCIe port do you mean by PCI bridge device? Do you mean > > > > PCIe Root Port? Or upstream port on some external PCIe switch connected > > > > via PCIe bus to the PCIe Root Port? Because all of these (virtual) PCIe > > > > devices are presented as PCI bridge devices, so it is not clear to which > > > > device it refers. > > > > > > HiKey 970 uses an external PCI bridge chipset (a Broadcom PEX 8606[1]), > > > with 3 elements connected to the bus: an Ethernet card, a M.2 slot and > > > a mini PCIe slot. It seems HiKey 970 is unique with regards to PERST# signal, > > > as there are 4 independent PERST# signals there: > > > > > > - one for PEX 8606 (the PCIe root port); > > > - one for Ethernet; > > > - one for M.2; > > > - one for mini-PCIe. > > > > > > After sending the PCIe PERST# signals, the device has to wait for 21 ms > > > before adjusting the eye diagram. > > > > > > [1] https://docs.broadcom.com/docs/PEX_8606_AIC_RDK_HRM_v1.3_06Aug10.pdf > > > > > > > Normally PERST# signal is used to reset endpoint card, other end of PCIe > > > > link and so PERST# signal should not affect PCIe Root Port at all. > > > > > > That's not the case, as PEX 8606 needs to complete its reset sequence > > > for the rest of the devices to be visible. If the wait time is reduced > > > or removed, the devices behind it won't be detected. > > > > These pieces of information should go into the commit log (or I can add > > a Link: tag to this discussion) - it is fundamental to understand these > > changes. > > > > I believe we can merge this series but we have to document this > > discussion appropriately. > > IMO, the best is to add a Link: to the discussion: > > Link: https://lore.kernel.org/all/9a365cffe5af9ec5a1f79638968c3a2efa979b65.1634622716.git.mchehab+huawei@kernel.org/ > > But if you prefer otherwise and want me to re-submit the series, please > let me know. I will squash this patch with the previous one (that describes the bridge PERST# requirements) and add the Link above to the commit log. Lorenzo