From: Bjorn Helgaas <helgaas@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: l.stach@pengutronix.de, bhelgaas@google.com, robh+dt@kernel.org,
broonie@kernel.org, lorenzo.pieralisi@arm.com,
festevam@gmail.com, francesco.dolcini@toradex.com,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com
Subject: Re: [PATCH v13 10/15] PCI: imx6: Turn off regulator when system is in suspend mode
Date: Thu, 23 Jun 2022 17:19:44 -0500 [thread overview]
Message-ID: <20220623221944.GA1481121@bhelgaas> (raw)
In-Reply-To: <1655461874-16908-11-git-send-email-hongxing.zhu@nxp.com>
On Fri, Jun 17, 2022 at 06:31:09PM +0800, Richard Zhu wrote:
> The driver should undo any enables it did itself. The regulator disable
> shouldn't be basing decisions on regulator_is_enabled().
>
> Move the regulator_disable to the suspend function, turn off regulator when
> the system is in suspend mode.
>
> To keep the balance of the regulator usage counter, disable the regulator
> in shutdown.
>
> Link: https://lore.kernel.org/r/1655189942-12678-6-git-send-email-hongxing.z
> hu@nxp.com
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> drivers/pci/controller/dwc/pci-imx6.c | 19 +++++++------------
> 1 file changed, 7 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
> index 2b42c37f1617..f72eb609769b 100644
> --- a/drivers/pci/controller/dwc/pci-imx6.c
> +++ b/drivers/pci/controller/dwc/pci-imx6.c
> @@ -670,8 +670,6 @@ static void imx6_pcie_clk_disable(struct imx6_pcie *imx6_pcie)
>
> static void imx6_pcie_assert_core_reset(struct imx6_pcie *imx6_pcie)
> {
> - struct device *dev = imx6_pcie->pci->dev;
> -
> switch (imx6_pcie->drvdata->variant) {
> case IMX7D:
> case IMX8MQ:
> @@ -702,14 +700,6 @@ static void imx6_pcie_assert_core_reset(struct imx6_pcie *imx6_pcie)
> break;
> }
>
> - if (imx6_pcie->vpcie && regulator_is_enabled(imx6_pcie->vpcie) > 0) {
> - int ret = regulator_disable(imx6_pcie->vpcie);
> -
> - if (ret)
> - dev_err(dev, "failed to disable vpcie regulator: %d\n",
> - ret);
> - }
> -
> /* Some boards don't have PCIe reset GPIO. */
> if (gpio_is_valid(imx6_pcie->reset_gpio))
> gpio_set_value_cansleep(imx6_pcie->reset_gpio,
> @@ -722,7 +712,7 @@ static int imx6_pcie_deassert_core_reset(struct imx6_pcie *imx6_pcie)
> struct device *dev = pci->dev;
> int ret;
>
> - if (imx6_pcie->vpcie && !regulator_is_enabled(imx6_pcie->vpcie)) {
> + if (imx6_pcie->vpcie) {
> ret = regulator_enable(imx6_pcie->vpcie);
> if (ret) {
> dev_err(dev, "failed to enable vpcie regulator: %d\n",
> @@ -795,7 +785,7 @@ static int imx6_pcie_deassert_core_reset(struct imx6_pcie *imx6_pcie)
> return 0;
>
> err_clks:
> - if (imx6_pcie->vpcie && regulator_is_enabled(imx6_pcie->vpcie) > 0) {
> + if (imx6_pcie->vpcie) {
> ret = regulator_disable(imx6_pcie->vpcie);
> if (ret)
> dev_err(dev, "failed to disable vpcie regulator: %d\n",
> @@ -1022,6 +1012,9 @@ static int imx6_pcie_suspend_noirq(struct device *dev)
> break;
> }
>
> + if (imx6_pcie->vpcie)
> + regulator_disable(imx6_pcie->vpcie);
> +
> return 0;
> }
The suspend and resume methods should be symmetric, and they should
*look* symmetric.
imx6_pcie_suspend_noirq() disables the regulator, so
imx6_pcie_resume_noirq() should enable it.
imx6_pcie_suspend_noirq() calls imx6_pcie_clk_disable() to disable
several clocks. imx6_pcie_resume_noirq() should call
imx6_pcie_clk_enable() to enable them.
imx6_pcie_clk_enable() *is* called in the resume path, but it's buried
inside imx6_pcie_host_init() and imx6_pcie_deassert_core_reset().
That makes it hard to analyze.
We should be able to look at imx6_pcie_suspend_noirq() and
imx6_pcie_resume_noirq() and easily see that the resume path resumes
everything that was suspended in the suspend path.
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-23 22:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:30 [PATCH v13 0/15] PCI: imx6: refine codes and add the error propagation Richard Zhu
2022-06-17 10:31 ` [PATCH v13 01/15] PCI: imx6: Move imx6_pcie_grp_offset(), imx6_pcie_configure_type() earlier Richard Zhu
2022-06-17 10:31 ` [PATCH v13 02/15] PCI: imx6: Move PHY management functions together Richard Zhu
2022-06-17 10:31 ` [PATCH v13 03/15] PCI: imx6: Move imx6_pcie_enable_ref_clk() earlier Richard Zhu
2022-06-17 10:31 ` [PATCH v13 04/15] PCI: imx6: Move imx6_pcie_clk_disable() earlier Richard Zhu
2022-06-17 10:31 ` [PATCH v13 05/15] PCI: imx6: Factor out ref clock disable to match enable Richard Zhu
2022-06-17 10:31 ` [PATCH v13 06/15] PCI: imx6: Collect clock enables in imx6_pcie_clk_enable() Richard Zhu
2022-06-17 10:31 ` [PATCH v13 07/15] PCI: imx6: Propagate .host_init() errors to caller Richard Zhu
2022-06-17 10:31 ` [PATCH v13 08/15] PCI: imx6: Disable i.MX6QDL clock when disabling ref clocks Richard Zhu
2022-06-17 10:31 ` [PATCH v13 09/15] PCI: imx6: Call host init function directly in resume Richard Zhu
2022-06-17 10:31 ` [PATCH v13 10/15] PCI: imx6: Turn off regulator when system is in suspend mode Richard Zhu
2022-06-23 22:19 ` Bjorn Helgaas [this message]
2022-06-24 5:05 ` Hongxing Zhu
2022-06-27 19:51 ` Bjorn Helgaas
2022-06-28 3:48 ` Hongxing Zhu
2022-06-28 15:51 ` Bjorn Helgaas
2022-06-29 3:56 ` Hongxing Zhu
2022-06-17 10:31 ` [PATCH v13 11/15] PCI: imx6: Move regulator enable out of imx6_pcie_deassert_core_reset() Richard Zhu
2022-06-17 10:31 ` [PATCH v13 12/15] PCI: imx6: Mark the link down as non-fatal error Richard Zhu
2022-06-17 10:31 ` [PATCH v13 13/15] PCI: imx6: Reduce resume time by only starting link if it was up before suspend Richard Zhu
2022-06-17 10:31 ` [PATCH v13 14/15] PCI: imx6: Do not hide phy driver callbacks and refine the error handling Richard Zhu
2022-06-17 10:31 ` [PATCH v13 15/15] PCI: imx6: Disable clocks in reverse order of enable Richard Zhu
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=20220623221944.GA1481121@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
/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).