Home
last modified time | relevance | path

Searched refs:PHY (Results 1 – 25 of 46) sorted by relevance

12

/linux-2.6.39/Documentation/networking/
Dphy.txt3 PHY Abstraction Layer
10 PHY. The PHY concerns itself with negotiating link parameters with the link
17 the PHY management code with the network driver. This has resulted in large
23 accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
30 Basically, this layer is meant to provide an interface to PHY devices which
36 Most network devices are connected to a PHY by means of a management bus.
46 mii_id is the address on the bus for the PHY, and regnum is the register
67 Connecting to a PHY
70 between the PHY device, and the network device. At this time, the PHY's bus
72 At this point, there are several ways to connect to the PHY:
[all …]
Ddm9000.txt90 device, whether or not an external PHY is attached to the device and
109 The chip is connected to an external PHY.
118 Switch to using the simpler PHY polling method which does not
119 try and read the MII PHY state regularly. This is only available
120 when using the internal PHY. See the section on link state polling
124 "Force simple NSR based PHY polling" allows this flag to be
128 PHY Link state polling
133 depending on the version of the chip and on which PHY is being used.
135 For the internal PHY, the original (and currently default) method is
140 To reduce the overhead for the internal PHY, there is now the option
[all …]
Dstmmac.txt25 phyaddr: to manually provide the physical address to the PHY device;
91 The driver is compatible with PAL to work with PHY and GPHY devices.
/linux-2.6.39/drivers/net/phy/
DKconfig2 # PHY Layer Configuration
6 tristate "PHY Device support and infrastructure"
10 Ethernet controllers are usually attached to PHY
12 managing PHY devices.
16 comment "MII PHY device drivers"
60 tristate "Drivers for Broadcom 63xx SOCs internal PHY"
72 Supports the Realtek 821x PHY.
77 Currently supports the DP83865 PHY.
85 tristate "Driver for LSI ET1011C PHY"
87 Supports the LSI ET1011C PHY.
[all …]
/linux-2.6.39/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt3 The MDIO is a bus to which the PHY devices are connected. For each
5 the definition of the PHY node in booting-without-of.txt for an example
6 of how to define a PHY.
26 As of this writing, every tsec is associated with an internal TBI PHY.
27 This PHY is accessed through the local MDIO bus. These buses are defined
46 - phy-handle : The phandle for the PHY connected to this ethernet
52 - phy-connection-type : a string naming the controller/PHY interface type,
Dphy.txt1 PHY nodes
/linux-2.6.39/drivers/atm/
Dnicstarmac.copyright6 * 10/1/97 - commented out CFG_PHYIE bit - we don't care when the PHY
10 * 10/5/97 - added code to handle PHY interrupts, disable PHY on
11 * loss of link, and correctly re-enable PHY when link is
19 * PHY component is expected to be 155 Mbps S/UNI-Lite or IDT 77155;
20 * see init_nicstar() for PHY initialization to change this. This driver
DKconfig190 bool "Use suni PHY driver (155Mbps)"
202 bool "Use IDT77015 PHY driver (25Mbps)"
302 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
388 bool "Use S/UNI PHY driver"
/linux-2.6.39/drivers/net/wireless/b43/
DKconfig90 bool "Support for 802.11n (N-PHY) devices (EXPERIMENTAL)"
93 Support for the N-PHY.
95 This enables support for devices with N-PHY.
101 bool "Support for low-power (LP-PHY) devices (EXPERIMENTAL)"
105 Support for the LP-PHY.
106 The LP-PHY is a low-power PHY built into some notebooks
/linux-2.6.39/drivers/usb/otg/
DKconfig77 UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs
79 The definition of internal PHY APIs are in the mach-omap2 layer.
109 handles PHY initialization, clock management, and workarounds
114 has an external PHY.
/linux-2.6.39/Documentation/devicetree/bindings/powerpc/4xx/
Demac.txt45 - phy-mode : string, mode of operations of the PHY interface.
51 MDIO lines for the PHY used by this EMAC.
66 - phy-address : 1 cell, optional, MDIO address of the PHY. If absent,
68 - phy-map : 1 cell, optional, bitmap of addresses to probe the PHY
/linux-2.6.39/arch/arm/mach-davinci/
DKconfig185 bool "RMII Ethernet PHY"
187 Say Y if you want to use the RMII PHY on the DA850/OMAP-L138/AM18x
188 EVM. This PHY is found on the UI daughter card that is supplied with
190 NOTE: Please take care while choosing this option, MII PHY will
/linux-2.6.39/arch/powerpc/boot/dts/
Dtqm8xx.dts83 PHY: ethernet-phy@f { label
96 phy-handle = <&PHY>;
Dmpc866ads.dts75 PHY: ethernet-phy@f { label
89 phy-handle = <&PHY>;
Dpdm360ng.dts276 // USB1 using external ULPI PHY
287 // USB0 using internal UTMI PHY
/linux-2.6.39/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Ducc.txt48 - phy-handle : The phandle for the PHY connected to this controller.
51 - phy-connection-type : a string naming the controller/PHY interface type,
/linux-2.6.39/Documentation/devicetree/bindings/
Dmarvell.txt74 The MDIO is a bus to which the PHY devices are connected. For each
76 the definition of the PHY node below for an example of how to define
77 a PHY.
139 - phy : the phandle for the PHY connected to this ethernet
156 c) Marvell Discovery PHY nodes
165 Example Discovery PHY node:
/linux-2.6.39/drivers/of/
DKconfig70 OpenFirmware MDIO bus (Ethernet PHY) accessors
/linux-2.6.39/Documentation/ABI/testing/
Dsysfs-class-uwb_rc10 Wideband MAC and PHY Specification' is assumed.
136 This gives an estimate on a suitable PHY rate. Refer
Dsysfs-class-uwb_rc-wusbhc32 The maximum PHY rate to use for all connected devices.
/linux-2.6.39/drivers/net/wireless/ath/ath5k/
DKconfig17 PHY: RF5111/2111 RF5112/2112 RF5413/2413
/linux-2.6.39/drivers/net/ixp2000/
Dixp2400_tx.uc2 * TX ucode for the Intel IXP2400 in POS-PHY mode.
12 * - The IXP2400 MSF is configured for POS-PHY mode, in a mode where
Dixp2400_rx.uc2 * RX ucode for the Intel IXP2400 in POS-PHY mode.
12 * - The IXP2400 MSF is configured for POS-PHY mode, in a mode where
/linux-2.6.39/drivers/net/wireless/rtl818x/
Drtl818x.h133 u8 PHY[4]; member
/linux-2.6.39/Documentation/networking/caif/
DLinux-CAIF.txt91 - Clients must implement PHY layer to access physical HW
93 - Clients must call configuration function to add PHY layer.

12