Received: by 2002:a05:6358:700f:b0:131:369:b2a3 with SMTP id 15csp1758691rwo; Wed, 2 Aug 2023 21:49:37 -0700 (PDT) X-Google-Smtp-Source: APBJJlEngm3dCmlD3LVpYHza16WdPnECAkeBk768CLpUgl2HDLB2LID4lH2XOjYcTHAJ9KtJc48U X-Received: by 2002:a05:6402:1650:b0:522:216a:28d4 with SMTP id s16-20020a056402165000b00522216a28d4mr6552532edx.7.1691038177742; Wed, 02 Aug 2023 21:49:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691038177; cv=none; d=google.com; s=arc-20160816; b=he0SYiHfp39X02386XV1RkB6zF0lHc+maurWWiAFPRV7vF0ZOehHyc2CEDtalTp1/A eKUpdpfp2WNdw1InJGSxbIKb+2HLn3pnybFc/DfBDhzcuccvY4PaTbFVNRskXHt+ot+x svzC9lX6XvhzAEqKW5ouBpAaFeFO6yP3S8o1F3fb4lixEPAaZ+qawQHVi2tflOgQzbU/ 3E21nzQ9SnoD5ElmNiF3f8UMXJJ+6fTuA2ZK4MR5t+okiur3BW6WIzpks4663geSI6Bf kexNNJ1c/xyrxw/2I9psn7juk5YnjhLkmeOimRXMkjQ0sG4F55W+DuQI3Yh7x14eWAEy hCcQ== 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 :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=IwsAe7bfutYwvnUldUEM6XD4njCqDjXWxp+BIgxyPJM=; fh=vze8Chmw7FXM5KwFXM+Lm7NFE2ya/VQoPeK7a84v91c=; b=Y7A04AEUCsYJglu6FUaMHYbC0QM26HiSyUVCHHSiWoCjcDcMhkeLvlqaQoXQbbZHCE SGRCWgWFGXBAgZgzCBj31hfMT2lgQHLfVeKiOgutE9OiR7R45TfAKubKtG3jMLQCOrLB naEySO8+861Yq7PtW2fdD8N28p+cmdDrx2rJTgnSffgBFUkYpvAcRbJfbBpd+UdHO1n4 Xun5J0HQhnqAn2X2jxDVKTfgLxWgycPMeEfV5yeDuw7QnFrr5zAaYGZjzUByIHomVVaa +q/oXfbfB7O6SdPslCxQAI9WUFqAWORIIHHDw7AX+34Bvy/eB3X/nZkYB3/juIrQWF8W 0AxA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g11-20020a50ee0b000000b0051dd401bf24si11418621eds.447.2023.08.02.21.49.12; Wed, 02 Aug 2023 21:49:37 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232933AbjHCCjZ (ORCPT + 99 others); Wed, 2 Aug 2023 22:39:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57864 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232506AbjHCCjL (ORCPT ); Wed, 2 Aug 2023 22:39:11 -0400 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E67019A0; Wed, 2 Aug 2023 19:39:09 -0700 (PDT) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id 4E8277FF9; Thu, 3 Aug 2023 10:23:49 +0800 (CST) Received: from EXMBX172.cuchost.com (172.16.6.92) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 3 Aug 2023 10:23:49 +0800 Received: from [192.168.125.136] (183.27.98.54) by EXMBX172.cuchost.com (172.16.6.92) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 3 Aug 2023 10:23:47 +0800 Message-ID: <1c546489-40dd-25c5-3ac2-9e3b3fd5a670@starfivetech.com> Date: Thu, 3 Aug 2023 10:23:47 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v1 8/9] PCI: PLDA: starfive: Add JH7110 PCIe controller Content-Language: en-US To: Bjorn Helgaas CC: Minda Chen , Daire McNamara , Conor Dooley , Rob Herring , Krzysztof Kozlowski , Bjorn Helgaas , Lorenzo Pieralisi , =?UTF-8?Q?Krzysztof_Wilczy=c5=84ski?= , Emil Renner Berthing , , , , , Paul Walmsley , "Palmer Dabbelt" , Albert Ou , "Philipp Zabel" , Mason Huo , Leyfoon Tan , Mika Westerberg , "Maciej W. Rozycki" , =?UTF-8?Q?Pali_Roh=c3=a1r?= , =?UTF-8?Q?Marek_Beh=c3=ban?= References: <20230802171805.GA62238@bhelgaas> From: Kevin Xie In-Reply-To: <20230802171805.GA62238@bhelgaas> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [183.27.98.54] X-ClientProxiedBy: EXCAS066.cuchost.com (172.16.6.26) To EXMBX172.cuchost.com (172.16.6.92) X-YovoleRuleAgent: yovoleflag X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_BLOCKED,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 On 2023/8/3 1:18, Bjorn Helgaas wrote: > On Tue, Aug 01, 2023 at 03:05:46PM +0800, Kevin Xie wrote: >> On 2023/8/1 7:12, Bjorn Helgaas wrote: >> ... > >> > The delay required by sec 6.6.1 is a minimum of 100ms following exit >> > from reset or, for fast links, 100ms after link training completes. >> > >> > The comment at the call of advk_pcie_wait_for_link() [2] says it is >> > the delay required by sec 6.6.1, but that doesn't seem right to me. >> > >> > For one thing, I don't think 6.6.1 says anything about "link up" being >> > the end of a delay. So if we want to do the delay required by 6.6.1, >> > "wait_for_link()" doesn't seem like quite the right name. >> > >> > For another, all the *_wait_for_link() functions can return success >> > after 0ms, 90ms, 180ms, etc. They're unlikely to return after 0ms, >> > but 90ms is quite possible. If we avoided the 0ms return and >> > LINK_WAIT_USLEEP_MIN were 100ms instead of 90ms, that should be enough >> > for slow links, where we need 100ms following "exit from reset." >> > >> > But it's still not enough for fast links where we need 100ms "after >> > link training completes" because we don't know when training >> > completed. If training completed 89ms into *_wait_for_link(), we only >> > delay 1ms after that. >> >> That's the point, we will add a extra 100ms after PERST# de-assert >> in the patch-v3 according to Base Spec r6.0 - 6.6.1: >> msleep(100); >> gpiod_set_value_cansleep(pcie->reset_gpio, 0); >> >> + /* As the requirement in PCIe base spec r6.0, system must wait a >> + * minimum of 100 ms following exit from a Conventional Reset >> + * before sending a Configuration Request to the device.*/ >> + msleep(100); >> + >> if (starfive_pcie_host_wait_for_link(pcie)) >> return -EIO; > > For fast links (links that support > 5.0 GT/s), the 100ms starts > *after* link training completes. The above looks OK if starfive only > supports slow links, but then I'm not sure why we would need > starfive_pcie_host_wait_for_link(). > Yes, the maximum speed of JH7110 PCIe is 5.0 GT/s (Gen2x1). About starfive_pcie_host_wait_for_link(): JH7110 SoC only has one root port in each PCIe controller (2 in total) and they do not support hot-plug yet. Thus, We add starfive_pcie_host_wait_for_link() to poll if it is a empty slot. If nothing here, we will exit the probe() of this controller, and it will not go into pci_host_probe() too. This may not be a very standard logic, should we remove it or rewrite in a better way? > Bjorn