From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E563BC43334 for ; Wed, 22 Jun 2022 06:50:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351493AbiFVGuF (ORCPT ); Wed, 22 Jun 2022 02:50:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59078 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351595AbiFVGt1 (ORCPT ); Wed, 22 Jun 2022 02:49:27 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7FDE136163; Tue, 21 Jun 2022 23:49:26 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2D36BB81C50; Wed, 22 Jun 2022 06:49:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BD321C34114; Wed, 22 Jun 2022 06:49:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1655880563; bh=5X/2z3DnYFBTxCdVc6BnK643pFWE6202pXELvDL5LrQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RzmrczCIbl4FiR4E7XPxESCAURY5n313J2+FHmgOpuDrE2u8WSwJja01eGG+k3e3G gQAULe2ivqoYZtLua7b7530q9iqz0HXPCGjDhyYvraD61p3A6HD7S0LfDa1HJy9Ity vNjNNZu5OV/KKIKg33XRFoQhUeJJIv/VjJ7QeZpa9TTrRh4peo09HuFXwKtCQsIRxr n+/5KxDp19d9ivthUYpdMgiaVEqqe8fegkJr1rHzV5nWcCqndEbrZi5RTx2IGwVn9R gztmtakDNfyeSd/kaSnI1Gx8wpofZyg1czgtcJzCQ2U2Viw06l4bJ+t53dlyqzQgvH BlxN/2/403aWw== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1o3uAx-0003ON-UD; Wed, 22 Jun 2022 08:49:20 +0200 Date: Wed, 22 Jun 2022 08:49:19 +0200 From: Johan Hovold To: Bjorn Helgaas Cc: Robert Marko , svarbanov@mm-sol.com, agross@kernel.org, bjorn.andersson@linaro.org, lpieralisi@kernel.org, robh@kernel.org, kw@linux.com, bhelgaas@google.com, p.zabel@pengutronix.de, jingoohan1@gmail.com, linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, johan+linaro@kernel.org Subject: Re: [PATCH v2] PCI: qcom: fix IPQ8074 Gen2 support Message-ID: References: <20220621112330.448754-1-robimarko@gmail.com> <20220621203211.GA1330530@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220621203211.GA1330530@bhelgaas> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 21, 2022 at 03:32:11PM -0500, Bjorn Helgaas wrote: > On Tue, Jun 21, 2022 at 01:23:30PM +0200, Robert Marko wrote: > > IPQ8074 has one Gen2 and one Gen3 port, currently the Gen2 port will > > cause the system to hang as its using DBI registers in the .init > > and those are only accesible after phy_power_on(). > > Is the fact that IPQ8074 has both a Gen2 and a Gen3 port relevant to > this patch? I don't see the connection. > > I see that qcom_pcie_host_init() does: > > qcom_pcie_host_init > pcie->cfg->ops->init(pcie) > phy_power_on(pcie->phy) > pcie->cfg->ops->post_init(pcie) > > and that you're moving DBI register accesses from > qcom_pcie_init_2_3_3() to qcom_pcie_post_init_2_3_3(). > > But I also see DBI register accesses in other .init() functions: > > qcom_pcie_init_2_1_0 > qcom_pcie_init_1_0_0 (oddly out of order) > qcom_pcie_init_2_3_2 > qcom_pcie_init_2_4_0 > > Why do these accesses not need to be moved? I assume it's because > pcie->phy is an optional PHY and phy_power_on() does nothing on those > controllers? At least the QMP PHY driver does not implement the PHY power_on op and instead fires everything up already at phy_init(). That may explain the difference in behaviour here. Johan