| /freebsd/sys/contrib/device-tree/Bindings/net/ | 
| H A D | fsl,fman-mdio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)3 ---
 4 $id: http://devicetree.org/schemas/net/fsl,fman-mdio.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Freescale Frame Manager MDIO Device
 10   - Frank Li <Frank.Li@nxp.com>
 12 description: FMan MDIO Node.
 13   The MDIO is a bus to which the PHY devices are connected.
 18       - fsl,fman-mdio
 19       - fsl,fman-xmdio
 [all …]
 
 | 
| H A D | brcm,unimac-mdio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause3 ---
 4 $id: http://devicetree.org/schemas/net/brcm,unimac-mdio.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Broadcom UniMAC MDIO bus controller
 10   - Doug Berger <opendmb@gmail.com>
 11   - Florian Fainelli <f.fainelli@gmail.com>
 12   - Rafał Miłecki <rafal@milecki.pl>
 15   - $ref: mdio.yaml#
 20       - brcm,genet-mdio-v1
 [all …]
 
 | 
| H A D | allwinner,sun8i-a83t-emac.yaml | 1 # SPDX-License-Identifier: GPL-2.03 ---
 4 $id: http://devicetree.org/schemas/net/allwinner,sun8i-a83t-emac.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 10   - Che
 [all...]
 | 
| H A D | mdio-mux-multiplexer.txt | 1 Properties for an MDIO bus multiplexer consumer device3 This is a special case of MDIO mux  when MDIO mux is defined as a consumer
 7 Required properties in addition to the MDIO Bus multiplexer properties:
 9 - compatible : should be "mmio-mux-multiplexer"
 10 - mux-controls : mux controller node to use for operating the mux
 11 - mdio-parent-bus : phandle to the parent MDIO bus.
 13 each child node of mdio bus multiplexer consumer device represent a mdio
 17 Documentation/devicetree/bindings/mux/mux-controller.txt
 18 and Documentation/devicetree/bindings/net/mdio-mux.txt
 25 		compatible = "fsl,lx2160aqds-fpga", "fsl,fpga-qixis-i2c",
 [all …]
 
 | 
| H A D | brcm,unimac-mdio.txt | 1 * Broadcom UniMAC MDIO bus controller4 - compatible: should one from "brcm,genet-mdio-v1", "brcm,genet-mdio-v2",
 5   "brcm,genet-mdio-v3", "brcm,genet-mdio-v4", "brcm,genet-mdio-v5" or
 6   "brcm,unimac-mdio"
 7 - reg: address and length of the register set for the device, first one is the
 9   larger than 16-bits MDIO transactions
 10 - reg-names: name(s) of the register must be "mdio" and optional "mdio_indir_rw"
 11 - #size-cells: must be 1
 12 - #address-cells: must be 0
 15 - interrupts: must be one if the interrupt is shared with the Ethernet MAC or
 [all …]
 
 | 
| H A D | cavium-mdio.txt | 1 * System Management Interface (SMI) / MDIO4 - compatible: One of:
 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.
 13 - #address-cells: Must be <1>.
 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";
 [all …]
 
 | 
| H A D | mdio-mux-multiplexer.yaml | 1 # SPDX-License-Identifier: GPL-2.03 ---
 4 $id: http://devicetree.org/schemas/net/mdio-mux-multiplexer.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Properties for an MDIO bus multiplexer consumer device
 10   - Andrew Lunn <andrew@lunn.ch>
 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
 25   mux-controls:
 [all …]
 
 | 
| H A D | qcom,ipq4019-mdio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause3 ---
 4 $id: http://devicetree.org/schemas/net/qcom,ipq4019-mdio.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Qualcomm IPQ40xx MDIO Controller
 10   - Robert Marko <robert.marko@sartura.hr>
 15       - enum:
 16           - qcom,ipq4019-mdio
 17           - qcom,ipq5018-mdio
 19       - items:
 [all …]
 
 | 
| H A D | brcm,mdio-mux-iproc.txt | 1 Properties for an MDIO bus multiplexer found in Broadcom iProc based SoCs.3 This MDIO bus multiplexer defines buses that could be internal as well as
 4 external to SoCs and could accept MDIO transaction compatible to C-22 or
 5 C-45 Clause. When child bus is selected, one needs to select these two
 6 properties as well to generate desired MDIO transaction on appropriate bus.
 10 MDIO multiplexer node:
 11 - compatible: brcm,mdio-mux-iproc.
 13 Every non-ethernet PHY requires a compatible so that it could be probed based
 17 - clocks: phandle of the core clock which drives the mdio block.
 20 at- Documentation/devicetree/bindings/net/mdio-mux.yaml
 [all …]
 
 | 
