forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2024-10-22 8ac6c7a54ed1b98d142dce24b11c6de6a1e239a5 
 kernel/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
....@@ -41,45 +41,3 @@
4141 				 0x0 0 0 3 &mbigen_pcie 3 12
4242 				 0x0 0 0 4 &mbigen_pcie 4 13>;
4343 	};
44
-
45
-HiSilicon Hip06/Hip07 PCIe host bridge DT (almost-ECAM) description.
46
-
47
-Some BIOSes place the host controller in a mode where it is ECAM
48
-compliant for all devices other than the root complex. In such cases,
49
-the host controller should be described as below.
50
-
51
-The properties and their meanings are identical to those described in
52
-host-generic-pci.txt except as listed below.
53
-
54
-Properties of the host controller node that differ from
55
-host-generic-pci.txt:
56
-
57
-- compatible     : Must be "hisilicon,hip06-pcie-ecam", or
58
-		   "hisilicon,hip07-pcie-ecam"
59
-
60
-- reg            : Two entries: First the ECAM configuration space for any
61
-		   other bus underneath the root bus. Second, the base
62
-		   and size of the HiSilicon host bridge registers include
63
-		   the RC's own config space.
64
-
65
-Example:
66
-	pcie0: pcie@a0090000 {
67
-		compatible = "hisilicon,hip06-pcie-ecam";
68
-		reg = <0 0xb0000000 0 0x2000000>,  /*  ECAM configuration space */
69
-		      <0 0xa0090000 0 0x10000>; /* host bridge registers */
70
-		bus-range = <0  31>;
71
-		msi-map = <0x0000 &its_dsa 0x0000 0x2000>;
72
-		msi-map-mask = <0xffff>;
73
-		#address-cells = <3>;
74
-		#size-cells = <2>;
75
-		device_type = "pci";
76
-		dma-coherent;
77
-		ranges = <0x02000000 0 0xb2000000 0x0 0xb2000000 0 0x5ff0000
78
-			  0x01000000 0 0 0 0xb7ff0000 0 0x10000>;
79
-		#interrupt-cells = <1>;
80
-		interrupt-map-mask = <0xf800 0 0 7>;
81
-		interrupt-map = <0x0 0 0 1 &mbigen_pcie0 650 4
82
-				 0x0 0 0 2 &mbigen_pcie0 650 4
83
-				 0x0 0 0 3 &mbigen_pcie0 650 4
84
-				 0x0 0 0 4 &mbigen_pcie0 650 4>;
85
-	};