From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Hongxing Zhu <hongxing.zhu@nxp.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v8 5/8] PCI: imx6: Refine the regulator usage
Date: Fri, 4 Mar 2022 08:45:30 +0100 [thread overview]
Message-ID: <20220304074530.GA1164950@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <AS8PR04MB8676418087498F9CAF9849FD8C019@AS8PR04MB8676.eurprd04.prod.outlook.com>
On Mon, Feb 28, 2022 at 03:43:03AM +0000, Hongxing Zhu wrote:
> > 2. We are playing around with vpcie during regulator during suspend/resume,
> > why? We currently have issue with suspend/resume when a PCIe switch is
> > there, with the final effect of PCIe being not usable afterward. I fear like this is
> > related to our issue.
> >
> To my understands, the VPCIE is the abstract of the DIESABLE# signal.
> Refer to the Chapter 3.1.12.3 W_DISABLE# Signal of PCI Express M.2 SPEC.
> These signals are used to disable the Adapter's radio operation to meet public
> Safety regulations or when otherwise desired.
> It's reasonable to assert/de-assert W_DISABLE# signal during suspend/resume.
>
> > What about vpcie enable in probe, and vpcie disable in shutdown and that's
> > all?
> The W_DISABLE# Signal is used to control the radios on the Adapters.
> I think you can do that, if the radios are always on in your system.
According to the binding documentation (imx6q-pcie.yaml)
vpcie-supply:
description: Should specify the regulator in charge of PCIe port power.
The regulator will be enabled when initializing the PCIe host and
disabled either as part of the init process or when shutting down
the host (optional required).
This is how it's documented to be used, if this is used according to the
documentation (and this is happening) what you are already doing (not
changed in this patch, you are right) is not correct.
Abusing this for the W_DISABLE# disable is new to me and does not look
legit.
Francesco
next prev parent reply other threads:[~2022-03-04 7:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 3:44 [PATCH v8 0/8] PCI: imx6: refine codes and add compliance tests mode support Richard Zhu
2022-02-25 3:44 ` [PATCH v8 1/8] PCI: imx6: Encapsulate the clock enable into one standalone function Richard Zhu
2022-02-25 3:44 ` [PATCH v8 2/8] PCI: imx6: Add the error propagation from host_init Richard Zhu
2022-02-25 3:44 ` [PATCH v8 3/8] PCI: imx6: Move imx6_pcie_clk_disable() earlier Richard Zhu
2022-02-25 3:44 ` [PATCH v8 4/8] PCI: imx6: Disable iMX6QDL PCIe REF clock when disable PCIe clocks Richard Zhu
2022-02-25 3:44 ` [PATCH v8 5/8] PCI: imx6: Refine the regulator usage Richard Zhu
2022-02-25 9:43 ` Francesco Dolcini
2022-02-28 3:43 ` Hongxing Zhu
2022-03-04 7:45 ` Francesco Dolcini [this message]
2022-03-04 8:44 ` Hongxing Zhu
2022-02-25 3:44 ` [PATCH v8 6/8] PCI: dwc: Add dw_pcie_host_ops.host_exit() callback Richard Zhu
2022-04-01 20:43 ` Rob Herring
2022-04-02 3:03 ` Hongxing Zhu
2022-04-04 14:39 ` Rob Herring
2022-04-05 3:15 ` Hongxing Zhu
2022-02-25 3:44 ` [PATCH v8 7/8] PCI: imx6: Disable clocks and regulators after link is down Richard Zhu
2022-02-25 3:44 ` [PATCH v8 8/8] PCI: imx6: Add compliance tests mode support Richard Zhu
2022-04-01 20:26 ` Rob Herring
2022-04-02 3:03 ` Hongxing Zhu
2022-03-14 5:26 ` [PATCH v8 0/8] PCI: imx6: refine codes and add " Hongxing 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=20220304074530.GA1164950@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.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 \
/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