From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: bhelgaas@google.com, robh+dt@kernel.org,
tsbogend@alpha.franken.de, lorenzo.pieralisi@arm.com,
p.zabel@pengutronix.de, jiaxun.yang@flygoat.com,
paulburton@kernel.org, info@metux.net, allison@lohutok.net,
kstewart@linuxfoundation.org, tglx@linutronix.de,
jonas.gorski@gmail.com, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH 2/3] dt-bindings: Document BCM6328 PCIe Host Controller
Date: Wed, 17 Jun 2020 12:25:55 +0200 [thread overview]
Message-ID: <20200617102556.3792821-3-noltari@gmail.com> (raw)
In-Reply-To: <20200617102556.3792821-1-noltari@gmail.com>
BCM6328 PCIe host controller is found on BCM6328, BCM6362 and BCM63268 SoCs.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
---
.../bindings/pci/brcm,bcm6328-pcie.yaml | 109 ++++++++++++++++++
1 file changed, 109 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.yaml
diff --git a/Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.yaml b/Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.yaml
new file mode 100644
index 000000000000..d2bd4933a5fa
--- /dev/null
+++ b/Documentation/devicetree/bindings/pci/brcm,bcm6328-pcie.yaml
@@ -0,0 +1,109 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/pci/brcm,bcm6328-pcie.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: BCM6328 PCIe Host Controller Device Tree Bindings
+
+maintainers:
+ - Álvaro Fernández Rojas <noltari@gmail.com>
+
+allOf:
+ - $ref: /schemas/pci/pci-bus.yaml#
+
+properties:
+ compatible:
+ enum:
+ - brcm,bcm6328-pcie
+ - brcm,bcm6362-pcie
+ - brcm,bcm63268-pcie
+
+ clocks:
+ maxItems: 1
+
+ clock-names:
+ items:
+ - const: pcie
+
+ "#interrupt-cells":
+ const: 1
+
+ interrupt-map-mask:
+ maxItems: 1
+
+ interrupt-map:
+ maxItems: 1
+
+ power-domains:
+ maxItems: 1
+
+ ranges:
+ maxItems: 1
+
+ reg:
+ maxItems: 1
+
+ resets:
+ maxItems: 4
+
+ reset-names:
+ items:
+ - const: pcie
+ - const: pcie-core
+ - const: pcie-ext
+ - const: pcie-hard
+
+required:
+ - brcm,serdes
+ - clocks
+ - clock-names
+ - "#interrupt-cells"
+ - interrupt-map-mask
+ - interrupt-map
+ - ranges
+ - reg
+ - resets
+ - reset-names
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ serdes_cntl: syscon@10001800 {
+ compatible = "syscon";
+ reg = <0x10001800 0x4>;
+ native-endian;
+ };
+
+ pcie: pcie@10e40000 {
+ compatible = "brcm,bcm6328-pcie";
+ reg = <0x10e40000 0x10000>;
+ #address-cells = <3>;
+ #size-cells = <2>;
+
+ device_type = "pci";
+ bus-range = <0x00 0x01>;
+ ranges = <0x2000000 0 0x10f00000 0x10f00000 0 0x100000>;
+ linux,pci-probe-only = <1>;
+
+ #interrupt-cells = <1>;
+ interrupt-map-mask = <0 0 0 0>;
+ interrupt-map = <0 0 0 0 &periph_intc BCM6328_IRQ_PCIE_RC 0>;
+
+ clocks = <&periph_clk BCM6328_CLK_PCIE>;
+ clock-names = "pcie";
+
+ resets = <&periph_rst BCM6328_RST_PCIE>,
+ <&periph_rst BCM6328_RST_PCIE_EXT>,
+ <&periph_rst BCM6328_RST_PCIE_CORE>,
+ <&periph_rst BCM6328_RST_PCIE_HARD>;
+ reset-names = "pcie",
+ "pcie-ext",
+ "pcie-core",
+ "pcie-hard";
+
+ power-domains = <&periph_pwr BCM6328_POWER_DOMAIN_PCIE>;
+
+ brcm,serdes = <&serdes_cntl>;
+ };
--
2.27.0
next prev parent reply other threads:[~2020-06-17 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 10:25 [PATCH 0/3] mips: bmips: add BCM6328 PCIe support Álvaro Fernández Rojas
2020-06-17 10:25 ` [PATCH 1/3] mips: bmips: add PCI support Álvaro Fernández Rojas
2020-06-17 11:09 ` Thomas Bogendoerfer
2020-06-17 10:25 ` Álvaro Fernández Rojas [this message]
2020-06-17 17:07 ` [PATCH 2/3] dt-bindings: Document BCM6328 PCIe Host Controller Rob Herring
2020-06-17 21:50 ` Florian Fainelli
2020-06-17 10:25 ` [PATCH 3/3] pci: add BCM6328 PCIe controller support Álvaro Fernández Rojas
2020-06-17 15:50 ` Bjorn Helgaas
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=20200617102556.3792821-3-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=allison@lohutok.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=info@metux.net \
--cc=jiaxun.yang@flygoat.com \
--cc=jonas.gorski@gmail.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/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).