Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp146582rwd; Wed, 7 Jun 2023 21:18:56 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ41sZJRlCvOsxu2yBdsbFIXuOeTUN4+AMXdNTUvIPMUHvLBCU2FMq7YhcacD3HodXiJPZKa X-Received: by 2002:a05:622a:174b:b0:3f9:cf74:2bb5 with SMTP id l11-20020a05622a174b00b003f9cf742bb5mr7840qtk.68.1686197936069; Wed, 07 Jun 2023 21:18:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686197936; cv=none; d=google.com; s=arc-20160816; b=b1YXM78g7IVK96sY4YMxPcYkEZKKDhhowCqqhl0DxMBMCll54KyNN2ppbpgbm2dbVz 0SBgY+M43oufkv0o8IS++FbrepDVZld7cBa1K+1JTbcUYAGum82oJizG/nhq2sl/mDej gmt6wNPyMSrWYbSa+x4tlGEJ1+zcLtk7obHr7kFqRP/nQw2KWRvTaUzSxLLt8+am3yvo HhaqTOIjCmxo5b7ziIQV7C6LYmouye4L4MYXcKRiWIY1sgNszAYMIOutfuXpVxH3mLOc evxNCTCDa2Wi9NeqATLREjPmR6ozYTR9dr8sPM6gZ6pdBRWTwsuZWXy3r03WR50PGgDa h48A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:to:subject:cc:user-agent:mime-version :date:message-id:dkim-signature; bh=ViAmDMcIbipS/ZX+/PXy2coOp+SWiCjOawla5igQ6aY=; b=dsqOMiav2LvZcvGz1bSNN7IuASqtJtqFQwH9A3PnsWO54Ol3wAlvxiwPNFYUoxlHa9 EGSx9NuF/EDN0vacXsyNQ9smpkvHiUj7CsEVFUhs/UwwtTnrpd6L2N5duX0e6259unuR 9kdBr5+j4+WhRPAvgso4wqDf3/pAF58SzoJd/w+Cy8QDjgqMN2bQi11YVwVXoK7xyrDb axadIagksk1LuAud85lNLmOVP6P+Yb/yYdrupMEm26C6M3BequAnQBYjW7BWkrH7ccUG LSiDc7QDH8/AOnaGKhBVvPKWPzYtDlOTLaV4whd5afh9CcKRu70Ti6tcfEjTa2Q+I3kp j1MA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="CXyZDOO/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v202-20020a6361d3000000b00542bea60d27si388011pgb.39.2023.06.07.21.18.39; Wed, 07 Jun 2023 21:18:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="CXyZDOO/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234014AbjFHEC3 (ORCPT + 99 others); Thu, 8 Jun 2023 00:02:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45552 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233976AbjFHECY (ORCPT ); Thu, 8 Jun 2023 00:02:24 -0400 Received: from fllv0016.ext.ti.com (fllv0016.ext.ti.com [198.47.19.142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A2B321702; Wed, 7 Jun 2023 21:02:19 -0700 (PDT) Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 358424Rr077185; Wed, 7 Jun 2023 23:02:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1686196924; bh=ViAmDMcIbipS/ZX+/PXy2coOp+SWiCjOawla5igQ6aY=; h=Date:CC:Subject:To:References:From:In-Reply-To; b=CXyZDOO/uwD5DHpXU8uAK3ohO0rHPZ11XFNntHM2qpAGO5ovj5q78Ztk+r9Osg/+9 cz9/dUULVtv7hAHOEDU225JnqQngS+HLcLhQihYj4/ohaDfsJ1l43dLpWptpDDi1jF QAU6Fqx8zB7n/xjg1jvLD+eL8TcP1gY36eIAw1xA= Received: from DFLE106.ent.ti.com (dfle106.ent.ti.com [10.64.6.27]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 358424Ln088582 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 7 Jun 2023 23:02:04 -0500 Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE106.ent.ti.com (10.64.6.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 7 Jun 2023 23:02:03 -0500 Received: from lelv0327.itg.ti.com (10.180.67.183) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 7 Jun 2023 23:02:03 -0500 Received: from [172.24.145.61] (ileaxei01-snat2.itg.ti.com [10.180.69.6]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 35841xXd125035; Wed, 7 Jun 2023 23:02:00 -0500 Message-ID: <5888f3ff-bc95-16ed-3cae-958719d87874@ti.com> Date: Thu, 8 Jun 2023 09:31:59 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 CC: , , , , , , , , , , , Subject: Re: [PATCH v3] PCI: cadence: Fix Gen2 Link Retraining process To: Lorenzo Pieralisi References: <20230607091427.852473-1-s-vadapalli@ti.com> Content-Language: en-US From: Siddharth Vadapalli In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Lorenzo, Thank you for reviewing this patch. On 07/06/23 15:53, Lorenzo Pieralisi wrote: > On Wed, Jun 07, 2023 at 02:44:27PM +0530, Siddharth Vadapalli wrote: >> The Link Retraining process is initiated to account for the Gen2 defect in >> the Cadence PCIe controller in J721E SoC. The errata corresponding to this >> is i2085, documented at: >> https://www.ti.com/lit/er/sprz455c/sprz455c.pdf >> >> The existing workaround implemented for the errata waits for the Data Link >> initialization to complete and assumes that the link retraining process >> at the Physical Layer has completed. However, it is possible that the >> Physical Layer training might be ongoing as indicated by the >> PCI_EXP_LNKSTA_LT bit in the PCI_EXP_LNKSTA register. >> >> Fix the existing workaround, to ensure that the Physical Layer training >> has also completed, in addition to the Data Link initialization. >> >> Fixes: 4740b969aaf5 ("PCI: cadence: Retrain Link to work around Gen2 training defect") >> Signed-off-by: Siddharth Vadapalli >> Reviewed-by: Vignesh Raghavendra >> --- >> >> Hello, >> >> This patch is based on linux-next tagged next-20230606. >> >> v2: >> https://lore.kernel.org/r/20230315070800.1615527-1-s-vadapalli@ti.com/ >> Changes since v2: >> - Merge the cdns_pcie_host_training_complete() function with the >> cdns_pcie_host_wait_for_link() function, as suggested by Bjorn >> for the v2 patch. >> - Add dev_err() to notify when Link Training fails, since this is a >> fatal error and proceeding from this point will almost always crash >> the kernel. >> >> v1: >> https://lore.kernel.org/r/20230102075656.260333-1-s-vadapalli@ti.com/ >> Changes since v1: >> - Collect Reviewed-by tag from Vignesh Raghavendra. >> - Rebase on next-20230315. >> >> Regards, >> Siddharth. >> >> .../controller/cadence/pcie-cadence-host.c | 20 +++++++++++++++++++ >> 1 file changed, 20 insertions(+) >> >> diff --git a/drivers/pci/controller/cadence/pcie-cadence-host.c b/drivers/pci/controller/cadence/pcie-cadence-host.c >> index 940c7dd701d6..70a5f581ff4f 100644 >> --- a/drivers/pci/controller/cadence/pcie-cadence-host.c >> +++ b/drivers/pci/controller/cadence/pcie-cadence-host.c >> @@ -12,6 +12,8 @@ >> >> #include "pcie-cadence.h" >> >> +#define LINK_RETRAIN_TIMEOUT HZ >> + >> static u64 bar_max_size[] = { >> [RP_BAR0] = _ULL(128 * SZ_2G), >> [RP_BAR1] = SZ_2G, >> @@ -80,8 +82,26 @@ static struct pci_ops cdns_pcie_host_ops = { >> static int cdns_pcie_host_wait_for_link(struct cdns_pcie *pcie) >> { >> struct device *dev = pcie->dev; >> + unsigned long end_jiffies; >> + u16 link_status; >> int retries; >> >> + /* Wait for link training to complete */ >> + end_jiffies = jiffies + LINK_RETRAIN_TIMEOUT; >> + do { >> + link_status = cdns_pcie_rp_readw(pcie, CDNS_PCIE_RP_CAP_OFFSET + PCI_EXP_LNKSTA); >> + if (!(link_status & PCI_EXP_LNKSTA_LT)) >> + break; > > You can use a bool variable eg link_trained and use that below. Sure, I will do that. link_trained = !(link_status & PCI_EXP_LNKSTA_LT); within the do-while loop and checking for it to be true in the loop as well as below. > >> + usleep_range(0, 1000); >> + } while (time_before(jiffies, end_jiffies)); >> + >> + if (!(link_status & PCI_EXP_LNKSTA_LT)) { >> + dev_info(dev, "Link training complete\n"); >> + } else { >> + dev_err(dev, "Fatal! Link training incomplete\n"); >> + return -ETIMEDOUT; >> + } > > I don't necessarily see the reason why you are adding additional > logging, more so given that this now does not affect just the > workaround but all cadence controllers. > > Actually, is that something you have tested and considered ? While I agree that I could have performed the entire Link Training check only if the Gen2 Link Retraining Quirk is set for the RC, considering that the completion of the Link Training is a necessity irrespective of whether or not the Quirk exists, I preferred to add the check unconditionally. I would like to point out that the race condition responsible for the crash is the following: Without the completion of the Physical Layer link training, the call to the cdns_pci_map_bus() function in order to access the End Point's registers (if an EP device is connected) results in the crash. This is primarily observed only on RT Linux where the software call to cdns_pci_map_bus() by PCI subsystem occurs quite fast, before the Physical Layer link training is complete. For this reason, irrespective of whether the Physical Layer link training occurs only once because of the default flow or occurs a second time due to the Gen2 Link Retraining Quirk, it appears to me that the crash could potentially occur in both cases if we don't wait for the Physical Layer link training to complete. Please let me know if this sounds acceptable. If not, I will check if the quirk is set before proceeding to verify link training completion and implement this in the v4 patch. > > Thanks, > Lorenzo > >> + >> /* Check if the link is up or not */ >> for (retries = 0; retries < LINK_WAIT_MAX_RETRIES; retries++) { >> if (cdns_pcie_link_up(pcie)) { >> -- >> 2.25.1 >> -- Regards, Siddharth.