Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp467295pxb; Thu, 21 Oct 2021 03:14:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJytArdYsx67cVFFa49dzQng++gEO/dQR9b9Y6/8jKhUl8KpPPorHl2z9EMfkbNtcji8rFiN X-Received: by 2002:a17:906:2757:: with SMTP id a23mr6134876ejd.230.1634811289503; Thu, 21 Oct 2021 03:14:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634811289; cv=none; d=google.com; s=arc-20160816; b=02+6B7T8y6ue/38dsf9+Vsfel2pO5juWV7/UvBYQOd3KPpjyD6ExFFa7RiYbmRKDcd tsKUmzEvumCwlG9rbKmQRPQ8N4bxH2aXhl7nAPWdUUrs079MYaIDyh/V6pPO7LRSI+Bt 2y8a3+3qWGNAiMFplrNLENCfPbdcI/yZWiSyoHJRejcUbquOl6dhRrf4Ni//vdmJH97u flofuMEsL5IwcxX/UNb80OOiKYH7MZwjR6mEyhcLsQgC7yfpi4gYFCUsm1we41Id4vGQ v6job8D7eLlcWTmyayXY/52/YLNYIAkhuwRLDWm1dGGK9ObViTiUlgte8dPr+ogcdHRw 0MdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=AZefuyZn/KLkX5tfjUs7lQjfWBtCLiYTa/QBcjM6sZw=; b=YxXjlXCr9jJdUkrT6ywm3LLHohyND5XhXzjadNvN3XwRqXycxMcIh6lCdQ9W0Uk9JT +WvkIWvKr0yaiwMdsILKoN+hasQtFhzIzg3M+dIgxlUJj1PEW/bSljUMbpR8GH1hMLTZ V3tZ+wrI3swpa/7vlfYiyGqeeSzyUsJuy2OCFUDOzdQ39zY99yE3aOiPaPSWo0tY8ZfQ Ye50P68B7EGH4NPdGHZtx9PQ0qPrWS5X4nYGxbVrvGo9DsAq6uTSrIpDlKF+OANCb5NG IReaNTqLwCvSdoLRnqncYHZ4pR2sPJIN6Bx+UEpGpK4yEJEjytTkMauFl2Y1qGLERqGb 1UYw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d11si7481447edj.442.2021.10.21.03.14.26; Thu, 21 Oct 2021 03:14:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229570AbhJUKMI (ORCPT + 99 others); Thu, 21 Oct 2021 06:12:08 -0400 Received: from foss.arm.com ([217.140.110.172]:40852 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229567AbhJUKMH (ORCPT ); Thu, 21 Oct 2021 06:12:07 -0400 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 8456CED1; Thu, 21 Oct 2021 03:09:51 -0700 (PDT) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E4A143F694; Thu, 21 Oct 2021 03:09:49 -0700 (PDT) Date: Thu, 21 Oct 2021 11:09:44 +0100 From: Lorenzo Pieralisi To: Mauro Carvalho Chehab Cc: linuxarm@huawei.com, mauro.chehab@huawei.com, Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Songxiaowei , Binghui Wang , Bjorn Helgaas , Rob Herring , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH v13 09/10] PCI: kirin: fix poweroff sequence Message-ID: <20211021100944.GA11904@lpieralisi> References: <8116a4ddaaeda8dd056e80fa0ee506c5c6f42ca7.1634539769.git.mchehab+huawei@kernel.org> <20211018102127.GD17152@lpieralisi> <20211018153716.0370a66c@sal.lan> <20211019094048.GA24481@lpieralisi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211019094048.GA24481@lpieralisi> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 19, 2021 at 10:40:48AM +0100, Lorenzo Pieralisi wrote: > On Mon, Oct 18, 2021 at 03:37:16PM +0100, Mauro Carvalho Chehab wrote: > > Em Mon, 18 Oct 2021 11:21:27 +0100 > > Lorenzo Pieralisi escreveu: > > > > > On Mon, Oct 18, 2021 at 08:07:34AM +0100, Mauro Carvalho Chehab wrote: > > > > This driver currently doesn't call dw_pcie_host_deinit() > > > > at the .remove() callback. This can cause an OOPS if the driver > > > > is unbound. > > > > > > This looks like a fix, it has to be marked as such. > > > > Well, without patch 10/10, the .remove() ops won't be called, > > so, it is not really a fix, but I can surely add a c/c > > stable@vger.kernel.org and add a Fixes: tag here. > > You have a point - unless we send patch 10 to stable as well I > would not tag it then. > > > > > While here, add a poweroff function, in order to abstract > > > > between the internal and external PHY logic. > > > > > > > > Acked-by: Xiaowei Song > > > > Signed-off-by: Mauro Carvalho Chehab > > > > --- > > > > > > > > See [PATCH v13 00/10] at: https://lore.kernel.org/all/cover.1634539769.git.mchehab+huawei@kernel.org/ > > > > > > > > drivers/pci/controller/dwc/pcie-kirin.c | 30 ++++++++++++++++--------- > > > > 1 file changed, 20 insertions(+), 10 deletions(-) > > > > > > > > diff --git a/drivers/pci/controller/dwc/pcie-kirin.c b/drivers/pci/controller/dwc/pcie-kirin.c > > > > index b17a194cf78d..ffc63d12f8ed 100644 > > > > --- a/drivers/pci/controller/dwc/pcie-kirin.c > > > > +++ b/drivers/pci/controller/dwc/pcie-kirin.c > > > > @@ -680,6 +680,23 @@ static const struct dw_pcie_host_ops kirin_pcie_host_ops = { > > > > .host_init = kirin_pcie_host_init, > > > > }; > > > > > > > > +static int kirin_pcie_power_off(struct kirin_pcie *kirin_pcie) > > > > +{ > > > > + int i; > > > > + > > > > + if (kirin_pcie->type == PCIE_KIRIN_INTERNAL_PHY) > > > > + return hi3660_pcie_phy_power_off(kirin_pcie); > > > > + > > > > + for (i = 0; i < kirin_pcie->n_gpio_clkreq; i++) { > > > > + gpio_direction_output(kirin_pcie->gpio_id_clkreq[i], 1); > > > > + } > > > > > > It looks like you are adding functionality here (ie gpio), not > > > just wrapping common code in a function. > > > > It is just reverting the power on logic there. > > What I am saying is that executing: > > for (i = 0; i < kirin_pcie->n_gpio_clkreq; i++) > gpio_direction_output(kirin_pcie->gpio_id_clkreq[i], 1); > > is an addition to what current code does AFAICS (ie you are not just > moving code into a function - kirin_pcie_power_off(), you are adding > to it), it is a logical change that belongs in a separate patch. > > There are two logical changes: > > - Adding dw_pcie_host_deinit() > - Moving PHY power off code into kirin_pcie_power_off() (and adding > gpio handling in it) > > That's what I read from the diffstat, please correct me if I am wrong. Hi Mauro, any comment on the above ? It is the last question I have before merging the series, please let me know. Thanks, Lorenzo