| H A D | fsl-enetc.txt | 9 - reg		: Specifies PCIe Device Number and Function12 - compatible	: Should be "fsl,enetc".
 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
 19 that in turn should contain the "ethernet-phy" node describing the
 26 - phy-handle		: Phandle to a PHY on the MDIO bus.
 29 - phy-connection-type	: Defined in ethernet.txt.
 31 - mdio			: "mdio" node, defined in mdio.txt.
 33 - ethernet-phy		: "ethernet-phy" node, defined in phy.txt.
 [all …]
 
 | 
| H A D | brcm,bcmgenet.txt | 4 - compatible: should contain one of "brcm,genet-v1", "brcm,genet-v2",5   "brcm,genet-v3", "brcm,genet-v4", "brcm,genet-v5", "brcm,bcm2711-genet-v5" or
 6   "brcm,bcm7712-genet-v5".
 7 - reg: address and length of the register set for the device
 8 - interrupts and/or interrupts-extended: must be two cells, the first cell
 11   optional third interrupt cell for Wake-on-LAN can be specified.
 12   See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
 14 - phy-mode: see ethernet.txt file in the same directory
 15 - #address-cells: should be 1
 16 - #size-cells: should be 1
 [all …]
 
 | 
| H A D | mdio-mux-mmioreg.txt | 1 Properties for an MDIO bus multiplexer controlled by a memory-mapped device3 This is a special case of a MDIO bus multiplexer.  A memory-mapped device,
 4 like an FPGA, is used to control which child bus is connected.  The mdio-mux
 5 node must be a child of the memory-mapped device.  The driver currently only
 6 supports devices with 8, 16 or 32-bit registers.
 10 - compatible : string, must contain "mdio-mux-mmioreg"
 12 - reg : integer, contains the offset of the register that controls the bus
 16 - mux-mask : integer, contains an eight-bit mask that specifies which
 18 	'reg' property of each child mdio-mux node must be constrained by
 23 The FPGA node defines a memory-mapped FPGA with a register space of 0x30 bytes.
 [all …]
 
 | 
| H A D | marvell-orion-mdio.txt | 1 * Marvell MDIO Ethernet Controller interface5 identical unit that provides an interface with the MDIO bus.
 11 - compatible: "marvell,orion-mdio" or "marvell,xmdio"
 12 - reg: address and length of the MDIO registers.  When an interrupt is
 14   otherwise it must be 0x84 bytes to cover the interrupt control
 18 - interrupts: interrupt line number for the SMI error/done interrupt
 19 - clocks: phandle for up to four required clocks for the MDIO instance
 21 The child nodes of the MDIO driver are the individual PHY devices
 22 connected to this MDIO bus. They must have a "reg" property given the
 23 PHY address on the MDIO bus.
 [all …]
 
 | 
| H A D | fsl,cpm-mdio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)3 ---
 4 $id: http://devicetree.org/schemas/net/fsl,cpm-mdio.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Freescale CPM MDIO Device
 10   - Frank Li <Frank.Li@nxp.com>
 15       - enum:
 16           - fsl,pq1-fec-mdio
 17           - fsl,cpm2-mdio-bitbang
 18       - items:
 [all …]
 
 | 
| H A D | brcm,mdio-mux-iproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)3 ---
 4 $id: http://devicetree.org/schemas/net/brcm,mdio-mux-iproc.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: MDIO bus multiplexer found in Broadcom iProc based SoCs.
 10   - Florian Fainelli <f.fainelli@gmail.com>
 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
 15   C-45 Clause. When child bus is selected, one needs to select these two
 16   properties as well to generate desired MDIO transaction on appropriate bus.
 [all …]
 
 | 
| H A D | hisilicon-hns-mdio.txt | 1 Hisilicon MDIO bus controller4 - compatible: can be one of:
 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.
 11 - #address-cells: Must be <1>.
 12 - #size-cells: Must be <0>.  MDIO addresses have no size component.
 14 Typically an MDIO bus might have several children.
 [all …]
 
 | 
| H A D | amlogic,gxl-mdio-mux.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause3 ---
 4 $id: http://devicetree.org/schemas/net/amlogic,gxl-mdio-mux.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Amlogic GXL MDIO bus multiplexer
 10   - Jerome Brunet <jbrunet@baylibre.com>
 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#
 [all …]
 
 | 
| H A D | fsl-fman.txt | 5   - FMan Node6   - FMan Port Node
 7   - FMan MURAM Node
 8   - FMan dTSEC/XGEC/mEMAC Node
 9   - FMan IEEE 1588 Node
 10   - FMan MDIO Node
 11   - Example
 18 Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
 23 - compatible
 28 		FMan block. The offset is 0xc4 from the beginning of the
 [all …]
 
 | 
