From: Richard Zhu <hongxing.zhu@nxp.com>
To: l.stach@pengutronix.de, andrew.smirnov@gmail.com,
shawnguo@kernel.org, kw@linux.com, bhelgaas@google.com,
stefan@agner.ch, lorenzo.pieralisi@arm.com
Cc: linux-pci@vger.kernel.org, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: [PATCH v3 0/3] add one regulator used to power up pcie phy
Date: Thu, 25 Mar 2021 16:44:39 +0800 [thread overview]
Message-ID: <1616661882-26487-1-git-send-email-hongxing.zhu@nxp.com> (raw)
Changes:
v2 -> v3:
Refine the DT binding descriptions, and the condition adjustment in the codes.
v1 -> v2:
Don't use the boolean property to specify the different power supply of PCIe PHY.
Use one regulator as a supply to the PCIe controller node, and the regulator APIs
to get the voltage of it.
Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt | 3 +++
arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 1 +
drivers/pci/controller/dwc/pci-imx6.c | 20 ++++++++++++++++++++
3 files changed, 24 insertions(+)
[PATCH v3 1/3] dt-bindings: imx6q-pcie: add one regulator used to
[PATCH v3 2/3] arm64: dts: imx8mq-evk: add one regulator used to
[PATCH v3 3/3] PCI: imx: clear vreg bypass when pcie vph voltage is
next reply other threads:[~2021-03-25 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 8:44 Richard Zhu [this message]
2021-03-25 8:44 ` [PATCH v3 1/3] dt-bindings: imx6q-pcie: add one regulator used to power up pcie phy Richard Zhu
2021-03-26 9:37 ` Lucas Stach
2021-03-25 8:44 ` [PATCH v3 2/3] arm64: dts: imx8mq-evk: " Richard Zhu
2021-03-26 9:40 ` Lucas Stach
2021-03-25 8:44 ` [PATCH v3 3/3] PCI: imx: clear vreg bypass when pcie vph voltage is 3v3 Richard Zhu
2021-03-26 7:45 ` Krzysztof Wilczyński
2021-03-26 9:41 ` Lucas Stach
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=1616661882-26487-1-git-send-email-hongxing.zhu@nxp.com \
--to=hongxing.zhu@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=bhelgaas@google.com \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--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=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).