/Documentation/devicetree/bindings/net/ |
D | brcm,unimac-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/brcm,unimac-mdio.yaml# 7 title: Broadcom UniMAC MDIO bus controller 15 - $ref: mdio.yaml# 20 - brcm,genet-mdio-v1 21 - brcm,genet-mdio-v2 22 - brcm,genet-mdio-v3 23 - brcm,genet-mdio-v4 24 - brcm,genet-mdio-v5 25 - brcm,asp-v2.0-mdio 26 - brcm,asp-v2.1-mdio [all …]
|
D | hisilicon-hns-mdio.txt | 1 Hisilicon MDIO bus controller 5 "hisilicon,hns-mdio" 6 "hisilicon,mdio" 7 "hisilicon,hns-mdio" is recommended to be used for hip05 and later SOCs, 8 while "hisilicon,mdio" is optional for backwards compatibility only on 10 - reg: The base address of the MDIO bus controller register bank. 12 - #size-cells: Must be <0>. MDIO addresses have no size component. 14 Typically an MDIO bus might have several children. 17 mdio@803c0000 { 20 compatible = "hisilicon,hns-mdio","hisilicon,mdio";
|
D | cavium-mdio.txt | 1 * System Management Interface (SMI) / MDIO 6 "cavium,octeon-3860-mdio": Compatibility with all cn3XXX, cn5XXX 9 "cavium,thunder-8890-mdio": Compatibility with all cn8XXX SOCs. 11 - reg: The base address of the MDIO bus controller register bank. 15 - #size-cells: Must be <0>. MDIO addresses have no size component. 17 Typically an MDIO bus might have several children. 20 mdio@1180000001800 { 21 compatible = "cavium,octeon-3860-mdio"; 33 * System Management Interface (SMI) / MDIO Nexus 35 Several mdio buses may be gathered as children of a single PCI [all …]
|
D | qcom,ipq4019-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/qcom,ipq4019-mdio.yaml# 7 title: Qualcomm IPQ40xx MDIO Controller 16 - qcom,ipq4019-mdio 17 - qcom,ipq5018-mdio 21 - qcom,ipq6018-mdio 22 - qcom,ipq8074-mdio 23 - const: qcom,ipq4019-mdio 35 the first Address and length of the register set for the MDIO controller. 41 - description: MDIO clock source frequency fixed to 100MHZ 54 - $ref: mdio.yaml# [all …]
|
D | mdio-mux-multiplexer.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-mux-multiplexer.yaml# 7 title: Properties for an MDIO bus multiplexer consumer device 13 This is a special case of MDIO mux when MDIO mux is defined as a consumer 19 - $ref: /schemas/net/mdio-mux.yaml# 23 const: mdio-mux-multiplexer 43 mdio-mux-1 { // Mux consumer 44 compatible = "mdio-mux-multiplexer"; 46 mdio-parent-bus = <&emdio1>; 50 mdio@0 { 56 mdio@8 { [all …]
|
D | amlogic,gxl-mdio-mux.yaml | 4 $id: http://devicetree.org/schemas/net/amlogic,gxl-mdio-mux.yaml# 7 title: Amlogic GXL MDIO bus multiplexer 13 This is a special case of a MDIO bus multiplexer. It allows to choose between 14 the internal mdio bus leading to the embedded 10/100 PHY or the external 15 MDIO bus on the Amlogic GXL SoC family. 18 - $ref: mdio-mux.yaml# 22 const: amlogic,gxl-mdio-mux 44 eth_phy_mux: mdio@558 { 45 compatible = "amlogic,gxl-mdio-mux"; 51 mdio-parent-bus = <&mdio0>; [all …]
|
D | allwinner,sun8i-a83t-emac.yaml | 127 mdio-mux: 133 const: allwinner,sun8i-h3-mdio-mux 135 mdio-parent-bus: 138 Phandle to EMAC MDIO. 146 mdio@1: 147 $ref: mdio.yaml# 149 description: Internal MDIO Bus 153 const: allwinner,sun8i-h3-mdio-internal 176 mdio@2: 177 $ref: mdio.yaml# [all …]
|
D | apm-xgene-mdio.txt | 1 APM X-Gene SoC MDIO node 3 MDIO node is defined to describe on-chip MDIO controller. 6 - compatible: Must be "apm,xgene-mdio-rgmii" or "apm,xgene-mdio-xfi" 12 For the phys on the mdio bus, there must be a node with the following fields: 18 mdio: mdio@17020000 { 19 compatible = "apm,xgene-mdio-rgmii"; 27 &mdio {
|
D | brcm,mdio-mux-iproc.yaml | 4 $id: http://devicetree.org/schemas/net/brcm,mdio-mux-iproc.yaml# 7 title: MDIO bus multiplexer found in Broadcom iProc based SoCs. 13 This MDIO bus multiplexer defines buses that could be internal as well as 14 external to SoCs and could accept MDIO transaction compatible to C-22 or 16 properties as well to generate desired MDIO transaction on appropriate bus. 19 - $ref: /schemas/net/mdio-mux.yaml# 23 const: brcm,mdio-mux-iproc 30 description: core clock driving the MDIO block 41 mdio_mux_iproc: mdio-mux@66020000 { 42 compatible = "brcm,mdio-mux-iproc"; [all …]
|
D | mdio-mux-mmioreg.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-mux-mmioreg.yaml# 7 title: Properties for an MDIO bus multiplexer controlled by a memory-mapped device 13 This is a special case of a MDIO bus multiplexer. A memory-mapped device, 14 like an FPGA, is used to control which child bus is connected. The mdio-mux 19 - $ref: /schemas/net/mdio-mux.yaml# 24 - const: mdio-mux-mmioreg 25 - const: mdio-mux 37 child mdio-mux node must be constrained by this mask. 48 mdio-mux@9 { 49 compatible = "mdio-mux-mmioreg", "mdio-mux"; [all …]
|
D | mdio-gpio.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-gpio.yaml# 7 title: MDIO on GPIOs 15 - $ref: mdio.yaml# 20 - virtual,mdio-gpio 21 - microchip,mdio-smi0 33 - description: MDIO 36 # Note: Each gpio-mdio bus should have an alias correctly numbered in "aliases" 44 mdio-gpio0 = &mdio0; 47 mdio0: mdio { 48 compatible = "virtual,mdio-gpio";
|
D | brcm,bcm6368-mdio-mux.yaml | 4 $id: http://devicetree.org/schemas/net/brcm,bcm6368-mdio-mux.yaml# 7 title: Broadcom BCM6368 MDIO bus multiplexer 13 This MDIO bus multiplexer defines buses that could be internal as well as 15 properties as well to generate desired MDIO transaction on appropriate bus. 18 - $ref: mdio-mux.yaml# 22 const: brcm,bcm6368-mdio-mux 35 mdio0: mdio@10e000b0 { 38 compatible = "brcm,bcm6368-mdio-mux"; 41 mdio_int: mdio@0 { 47 mdio_ext: mdio@1 {
|
D | amlogic,g12a-mdio-mux.yaml | 4 $id: http://devicetree.org/schemas/net/amlogic,g12a-mdio-mux.yaml# 7 title: MDIO bus multiplexer/glue of Amlogic G12a SoC family 10 This is a special case of a MDIO bus multiplexer. It allows to choose between 11 the internal mdio bus leading to the embedded 10/100 PHY or the external 12 MDIO bus. 18 - $ref: mdio-mux.yaml# 22 const: amlogic,g12a-mdio-mux 51 mdio-multiplexer@4c000 { 52 compatible = "amlogic,g12a-mdio-mux"; 56 mdio-parent-bus = <&mdio0>; [all …]
|
D | fsl-enetc.txt | 14 1. The ENETC external port is connected to a MDIO configurable phy 16 1.1. Using the local ENETC Port MDIO interface 18 In this case, the ENETC node should include a "mdio" sub-node 26 - phy-handle : Phandle to a PHY on the MDIO bus. 31 - mdio : "mdio" node, defined in mdio.txt. 43 mdio { 52 1.2. Using the central MDIO PCIe endpoint device 54 In this case, the mdio node should be defined as another PCIe 62 - compatible : Should be "fsl,enetc-mdio". 64 The remaining required mdio bus properties are standard, their bindings [all …]
|
D | aspeed,ast2600-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/aspeed,ast2600-mdio.yaml# 7 title: ASPEED AST2600 MDIO Controller 13 The ASPEED AST2600 MDIO controller is the third iteration of ASPEED's MDIO 18 - $ref: mdio.yaml# 22 const: aspeed,ast2600-mdio 26 description: The register range of the MDIO controller instance 42 mdio0: mdio@1e650000 { 43 compatible = "aspeed,ast2600-mdio";
|
D | mdio-mux.yaml | 4 $id: http://devicetree.org/schemas/net/mdio-mux.yaml# 7 title: Common MDIO bus multiplexer/switch properties. 13 An MDIO bus multiplexer/switch will have several child busses that are 14 numbered uniquely in a device dependent manner. The nodes for an MDIO 18 mdio-parent-bus: 21 The phandle of the MDIO bus that this multiplexer's master-side port is 31 '^mdio@[0-9a-f]+$': 32 $ref: mdio.yaml#
|
D | mdio.yaml | 4 $id: http://devicetree.org/schemas/net/mdio.yaml# 7 title: MDIO Bus Common Properties 15 These are generic properties that can apply to any MDIO bus. Any 16 MDIO bus must have a list of child nodes, one per device on the 22 pattern: "^mdio(@.*)?" 34 lines of all devices on that MDIO bus. 38 RESET pulse width in microseconds. It applies to all MDIO devices 44 Delay after reset deassert in microseconds. It applies to all MDIO 51 Desired MDIO bus clock frequency in Hz. Values greater than IEEE 802.3 75 If set, indicates the MDIO device does not correctly release [all …]
|
D | ti,davinci-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/ti,davinci-mdio.yaml# 7 title: TI SoC Davinci/Keystone2 MDIO Controller 13 TI SoC Davinci/Keystone2 MDIO Controller 16 - $ref: mdio.yaml# 26 - const: ti,cpsw-mdio 29 - const: ti,am4372-mdio 30 - const: ti,cpsw-mdio 39 description: MDIO Bus frequency 74 davinci_mdio: mdio@4a101000 {
|
D | fsl-tsec-phy.txt | 1 * MDIO IO device 3 The MDIO is a bus to which the PHY devices are connected. For each 15 mdio. Currently supported strings/devices are: 17 - "fsl,gianfar-mdio" 19 - "fsl,etsec2-mdio" 20 - "fsl,ucc-mdio" 21 - "fsl,fman-mdio" 22 When device_type is "mdio", the following strings are also considered: 28 mdio@24520 { 30 compatible = "fsl,gianfar-mdio"; [all …]
|
D | allwinner,sun4i-a10-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/allwinner,sun4i-a10-mdio.yaml# 7 title: Allwinner A10 MDIO Controller 14 - $ref: mdio.yaml# 24 - allwinner,sun4i-a10-mdio 27 - allwinner,sun4i-mdio 40 const: allwinner,sun4i-a10-mdio 56 mdio@1c0b080 { 57 compatible = "allwinner,sun4i-a10-mdio";
|
D | brcm,iproc-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/brcm,iproc-mdio.yaml# 7 title: Broadcom iProc MDIO bus controller 13 - $ref: mdio.yaml# 17 const: brcm,iproc-mdio 29 mdio@18002000 { 30 compatible = "brcm,iproc-mdio";
|
D | qcom,ipq8064-mdio.yaml | 4 $id: http://devicetree.org/schemas/net/qcom,ipq8064-mdio.yaml# 7 title: Qualcomm ipq806x MDIO bus controller 13 The ipq806x soc have a MDIO dedicated controller that is 17 - $ref: mdio.yaml# 21 const: qcom,ipq8064-mdio 42 mdio0: mdio@37000000 { 46 compatible = "qcom,ipq8064-mdio";
|
/Documentation/devicetree/bindings/net/dsa/ |
D | realtek.yaml | 18 MDIO or SPI. 21 bit-banged GPIO that while it reuses the MDIO lines MCK and MDIO does 22 not use the MDIO protocol. This binding defines how to specify the 26 The MDIO-connected switches use MDIO protocol to access their registers. 27 The realtek-mdio driver is an MDIO driver and it must be inserted inside 28 an MDIO node. 54 mdio-gpios: 55 description: GPIO line for the MDIO data line. 98 mdio: 99 $ref: /schemas/net/mdio.yaml# [all …]
|
D | marvell.txt | 10 Marvell Switches are MDIO devices. The following properties should be 11 placed as a child node of an mdio device. 17 which is at a different MDIO base address in different switch families. 44 - mdio : Container of PHY and devices on the switches MDIO 46 - mdio? : Container of PHYs and devices on the external MDIO 48 "marvell,mv88e6xxx-mdio-external" 52 mdio { 65 mdio { 77 mdio { 90 mdio { [all …]
|
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
D | network.txt | 23 * MDIO 26 fsl,pq1-fec-mdio (reg is same as first resource of FEC device) 27 fsl,cpm2-mdio-bitbang (reg is port C registers) 29 Properties for fsl,cpm2-mdio-bitbang: 30 fsl,mdio-pin : pin of port C controlling mdio data 31 fsl,mdc-pin : pin of port C controlling mdio clock 34 mdio@10d40 { 35 compatible = "fsl,mpc8272ads-mdio-bitbang", 36 "fsl,mpc8272-mdio-bitbang", 37 "fsl,cpm2-mdio-bitbang"; [all …]
|