From: Florian Fainelli <f.fainelli@gmail.com>
To: devicetree@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com (maintainer:BROADCOM IPROC
ARM ARCHITECTURE),
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
IPROC ARM ARCHITECTURE), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v4 0/6] Convert iProc PCIe binding to YAML
Date: Fri, 10 Dec 2021 12:04:45 -0800 [thread overview]
Message-ID: <20211210200451.3849106-1-f.fainelli@gmail.com> (raw)
This patch series converts the iProc PCIe binding to YAML. Given there
is a majority of DTS changes, it would make sense for me to pull this
via the Broadcom ARM SoC git tree.
Thanks!
Changes in v4:
- Listed 'bus-ranges', '#address-cells', '#size-cells' and 'device_type'
as evaluated
- fixed first patch to drop reference to 'interrupt-controller'
Changes in v3:
- converted Cygnus PCIe PHY binding
- removed interrupt-controller from being a mandatory property
Changes in v2:
- document msi sub-node compatible string
Florian Fainelli (6):
ARM: dts: Cygnus: Fixed iProc PCIe controller properties
ARM: dts: Cygnus: Update PCIe PHY node unit name(s)
ARM: dts: HR2: Fixed iProc PCIe MSI sub-node
ARM: dts: NSP: Fixed iProc PCIe MSI sub-node
dt-bindings: phy: Convert Cygnus PCIe PHY to YAML
dt-bindings: pci: Convert iProc PCIe to YAML
.../bindings/pci/brcm,iproc-pcie.txt | 133 -------------
.../bindings/pci/brcm,iproc-pcie.yaml | 176 ++++++++++++++++++
.../bindings/phy/brcm,cygnus-pcie-phy.txt | 47 -----
.../bindings/phy/brcm,cygnus-pcie-phy.yaml | 76 ++++++++
arch/arm/boot/dts/bcm-cygnus.dtsi | 18 +-
arch/arm/boot/dts/bcm-hr2.dtsi | 4 +-
arch/arm/boot/dts/bcm-nsp.dtsi | 6 +-
7 files changed, 266 insertions(+), 194 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
create mode 100644 Documentation/devicetree/bindings/pci/brcm,iproc-pcie.yaml
delete mode 100644 Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
create mode 100644 Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.yaml
--
2.25.1
next reply other threads:[~2021-12-10 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 20:04 Florian Fainelli [this message]
2021-12-10 20:04 ` [PATCH v4 1/6] ARM: dts: Cygnus: Fixed iProc PCIe controller properties Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 2/6] ARM: dts: Cygnus: Update PCIe PHY node unit name(s) Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 3/6] ARM: dts: HR2: Fixed iProc PCIe MSI sub-node Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 4/6] ARM: dts: NSP: " Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 5/6] dt-bindings: phy: Convert Cygnus PCIe PHY to YAML Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 6/6] dt-bindings: pci: Convert iProc PCIe " Florian Fainelli
2021-12-13 18:44 ` [PATCH v4 0/6] Convert iProc PCIe binding " Florian Fainelli
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=20211210200451.3849106-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).