From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
"Krzysztof Wilczyński" <kw@linux.com>,
Songxiaowei <songxiaowei@hisilicon.com>,
"Binghui Wang" <wangbinghui@hisilicon.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v13 09/10] PCI: kirin: fix poweroff sequence
Date: Tue, 19 Oct 2021 10:40:48 +0100 [thread overview]
Message-ID: <20211019094048.GA24481@lpieralisi> (raw)
In-Reply-To: <20211018153716.0370a66c@sal.lan>
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 <lorenzo.pieralisi@arm.com> 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 <songxiaowei@hisilicon.com>
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > > ---
> > >
> > > 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.
Thanks,
Lorenzo
> >
> > Also, remove the braces, they aren't needed.
>
> Yeah, I forgot to drop it, when I dropped a tem code that had some
> dev_dbg() on it.
>
> I'll drop on v14.
>
> Regards,
> Mauro
next prev parent reply other threads:[~2021-10-19 9:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 7:07 [PATCH v13 00/10] Add support for Hikey 970 PCIe Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 01/10] PCI: kirin: Reorganize the PHY logic inside the driver Mauro Carvalho Chehab
2021-10-18 10:11 ` Lorenzo Pieralisi
2021-10-18 7:07 ` [PATCH v13 02/10] PCI: kirin: Add support for a PHY layer Mauro Carvalho Chehab
2021-10-18 10:02 ` Lorenzo Pieralisi
2021-10-18 7:07 ` [PATCH v13 03/10] PCI: kirin: Use regmap for APB registers Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 04/10] PCI: kirin: Add support for bridge slot DT schema Mauro Carvalho Chehab
2021-10-18 9:56 ` Lorenzo Pieralisi
2021-10-18 7:07 ` [PATCH v13 05/10] PCI: kirin: Add Kirin 970 compatible Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 06/10] PCI: kirin: Add MODULE_* macros Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 07/10] PCI: kirin: Allow building it as a module Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 08/10] PCI: kirin: Add power_off support for Kirin 960 PHY Mauro Carvalho Chehab
2021-10-18 7:07 ` [PATCH v13 09/10] PCI: kirin: fix poweroff sequence Mauro Carvalho Chehab
2021-10-18 10:21 ` Lorenzo Pieralisi
2021-10-18 14:37 ` Mauro Carvalho Chehab
2021-10-19 9:40 ` Lorenzo Pieralisi [this message]
2021-10-21 10:09 ` Lorenzo Pieralisi
2021-10-18 7:07 ` [PATCH v13 10/10] PCI: kirin: Allow removing the driver Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211019094048.GA24481@lpieralisi \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=wangbinghui@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).