Document Qualcomm PCIe driver devicetree bindings.

Signed-off-by: Stanimir Varbanov <svarba...@mm-sol.com>
---
 .../devicetree/bindings/pci/qcom,pcie.txt          |  159 ++++++++++++++++++++
 1 files changed, 159 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pci/qcom,pcie.txt

diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt 
b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
new file mode 100644
index 0000000..2331144
--- /dev/null
+++ b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
@@ -0,0 +1,159 @@
+* Qualcomm PCI express root complex
+
+- compatible:
+       Usage: required
+       Value type: <stringlist>
+       Definition: Value shall include "qcom,pcie"
+
+- reg:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: Four register ranges as listed in the reg-names property
+
+- reg-names:
+       Usage: required
+       Value type: <stringlist>
+       Definition: Must include the following entries
+               - "parf"   Qualcomm specific registers
+               - "dbi"    Designware PCIe registers
+               - "elbi"   External local bus interface registers
+               - "config" PCIe configuration space
+
+- device_type:
+       Usage: required
+       Value type: <string>
+       Definition: Should be "pci". As specified in designware-pcie.txt
+
+- #address-cells:
+       Usage: required
+       Value type: <u32>
+       Definition: Should be set to 3. As specified in designware-pcie.txt
+
+- #size-cells:
+       Usage: required
+       Value type: <u32>
+       Definition: Should be set 2. As specified in designware-pcie.txt
+
+- ranges:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: As specified in designware-pcie.txt
+
+- interrupts:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: MSI interrupt
+
+- interrupt-names:
+       Usage: required
+       Value type: <stringlist>
+       Definition: Should contain "msi"
+
+- #interrupt-cells:
+       Usage: required
+       Value type: <u32>
+       Definition: Should be 1. As specified in designware-pcie.txt
+
+- interrupt-map-mask:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: As specified in designware-pcie.txt
+
+- interrupt-map:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: As specified in designware-pcie.txt
+
+- clocks:
+       Usage: required
+       Value type: <prop-encoded-array>
+       Definition: Four clocks as listed in clock-names property
+
+- clock-names:
+       Usage: required
+       Value type: <stringlist>
+       Definition: Must include the following entries
+               - "aux"        auxiliary (AUX) clock
+               - "iface"      configuration AHB clock
+               - "bus_master" master AXI clock
+               - "bus_slave"  slave AXI clock
+
+- resets:
+       Usage: required
+       Value type: <phandle>
+       Definition: List of phandle and reset specifier pairs as listed
+                   in reset-names property
+
+- reset-names:
+       Usage: required
+       Value type: <stringlist>
+       Definition: Should contain the following entries
+               - "core" core reset
+
+- <name>-supply:
+       Usage: required
+       Value type: <phandle>
+       Definition: List of phandles to the supply regulators
+               - "vdd_pc" collapsing and restoring power to peripheral
+- gpios:
+       Usage: optional
+       Value type: <phandle>
+       Definition: List of phandle and gpio specifier. Should include
+                   - "perst"  PCIe endpoint reset signal line
+                   - "pewake" PCIe endpoint wake signal line
+
+- pinctrl-0:
+       Usage: required
+       Value type: <phandle>
+       Definition: List of phandles pointing at a pin(s) configuration
+
+- pinctrl-names
+       Usage: required
+       Value type: <stringlist>
+       Definition: List of names of pinctrl-0 state
+
+* Example
+
+       pcie0@fc520000 {
+               compatible = "qcom,pcie";
+               reg = <0xfc520000 0x2000>,
+                     <0xff000000 0x1000>,
+                     <0xff001000 0x1000>,
+                     <0xff002000 0x2000>;
+               reg-names = "parf", "dbi", "elbi", "config";
+               device_type = "pci";
+               linux,pci-domain = <0>;
+               bus-range = <0x00 0xff>;
+               num-lanes = <1>;
+               #address-cells = <3>;
+               #size-cells = <2>;
+               ranges = <0x81000000 0 0          0xff200000 0 0x00100000   /* 
I/O */
+                         0x82000000 0 0x00300000 0xff300000 0 0x00d00000>; /* 
Memory */
+               interrupts = <0 243 0>;
+               interrupt-names = "msi";
+               #interrupt-cells = <1>;
+               interrupt-map-mask = <0 0 0 0x7>;
+               interrupt-map = <0 0 0 1 &intc 0 244 IRQ_TYPE_LEVEL_HIGH>, /* 
int_a */
+                               <0 0 0 2 &intc 0 245 IRQ_TYPE_LEVEL_HIGH>, /* 
int_b */
+                               <0 0 0 3 &intc 0 247 IRQ_TYPE_LEVEL_HIGH>, /* 
int_c */
+                               <0 0 0 4 &intc 0 248 IRQ_TYPE_LEVEL_HIGH>; /* 
int_d */
+
+               clocks = <&gcc GCC_PCIE_0_AUX_CLK>,
+                        <&gcc GCC_PCIE_0_CFG_AHB_CLK>,
+                        <&gcc GCC_PCIE_0_MSTR_AXI_CLK>,
+                        <&gcc GCC_PCIE_0_SLV_AXI_CLK>;
+               clock-names = "aux", "iface", "master_bus", "slave_bus";
+
+               resets = <&gcc GCC_PCIE_0_BCR>;
+               reset-names = "core";
+
+               vdd_pc-supply = <&gdsc_pcie0>;
+
+               phys = <&pciephy0>;
+               phy-names = "pciephy";
+
+               gpios = <&tlmm 70 0>;   /* perst */
+
+               pinctrl-0 = <&pcie0_pins_default>;
+               pinctrl-names = "default";
+       };
-- 
1.7.0.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to