| H A D | mdio-mux-mmioreg.yaml | 1 # SPDX-License-Identifier: GPL-2.03 ---
 4 $id: http://devicetree.org/schemas/net/mdio-mux-mmioreg.yaml#
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 7 title: Properties for an MDIO bus multiplexer controlled by a memory-mapped device
 10   - Andrew Lunn <andrew@lunn.ch>
 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
 15   node must be a child of the memory-mapped device.  The driver currently only
 16   supports devices with 8, 16 or 32-bit registers.
 [all …]
 
 | 
| H A D | apm-xgene-mdio.txt | 1 APM X-Gene SoC MDIO node3 MDIO node is defined to describe on-chip MDIO controller.
 6 	- compatible: Must be "apm,xgene-mdio-rgmii" or "apm,xgene-mdio-xfi"
 7 	- #address-cells: Must be <1>.
 8 	- #size-cells: Must be <0>.
 9 	- reg: Address and length of the register set
 10 	- clocks: Reference to the clock entry
 12 For the phys on the mdio bus, there must be a node with the following fields:
 13 	- compatible: PHY identifier.  Please refer ./phy.txt for the format.
 14 	- reg: The ID number for the phy.
 [all …]
 
 | 
| /freebsd/sbin/mdconfig/ | 
| H A D | mdconfig.c | 1 /*-2  * SPDX-License-Identifier: BSD-2-Clause
 4  * Copyright (c) 2000-2004 Poul-Henning Kamp <phk@FreeBSD.org>
 57 static struct md_ioctl mdio;  variable
 70 #define OPT_VERBOSE	0x01
 71 #define OPT_UNIT	0x02
 72 #define OPT_DONE	0x04
 73 #define OPT_LIST	0x10
 82 "usage: mdconfig -a -t type [-n] [-o [no]option] ... [-f file]\n"  in usage()
 83 "                [-s size] [-S sectorsize] [-u unit] [-L label]\n"  in usage()
 [all …]
 
 | 
| /freebsd/sys/contrib/device-tree/Bindings/net/dsa/ | 
| H A D | realtek.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)3 ---
 5 $schema: http://devicetree.org/meta-schemas/core.yaml#
 10   - $ref: dsa.yaml#/$defs/ethernet-ports
 13   - Linus Walleij <linus.walleij@linaro.org>
 18   MDIO or SPI.
 20   The SMI "Simple Management Interface" is a two-wire protocol using
 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
 23   SMI-based Realtek devices. The realtek-smi driver is a platform driver
 [all …]
 
 | 
| H A D | realtek-smi.txt | 1 Realtek SMI-based Switches4 The SMI "Simple Management Interface" is a two-wire protocol using
 5 bit-banged GPIO that while it reuses the MDIO lines MCK and MDIO does
 6 not use the MDIO protocol. This binding defines how to specify the
 7 SMI-based Realtek devices.
 11 - compatible: must be exactly one of:
 23 - mdc-gpios: GPIO line for the MDC clock line.
 24 - mdio-gpios: GPIO line for the MDIO data line.
 25 - reset-gpios: GPIO line for the reset signal.
 28 - realtek,disable-leds: if the LED drivers are not used in the
 [all …]
 
 | 
| /freebsd/sys/contrib/device-tree/src/arm64/freescale/ | 
| H A D | fsl-lx2160a-qds.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)7 /dts-v1/;
 9 #include "fsl-lx2160a.dtsi"
 13 	compatible = "fsl,lx2160a-qds", "fsl,lx2160a";
 23 		stdout-path = "serial0:115200n8";
 26 	sb_3v3: regulator-sb3v3 {
 27 		compatible = "regulator-fixed";
 28 		regulator-name = "MC34717-3.3VSB";
 29 		regulator-min-microvolt = <3300000>;
 30 		regulator-max-microvolt = <3300000>;
 [all …]
 
 | 
| H A D | fsl-lx2162a-qds.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)7 /dts-v1/;
 9 #include "fsl-lx2160a.dtsi"
 13 	compatible = "fsl,lx2162a-qds", "fsl,lx2160a";
 23 		stdout-path = "serial0:115200n8";
 26 	sb_3v3: regulator-sb3v3 {
 27 		compatible = "regulator-fixed";
 28 		regulator-name = "LTM4619-3.3VSB";
 29 		regulator-min-microvolt = <3300000>;
 30 		regulator-max-microvolt = <3300000>;
 [all …]
 
 |