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 X-Spam-Level: X-Spam-Status: No, score=-10.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B6EAC11F68 for ; Wed, 30 Jun 2021 09:47:09 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 664B961D08 for ; Wed, 30 Jun 2021 09:47:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 664B961D08 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:Cc:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=aaLFwW7eppVSFQrPcQGiY5ixfJ1/XSG0NpWLttGC6D8=; b=r+R/aJcwYdaCbDtSiObjtsdtRF SXu3dRNFAlgBwBZ6jRQ5UkZC9Isx+eXPylFk2R320Qm48zbnxM+ITsQX9KnOqv0uMt1+MCfmJsvrR 12+KkNCgXecX/3hGtv9eTGdW+CDU1OzfAxialQ64auLqlroTnl2Xqq/SdzM9bxwH/LPS73lpSiKwR s40MO21Dmv28YQuA0o736mmwHxvAL/JpcbXGpFZIKYXZ/sw0l5MwmqbfQQWIDkbeJ7NJTEmspAb/f lvTS3W6hNQs0G5+qzf5JLDpy3Q7y5GSWxFnL76xPjrZFFSEbftyk9uNpoNrG+3Hc4Tm6j4clGLSxx V8SmJTxA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1lyWmF-00DWx3-EA; Wed, 30 Jun 2021 09:45:03 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1lyWmB-00DWvZ-Fc; Wed, 30 Jun 2021 09:45:01 +0000 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 40A5D1042; Wed, 30 Jun 2021 02:44:53 -0700 (PDT) Received: from [10.57.40.45] (unknown [10.57.40.45]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 500E33F718; Wed, 30 Jun 2021 02:44:49 -0700 (PDT) Subject: Re: [PATCH v2] PCI: rockchip: Avoid accessing PCIe registers with clocks gated To: Bjorn Helgaas Cc: Javier Martinez Canillas , linux-kernel@vger.kernel.org, Peter Robinson , Shawn Lin , Bjorn Helgaas , Heiko Stuebner , Lorenzo Pieralisi , Rob Herring , linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org, Michal Simek , Ley Foon Tan , rfi@lists.rocketboards.org, Jingoo Han , Thierry Reding , Jonathan Hunter , linux-tegra@vger.kernel.org References: <20210629231410.GA4097899@bjorn-Precision-5520> From: Robin Murphy Message-ID: Date: Wed, 30 Jun 2021 10:44:44 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210629231410.GA4097899@bjorn-Precision-5520> Content-Language: en-GB X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210630_024459_679176_F9823C50 X-CRM114-Status: GOOD ( 28.71 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2021-06-30 00:14, Bjorn Helgaas wrote: > On Tue, Jun 29, 2021 at 11:52:44AM +0100, Robin Murphy wrote: >> On 2021-06-29 07:17, Javier Martinez Canillas wrote: >>> On 6/29/21 2:38 AM, Bjorn Helgaas wrote: >>>> On Thu, Jun 24, 2021 at 05:40:40PM -0500, Bjorn Helgaas wrote: >>> >>> [snip] >>> >>>>>> >>>>>> So let's just move all the IRQ init before the pci_host_probe() call, that >>>>>> will prevent issues like this and seems to be the correct thing to do too. >>>>> >>>>> Previously we registered rockchip_pcie_subsys_irq_handler() and >>>>> rockchip_pcie_client_irq_handler() before the PCIe clocks were >>>>> enabled. That's a problem because they depend on those clocks being >>>>> enabled, and your patch fixes that. >>>>> >>>>> rockchip_pcie_legacy_int_handler() depends on rockchip->irq_domain, >>>>> which isn't initialized until rockchip_pcie_init_irq_domain(). >>>>> Previously we registered rockchip_pcie_legacy_int_handler() as the >>>>> handler for the "legacy" IRQ before rockchip_pcie_init_irq_domain(). >>>>> >>>>> I think your patch *also* fixes that problem, right? >>>> >>>> The lack of consistency in how we use >>>> irq_set_chained_handler_and_data() really bugs me. >>>> >>>> Your patch fixes the ordering issue where we installed >>>> rockchip_pcie_legacy_int_handler() before initializing data >>>> (rockchip->irq_domain) that it depends on. >>>> >>>> But AFAICT, rockchip still has the problem that we don't *unregister* >>>> rockchip_pcie_legacy_int_handler() when the rockchip-pcie module is >>>> removed. Doesn't this mean that if we unload the module, then receive >>>> an interrupt from the device, we'll try to call a function that is no >>>> longer present? >>> >>> Good question, I don't to be honest. I'll have to dig deeper on this but >>> my experience is that the module removal (and device unbind) is not that >>> well tested on ARM device drivers in general. >> >> Well, it does use devm_request_irq() so the handler should be unregistered >> by devres *after* ->remove has finished, however that does still leave a >> potential race window in which a pending IRQ could be taken during the later >> part of rockchip_pcie_remove() after it has started turning off critical >> things. Unless the clocks and regulators can also be delegated to devres, it >> might be more robust to explicitly manage the IRQs as well. Mixing the two >> schemes can be problematic when the exact order of both setup and teardown >> matters. > > I don't understand the devm_request_irq() connection. I'm looking at > this irq_set_chained_handler_and_data() call [1]: > > static int rockchip_pcie_setup_irq(struct rockchip_pcie *rockchip) > { > ... > irq = platform_get_irq_byname(pdev, "legacy"); > irq_set_chained_handler_and_data(irq, > rockchip_pcie_legacy_int_handler, > rockchip); > > irq = platform_get_irq_byname(pdev, "client"); > ... > > We look up "irq", pass it to irq_set_chained_handler_and_data(), and > throw it away without saving it anywhere. How would anything know how > to unregister rockchip_pcie_legacy_int_handler()? > > I could imagine irq_set_chained_handler_and_data() saving what's > needed for unregistration, but I would think that would require a > device pointer, which we don't give it. > > I'm IRQ-illiterate, so please educate me! Oh, my mistake, I was looking at the "sys" and "client" IRQs and spoke too soon; the "legacy" IRQ does appear to be completely leaked as you say, so there are two degrees of issue here. Robin. > > Bjorn > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/controller/pcie-rockchip-host.c?id=v5.13#n562 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel