.. | .. |
---|
2 | 2 | ======================== |
---|
3 | 3 | |
---|
4 | 4 | This defines device tree bindings for the Vitesse VSC73xx switch chips. |
---|
5 | | -The Vitesse company has been acquired by Microsemi and Microsemi in turn |
---|
6 | | -acquired by Microchip but retains this vendor branding. |
---|
| 5 | +The Vitesse company has been acquired by Microsemi and Microsemi has |
---|
| 6 | +been acquired Microchip but retains this vendor branding. |
---|
7 | 7 | |
---|
8 | 8 | The currently supported switch chips are: |
---|
9 | 9 | Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch |
---|
.. | .. |
---|
11 | 11 | Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch |
---|
12 | 12 | Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch |
---|
13 | 13 | |
---|
14 | | -The device tree node is an SPI device so it must reside inside a SPI bus |
---|
15 | | -device tree node, see spi/spi-bus.txt |
---|
| 14 | +This switch could have two different management interface. |
---|
| 15 | + |
---|
| 16 | +If SPI interface is used, the device tree node is an SPI device so it must |
---|
| 17 | +reside inside a SPI bus device tree node, see spi/spi-bus.txt |
---|
| 18 | + |
---|
| 19 | +When the chip is connected to a parallel memory bus and work in memory-mapped |
---|
| 20 | +I/O mode, a platform device is used to represent the vsc73xx. In this case it |
---|
| 21 | +must reside inside a platform bus device tree node. |
---|
16 | 22 | |
---|
17 | 23 | Required properties: |
---|
18 | 24 | |
---|
.. | .. |
---|
38 | 44 | |
---|
39 | 45 | Examples: |
---|
40 | 46 | |
---|
| 47 | +SPI: |
---|
41 | 48 | switch@0 { |
---|
42 | 49 | compatible = "vitesse,vsc7395"; |
---|
43 | 50 | reg = <0>; |
---|
.. | .. |
---|
79 | 86 | }; |
---|
80 | 87 | }; |
---|
81 | 88 | }; |
---|
| 89 | + |
---|
| 90 | +Platform: |
---|
| 91 | +switch@2,0 { |
---|
| 92 | + #address-cells = <1>; |
---|
| 93 | + #size-cells = <1>; |
---|
| 94 | + compatible = "vitesse,vsc7385"; |
---|
| 95 | + reg = <0x2 0x0 0x20000>; |
---|
| 96 | + reset-gpios = <&gpio0 12 GPIO_ACTIVE_LOW>; |
---|
| 97 | + |
---|
| 98 | + ports { |
---|
| 99 | + #address-cells = <1>; |
---|
| 100 | + #size-cells = <0>; |
---|
| 101 | + |
---|
| 102 | + port@0 { |
---|
| 103 | + reg = <0>; |
---|
| 104 | + label = "lan1"; |
---|
| 105 | + }; |
---|
| 106 | + port@1 { |
---|
| 107 | + reg = <1>; |
---|
| 108 | + label = "lan2"; |
---|
| 109 | + }; |
---|
| 110 | + port@2 { |
---|
| 111 | + reg = <2>; |
---|
| 112 | + label = "lan3"; |
---|
| 113 | + }; |
---|
| 114 | + port@3 { |
---|
| 115 | + reg = <3>; |
---|
| 116 | + label = "lan4"; |
---|
| 117 | + }; |
---|
| 118 | + vsc: port@6 { |
---|
| 119 | + reg = <6>; |
---|
| 120 | + label = "cpu"; |
---|
| 121 | + ethernet = <&enet0>; |
---|
| 122 | + phy-mode = "rgmii"; |
---|
| 123 | + fixed-link { |
---|
| 124 | + speed = <1000>; |
---|
| 125 | + full-duplex; |
---|
| 126 | + pause; |
---|
| 127 | + }; |
---|
| 128 | + }; |
---|
| 129 | + }; |
---|
| 130 | + |
---|
| 131 | +}; |
---|