From: Frank Li <Frank.Li@nxp.com>
To: conor@kernel.org
Cc: Frank.Li@nxp.com, bhelgaas@google.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, helgaas@kernel.org,
imx@lists.linux.dev, krzysztof.kozlowski+dt@linaro.org,
kw@linux.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, lpieralisi@kernel.org,
robh@kernel.org
Subject: [PATCH v6 0/3] dt-bindings: pci: layerscape-pci: Convert to yaml format
Date: Fri, 1 Mar 2024 11:27:38 -0500 [thread overview]
Message-ID: <20240301162741.765524-1-Frank.Li@nxp.com> (raw)
Change from
Change from v5 to v6
- Rob require every commit pass dtb_check, so first commit included
nesssary change. and list change at commit message.
- Reduce to 3 patches.
Change from v4 to v5
- split 5 patch.
- create one base patch, which the same as original txt.
- two patch fix for RC.
- two patch fix for EP.
Change from v3 to v4
- remove ep label
- remove status="disabled"
- remove deprecated property
- fixed irq max-numbers
- because dts still use "reg" instead "dbi", to avoid dtb check warning,
not referernece to snps,dwc-pcie yet.
Change from v2 to v3
- update commit message, show change compare txt file
- add failback compatible fsl,ls-pcie-ep.
- add commit message about 'addr_space' and 'config'.
Change from v1 to v2
- remove '|-'
- dma-coherent: true
- add interrupts and interrupt-names at before Allof
- remove ref to snps,pcie*.yaml, some reg-names are not aligned with in
drivers
- Add an example for pcie-ep
Frank Li (3):
dt-bindings: pci: layerscape-pci: Convert to yaml format
dt-bindings: pci: layerscape-pci: Add snps,dw-pcie.yaml reference
dt-bindings: pci: layerscape-pci-ep: Add snps,dw-pcie-ep.yaml
reference
.../bindings/pci/fsl,layerscape-pcie-ep.yaml | 91 +++++++++
.../bindings/pci/fsl,layerscape-pcie.yaml | 173 ++++++++++++++++++
.../bindings/pci/layerscape-pci.txt | 79 --------
3 files changed, 264 insertions(+), 79 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pci/fsl,layerscape-pcie-ep.yaml
create mode 100644 Documentation/devicetree/bindings/pci/fsl,layerscape-pcie.yaml
delete mode 100644 Documentation/devicetree/bindings/pci/layerscape-pci.txt
--
2.34.1
next reply other threads:[~2024-03-01 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 16:27 Frank Li [this message]
2024-03-01 16:27 ` [PATCH v6 1/3] dt-bindings: pci: layerscape-pci: Convert to yaml format Frank Li
2024-03-04 17:32 ` Rob Herring
2024-03-04 17:47 ` Frank Li
2024-03-05 14:46 ` Rob Herring
2024-03-05 15:25 ` Frank Li
2024-03-11 3:08 ` Frank Li
2024-03-01 16:27 ` [PATCH v6 2/3] dt-bindings: pci: layerscape-pci: Add snps,dw-pcie.yaml reference Frank Li
2024-03-04 18:17 ` Rob Herring
2024-03-04 19:10 ` Frank Li
2024-03-01 16:27 ` [PATCH v6 3/3] dt-bindings: pci: layerscape-pci-ep: Add snps,dw-pcie-ep.yaml reference Frank Li
2024-03-04 18:20 ` Rob Herring
2024-03-04 19:08 ` Frank Li
2024-03-05 14:37 ` Rob Herring
2024-03-05 15:30 ` Frank Li
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=20240301162741.765524-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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).