Searched refs:PHY (Results 1 – 25 of 57) sorted by relevance
123
| /linux-3.4.99/Documentation/networking/ |
| D | phy.txt | 3 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
68 Connecting to a PHY
71 between the PHY device, and the network device. At this time, the PHY's bus
73 At this point, there are several ways to connect to the PHY:
[all …]
|
| D | dm9000.txt | 90 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 …]
|
| D | stmmac.txt | 27 phyaddr: to manually provide the physical address to the PHY device;
102 The driver is compatible with PAL to work with PHY and GPHY devices.
134 o interface: PHY device's interface.
177 o irqs: list of IRQs, one per PHY.
178 o probed_phy_irq: if irqs is NULL, use this for probed PHY.
202 there are two MAC cores: one MAC is for MDIO Bus/PHY emulation
224 and the second one, with a real PHY device attached to the bus,
|
| /linux-3.4.99/drivers/net/phy/ |
| D | Kconfig | 2 # 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"
65 tristate "Drivers for Broadcom 63xx SOCs internal PHY"
78 Supports the Realtek 821x PHY.
83 Currently supports the DP83865 PHY.
91 tristate "Driver for LSI ET1011C PHY"
93 Supports the LSI ET1011C PHY.
[all …]
|
| /linux-3.4.99/drivers/net/wireless/b43/ |
| D | Kconfig | 112 bool "Support for 802.11n (N-PHY) devices (EXPERIMENTAL)"
115 Support for the N-PHY.
117 This enables support for devices with N-PHY.
123 bool "Support for low-power (LP-PHY) devices"
127 Support for the LP-PHY.
128 The LP-PHY is a low-power PHY built into some notebooks
133 bool "Support for HT-PHY (high throughput) devices (EXPERIMENTAL)"
136 Support for the HT-PHY.
138 Enables support for BCM4331 and possibly other chipsets with that PHY.
141 bool "Support for LCN-PHY devices (BROKEN)"
[all …]
|
| /linux-3.4.99/drivers/atm/ |
| D | nicstarmac.copyright | 6 * 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
|
| /linux-3.4.99/drivers/net/ethernet/davicom/ |
| D | Kconfig | 18 bool "Force simple NSR based PHY polling"
23 costly MII PHY reads. Note, this will not work if the chip is
24 operating with an external PHY.
|
| /linux-3.4.99/Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 3 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,
|
| D | smsc911x.txt | 9 - phy-mode : String, operation mode of the PHY interface.
21 internal PHY
23 external PHY
|
| D | fsl-fec.txt | 7 - phy-mode : String, operation mode of the PHY interface.
|
| D | phy.txt | 1 PHY nodes
|
| D | macb.txt | 11 - phy-mode: String, operation mode of the PHY interface.
|
| D | stmmac.txt | 12 - phy-mode: String, operation mode of the PHY interface.
|
| /linux-3.4.99/drivers/usb/otg/ |
| D | Kconfig | 77 UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs
79 The definition of internal PHY APIs are in the mach-omap2 layer.
95 handles PHY initialization, clock management, and workarounds
100 has an external PHY.
|
| /linux-3.4.99/Documentation/ABI/stable/ |
| D | firewire-cdev | 27 - PHY packet transmission and reception
48 - PHY packet transmission and reception
73 request reception, or PHY packet reception. Always use a read
|
| /linux-3.4.99/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | emac.txt | 45 - 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-3.4.99/drivers/net/ethernet/freescale/ |
| D | Kconfig | 50 an external MII PHY chip or 10 Mbps 7-wire interface
52 If your board uses an external PHY connected to FEC, enable this.
|
| /linux-3.4.99/Documentation/scsi/ |
| D | ufs.txt | 28 on MIPI M-PHY physical layer standard. UFS uses MIPI M-PHY as the
85 MIPI UniPro and MIPI M-PHY. UIC provides 2 service access points
|
| /linux-3.4.99/arch/arm/mach-davinci/ |
| D | Kconfig | 185 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-3.4.99/arch/powerpc/boot/dts/ |
| D | mpc866ads.dts | 75 PHY: ethernet-phy@f { label
89 phy-handle = <&PHY>;
|
| D | tqm8xx.dts | 108 PHY: ethernet-phy@f { label
121 phy-handle = <&PHY>;
|
| /linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| D | ucc.txt | 48 - phy-handle : The phandle for the PHY connected to this controller.
51 - phy-connection-type : a string naming the controller/PHY interface type,
|
| /linux-3.4.99/Documentation/devicetree/bindings/ |
| D | marvell.txt | 74 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-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-class-uwb_rc | 10 Wideband MAC and PHY Specification' is assumed.
136 This gives an estimate on a suitable PHY rate. Refer
|
| D | sysfs-class-uwb_rc-wusbhc | 32 The maximum PHY rate to use for all connected devices.
|
123