From: Richard Zhu <hongxing.zhu@nxp.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
l.stach@pengutronix.de, shawnguo@kernel.org,
lorenzo.pieralisi@arm.com, peng.fan@nxp.com, marex@denx.de,
marcel.ziswiler@toradex.com, tharvey@gateworks.com,
frank.li@nxp.com
Cc: hongxing.zhu@nxp.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com
Subject: [PATCH v7 1/5] dt-bindings: imx6q-pcie: Prepare to separate the Endpoint binding document
Date: Mon, 30 Jan 2023 11:32:15 +0800 [thread overview]
Message-ID: <1675049539-14976-2-git-send-email-hongxing.zhu@nxp.com> (raw)
In-Reply-To: <1675049539-14976-1-git-send-email-hongxing.zhu@nxp.com>
Prepare to create one separate DT-schema for i.MX PCIe Endpoint
controllers in another commit.
Remove the EP mode compatible, and update the description.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
.../devicetree/bindings/pci/fsl,imx6q-pcie.yaml | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
index f13f87fddb3d..2985d14b9ecc 100644
--- a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
+++ b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
@@ -13,6 +13,11 @@ maintainers:
description: |+
This PCIe host controller is based on the Synopsys DesignWare PCIe IP
and thus inherits all the common properties defined in snps,dw-pcie.yaml.
+ The controller instances are dual mode where in they can work either in
+ Root Port mode or Endpoint mode but one at a time.
+
+ See fsl,imx6q-pcie-ep.yaml for details on the Endpoint mode device tree
+ bindings.
properties:
compatible:
@@ -24,9 +29,6 @@ properties:
- fsl,imx8mq-pcie
- fsl,imx8mm-pcie
- fsl,imx8mp-pcie
- - fsl,imx8mm-pcie-ep
- - fsl,imx8mq-pcie-ep
- - fsl,imx8mp-pcie-ep
reg:
items:
@@ -178,6 +180,7 @@ required:
allOf:
- $ref: /schemas/pci/snps,dw-pcie.yaml#
+
- if:
properties:
compatible:
--
2.34.1
next prev parent reply other threads:[~2023-01-30 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 3:32 [PATCH DTS v7 0/5] Add i.MX PCIe EP mode support Richard Zhu
2023-01-30 3:32 ` Richard Zhu [this message]
2023-01-30 22:31 ` [PATCH v7 1/5] dt-bindings: imx6q-pcie: Prepare to separate the Endpoint binding document Rob Herring
2023-01-31 7:53 ` Hongxing Zhu
2023-01-30 3:32 ` [PATCH v7 2/5] dt-bindings: imx6q-pcie: Add schema for i.MX8M PCIe Endpoint modes Richard Zhu
2023-01-30 22:29 ` Rob Herring
2023-01-31 7:53 ` Hongxing Zhu
2023-01-30 3:32 ` [PATCH v7 3/5] arm64: dts: Add i.MX8MM PCIe EP support Richard Zhu
2023-01-30 3:32 ` [PATCH v7 4/5] arm64: dts: Add i.MX8MQ " Richard Zhu
2023-01-30 3:32 ` [PATCH v7 5/5] arm64: dts: Add i.MX8MP " 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=1675049539-14976-2-git-send-email-hongxing.zhu@nxp.com \
--to=hongxing.zhu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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).