2 # PHY Layer Configuration
6 tristate "PHY Device support and infrastructure"
8 depends on NET_ETHERNET && (BROKEN || !S390)
10 Ethernet controllers are usually attached to PHY
11 devices. This option provides infrastructure for
16 comment "MII PHY device drivers"
19 tristate "Drivers for Marvell PHYs"
21 Currently has a driver for the 88E1011S
24 tristate "Drivers for Davicom PHYs"
26 Currently supports dm9161e and dm9131
29 tristate "Drivers for Quality Semiconductor PHYs"
31 Currently supports the qs6612
34 tristate "Drivers for the Intel LXT PHYs"
36 Currently supports the lxt970, lxt971
39 tristate "Drivers for the Cicada PHYs"
41 Currently supports the cis8204
44 tristate "Drivers for the Vitesse PHYs"
46 Currently supports the vsc8244
49 tristate "Drivers for SMSC PHYs"
51 Currently supports the LAN83C185 PHY
54 tristate "Drivers for Broadcom PHYs"
56 Currently supports the BCM5411, BCM5421 and BCM5461 PHYs.
59 tristate "Drivers for ICPlus PHYs"
61 Currently supports the IP175C PHY.
64 tristate "Drivers for PHY emulation on fixed speed/link"
66 Adds the driver to PHY layer to cover the boards that do not have any PHY bound,
67 but with the ability to manipulate the speed/link in software. The relevant MII
68 speed/duplex parameters could be effectively handled in a user-specified function.
69 Currently tested with mpc866ads.
71 config FIXED_MII_10_FDX
72 bool "Emulation for 10M Fdx fixed PHY behavior"
75 config FIXED_MII_100_FDX
76 bool "Emulation for 100M Fdx fixed PHY behavior"
79 config FIXED_MII_1000_FDX
80 bool "Emulation for 1000M Fdx fixed PHY behavior"
84 int "Number of emulated PHYs to allocate "
88 Sometimes it is required to have several independent emulated
89 PHYs on the bus (in case of multi-eth but phy-less HW for instance).
90 This control will have specified number allocated for each fixed
94 tristate "Support for bitbanged MDIO buses"
96 This module implements the MDIO bus protocol in software,
97 for use by low level drivers that export the ability to
98 drive the relevant pins.