Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp3174117ioo; Sun, 29 May 2022 16:05:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxYogc8jzhAyOT4U6VzI/c3n0laOQdC+q/bAKp5pcfZShAZSS+88NxjQ0bAQDSVq8brfkRD X-Received: by 2002:a17:90b:4c4a:b0:1e3:3b3:8800 with SMTP id np10-20020a17090b4c4a00b001e303b38800mr1373994pjb.6.1653865501329; Sun, 29 May 2022 16:05:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653865501; cv=none; d=google.com; s=arc-20160816; b=fHJyHq1PJ2wzNXntHHQs4a2XkfhBYEuyENEOWbYmHoAZBQdD1YbL55Pj9U+BorrvwU OYhloNkFP5HhhSQAgwFHbtJCLhB1CdWYCMBpMjdSpSVk/O1zB3er1VbvleOmhZS0wcX7 jc/lJrGkuauP2qu03OpAo57Cn/lxJdzHm6C6BTIcZqiQF2vw6tlpjZQrCjDdvTFmAEaV EbSHYcc/g0wx1LwqMaiO8r11QeYo76y7bCriweXHMyJ+M3/QcV/Yzmq6KxHwxyMP5+mH Tr+6mjea4GZ8o39/wmPJclyVU2p2zC9X0+S8/AqJbDaIY4TFG9oA1kdo7I/jUarxtwcj SWnw== 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=Zw4bV2oI1Hw+9wOMJRlsF8ruqPUMnCJDLXJeSgzLoQg=; b=EeJ5OTBgkz02wV8pkXCo3A8IV7EEDOIfO4V+0KwKawJaLmBOYD8Kk/iSIO09bOSO7M K6ZTliZHjJO88gos41SEReP+5fXxaZ7R4dHnkVeQhChSdLZVWfQuFXTN3EkVQ2a4KOmb v+d1aMPr2f7POa3s44rKzA0SxbKa1/E8kKtPpr06eRX2GZ9O3Gk39uMTCFwU82ad/TyZ bLXjQy/QBWjANFNgVeXmRi8GkHfS6N3RJXihXF7E7aG8CFf/8M0TS4YB2Uzh0FBOq/cq U4zSjRhmys5cbUOBfRFZM30WGFAF9sVgTx+YqYBKFL5RFcBZ7ORS/lffENomQp78XVXI lYiQ== 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 t26-20020a65609a000000b003f70a42d81fsi12543710pgu.319.2022.05.29.16.04.41; Sun, 29 May 2022 16:05:01 -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 S231441AbiE2Rge (ORCPT + 99 others); Sun, 29 May 2022 13:36:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54332 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231407AbiE2Rga (ORCPT ); Sun, 29 May 2022 13:36:30 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 99DB211465; Sun, 29 May 2022 10:36:28 -0700 (PDT) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1nvMq1-0005v5-9X; Sun, 29 May 2022 19:36:25 +0200 Message-ID: Date: Sun, 29 May 2022 19:36:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH v2 1/1] PCI: brcmstb: Fix regression regarding missing PCIe linkup Content-Language: en-US To: Jim Quinlan , linux-pci , Nicolas Saenz Julienne , Bjorn Helgaas , James Dutton , Cyril Brulebois , bcm-kernel-feedback-list , Jim Quinlan Cc: Florian Fainelli , Lorenzo Pieralisi , Rob Herring , =?UTF-8?Q?Krzysztof_Wilczy=c5=84ski?= , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , open list References: <20220528224423.7017-1-jim2101024@gmail.com> <20220528224423.7017-2-jim2101024@gmail.com> From: Thorsten Leemhuis In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1653845788;9339f1b1; X-HE-SMSGID: 1nvMq1-0005v5-9X X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,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 29.05.22 18:52, Jim Quinlan wrote: > On Sat, May 28, 2022 at 6:44 PM Jim Quinlan wrote: >> >> commit 93e41f3fca3d ("PCI: brcmstb: Add control of subdevice voltage regulators") > >> Signed-off-by: Jim Quinlan >> introduced a regression on the PCIe RPi4 Compute Module. If the PCIe >> root port DT node described in [2] was missing, no linkup would be attempted, >> and subsequent accesses would cause a panic because this particular PCIe HW >> causes a CPU abort on illegal accesses (instead of returning 0xffffffff). >> >> We fix this by allowing the DT root port node to be missing, as it behaved >> before the original patchset messed things up. >> >> In addition, two small changes are made: >> >> 1. Having pci_subdev_regulators_remove_bus() call >> regulator_bulk_free() in addtion to regulator_bulk_disable(). >> 2. Having brcm_pcie_add_bus() return 0 if there is an >> error in calling pci_subdev_regulators_add_bus(). >> Instead, we dev_err() and turn on our refusal mode instead. >> >> It would be best if this commit were tested by someone with a Rpi CM4 >> platform, as that is how the regression was found. I have only emulated >> the problem and fix on different platform. >> >> Note that a bisection identified >> >> commit 830aa6f29f07 ("PCI: brcmstb: Split brcm_pcie_setup() into two funcs") >> >> as the first failing commit. This commit is a regression, but is unrelated >> and was fixed by a subsequent commit in the original patchset. >> >> [1] https://bugzilla.kernel.org/show_bug.cgi?id=215925 >> [2] Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml >> >> Fixes: 93e41f3fca3d ("PCI: brcmstb: Add control of subdevice voltage regulators") >> Fixes: 830aa6f29f07 ("PCI: brcmstb: Split brcm_pcie_setup() into two funcs") >> Link: https://bugzilla.kernel.org/show_bug.cgi?id=215925 > Thorston -- I forgot to replace the bugzilla link; I'll get it on V3. -- Jim Don't worry to much about these details that might matter for regzbot normally (the automatic handling of links to bugzilla ticket is sadly dysfunctional currently anyway). Just getting the issue fixed in the not-to-distant future is what I mainly care about. :-D Ciao Thorsten