| /linux/Documentation/translations/zh_CN/driver-api/phy/ |
| H A D | phy.rst | 11 PHY子系统
16 本文档解释了 PHY 的通用框架和提供的API，以及使用方法。
21 *PHY* 是物理层的缩写，它被用来把设备连接到一个物理媒介，例如USB控制器
22 有一个提供序列化、反序列化、编码、解码和负责获取所需的数据传输速率的 PHY。
23 注意，有些USB控制器内嵌了 PHY 的功能，其它的则使用了一个外置的PHY，此外
24 使用 PHY 的设备还有无线网、以太网、SATA等（控制器）。
26 创建这个框架的目的是将遍布 Linux 内核的 PHY 驱动程序融入到 drivers/phy，
29 该框架仅适用于使用外部 PHY（PHY 功能未嵌入控制器内）的设备。
31 注册/注销PHY provider
34 PHY provider是指实现一个或多个 PHY 实例的实体。对于 PHY provider 仅
[all …]
|
| /linux/Documentation/driver-api/phy/ |
| H A D | phy.rst | 2 PHY subsystem
7 This document explains the Generic PHY Framework along with the APIs provided,
13 *PHY* is the abbreviation for physical layer. It is used to connect a device
14 to the physical medium e.g., the USB controller has a PHY to provide functions
17 controllers have PHY functionality embedded into it and others use an external
18 PHY. Other peripherals that use PHY include Wireless LAN, Ethernet,
21 The intention of creating this framework is to bring the PHY drivers spread
25 This framework will be of use only to devices that use external PHY (PHY
28 Registering/Unregistering the PHY provider
31 PHY provider refers to an entity that implements one or more PHY instances.
[all …]
|
| /linux/drivers/phy/qualcomm/ |
| H A D | Kconfig | 6 tristate "Atheros AR71XX/9XXX USB PHY driver"
12 Enable this to support the USB PHY on Atheros AR71XX/9XXX SoCs.
15 tristate "Qualcomm APQ8064 SATA SerDes/PHY driver"
22 tristate "Qualcomm eDP PHY driver"
28 Enable this driver to support the Qualcomm eDP PHY found in various
32 tristate "Qualcomm IPQ4019 USB PHY driver"
36 Support for the USB PHY-s on Qualcomm IPQ40xx SoC-s.
39 tristate "Qualcomm IPQ806x SATA SerDes/PHY driver"
46 tristate "Qualcomm PCIe Gen2 PHY Driver"
50 Enable this to support the Qualcomm PCIe PHY, used with the Synopsys
[all …]
|
| /linux/drivers/phy/broadcom/ |
| H A D | Kconfig | 5 menu "PHY drivers for Broadcom platforms"
8 tristate "BCM63xx USBH PHY driver"
12 Enable this to support the BCM63xx USBH PHY driver.
16 tristate "Broadcom Cygnus PCIe PHY driver"
21 Enable this to support the Broadcom Cygnus PCIe PHY.
25 tristate "Broadcom Stingray USB PHY driver"
30 Enable this to support the Broadcom Stingray USB PHY
36 tristate "Broadcom Kona USB2 PHY Driver"
40 Enable this to support the Broadcom Kona USB 2.0 PHY.
43 tristate "Broadcom Northstar USB 2.0 PHY Driver"
[all …]
|
| /linux/drivers/phy/rockchip/ |
| H A D | Kconfig | 6 tristate "Rockchip Display Port PHY Driver"
10 Enable this to support the Rockchip Display Port PHY.
25 tristate "Rockchip EMMC PHY Driver"
29 Enable this to support the Rockchip EMMC PHY.
32 tristate "Rockchip INNO HDMI PHY Driver"
38 Enable this to support the Rockchip Innosilicon HDMI PHY.
49 Support for Rockchip USB2.0 PHY with Innosilicon IP block.
52 tristate "Rockchip Innosilicon MIPI CSI PHY driver"
57 Enable this to support the Rockchip MIPI CSI PHY with
61 tristate "Rockchip Innosilicon MIPI/LVDS/TTL PHY driver"
[all …]
|
| /linux/drivers/phy/ti/ |
| H A D | Kconfig | 6 tristate "TI DA8xx USB PHY Driver"
11 Enable this to support the USB PHY on DA8xx SoCs.
13 This driver controls both the USB 1.1 PHY and the USB 2.0 PHY.
16 tristate "TI dm816x USB PHY driver"
33 This option enables support for TI AM654 SerDes PHY used for
53 tristate "OMAP CONTROL PHY Driver"
56 Enable this to add support for the PHY part present in the control
57 module. This driver has API to power on the USB2 PHY and to write to
59 power on the USB2 PHY is present in OMAP4 and OMAP5. OMAP5 has an
60 additional register to power on USB3 PHY/SATA PHY/PCIE PHY
[all …]
|
| /linux/drivers/phy/mediatek/ |
| H A D | Kconfig | 6 tristate "MediaTek PCIe-PHY Driver"
11 Say 'Y' here to add support for MediaTek PCIe PHY driver.
12 This driver create the basic PHY instance and provides initialize
17 tristate "MediaTek 10GE SerDes XFI T-PHY driver"
22 Say 'Y' here to add support for MediaTek XFI T-PHY driver.
23 The driver provides access to the Ethernet SerDes T-PHY supporting
28 tristate "MediaTek T-PHY Driver"
34 Say 'Y' here to add support for MediaTek T-PHY driver,
36 SATA, and meanwhile supports two version T-PHY which have
37 different banks layout, the T-PHY with shared banks between
[all …]
|
| /linux/drivers/phy/marvell/ |
| H A D | Kconfig | 6 bool "Armada 375 USB cluster PHY support" if COMPILE_TEST
12 tristate "Marvell Berlin SATA PHY driver"
17 Enable this to support the SATA PHY on Marvell Berlin SoCs.
20 tristate "Marvell Berlin USB PHY Driver"
25 Enable this to support the USB PHY on Marvell Berlin SoCs.
46 Enable this to support Marvell A3700 UTMI PHY driver.
76 Enable this to support Marvell CP110 UTMI PHY driver.
85 tristate "Marvell USB HSIC 28nm PHY Driver"
89 Enable this to support Marvell USB HSIC PHY driver for Marvell
90 SoC. This driver will do the PHY initialization and shutdown.
[all …]
|
| /linux/drivers/phy/cadence/ |
| H A D | Kconfig | 7 tristate "Cadence Torrent PHY driver"
13 Support for Cadence Torrent PHY.
16 tristate "Cadence D-PHY Support"
21 Choose this option if you have a Cadence D-PHY in your
26 tristate "Cadence D-PHY Rx Support"
31 Support for Cadence D-PHY in Rx configuration.
34 tristate "Cadence Sierra PHY Driver"
39 Enable this to support the Cadence Sierra PHY driver
42 tristate "Cadence Salvo PHY Driver"
46 Enable this to support the Cadence SALVO PHY driver,
[all …]
|
| /linux/drivers/phy/samsung/ |
| H A D | Kconfig | 6 tristate "Exynos SoC series Display Port PHY driver"
12 Support for Display Port PHY found on Samsung Exynos SoCs.
15 tristate "S5P/Exynos SoC series MIPI CSI-2/DSI PHY driver"
25 bool "Exynos PCIe PHY driver"
29 Enable PCIe PHY support for Exynos SoC series.
30 This driver provides PHY interface for Exynos PCIe controller.
33 tristate "Exynos SoC series UFS PHY driver"
38 Enable this to support the Samsung Exynos SoC UFS PHY driver for
40 controller to do PHY related programming.
43 tristate "S5P/Exynos SoC series USB 2.0 PHY drive
[all...] |
| /linux/drivers/phy/socionext/ |
| H A D | Kconfig | 3 # PHY drivers for Socionext platforms.
7 tristate "UniPhier USB2 PHY driver"
13 Enable this to support USB PHY implemented on USB2 controller
15 with USB 2.0 PHY that is part of the UniPhier SoC.
16 In case of Pro4, it is necessary to specify this USB2 PHY instead
17 of USB3 HS-PHY.
20 tristate "UniPhier USB3 PHY driver"
25 Enable this to support USB PHY implemented in USB3 controller
29 tristate "Uniphier PHY driver for PCIe controller"
35 Enable this to support PHY implemented in PCIe controller
[all …]
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | phy-hisi-inno-usb2.txt | 1 Device tree bindings for HiSilicon INNO USB2 PHY
7 - reg: Should be the address space for PHY configuration register in peripheral
9 - clocks: The phandle and clock specifier pair for INNO USB2 PHY device
11 - resets: The phandle and reset specifier pair for INNO USB2 PHY device reset
16 The INNO USB2 PHY device should be a child node of peripheral controller that
17 contains the PHY configuration register, and each device supports up to 2 PHY
18 ports which are represented as child nodes of INNO USB2 PHY device.
20 Required properties for PHY port node:
21 - reg: The PHY port instance number.
22 - #phy-cells: Defined by generic PHY bindings. Must be 0.
[all …]
|
| H A D | phy-bindings.txt | 2 information about PHY subsystem refer to Documentation/driver-api/phy/phy.rst
4 PHY device node
8 #phy-cells: Number of cells in a PHY specifier; The meaning of all those
9 cells is defined by the binding for the phy node. The PHY
11 PHY.
14 phy-supply: Phandle to a regulator that provides power to the PHY. This
15 regulator will be managed during the PHY power on/off sequence.
29 That node describes an IP block (PHY provider) that implements 2 different PHYs.
33 PHY user node
37 phys : the phandle for the PHY device (used by the PHY subsystem; not to be
[all …]
|
| H A D | brcm,stingray-usb-phy.txt | 1 Broadcom Stingray USB PHY
5 - "brcm,sr-usb-combo-phy" is combo PHY has two PHYs, one SS and one HS.
6 - "brcm,sr-usb-hs-phy" is a single HS PHY.
7 - reg: offset and length of the PHY blocks registers
10 the PHY number of two PHYs. 0 for HS PHY and 1 for SS PHY.
13 Refer to phy/phy-bindings.txt for the generic PHY binding properties
|
| H A D | ti-phy.txt | 1 TI PHY: DT DOCUMENTATION FOR PHYs in TI PLATFORMs
3 OMAP CONTROL PHY
11 e.g. USB3 PHY and SATA PHY on OMAP5.
14 e.g. PCIE PHY in DRA7x
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
30 TI PIPE3 PHY
54 PHY). If "id" is not provided, it is set to default value of '1'.
62 - ctrl-module : phandle of the control module used by PHY driver to power on
63 the PHY.
[all …]
|
| /linux/drivers/phy/freescale/ |
| H A D | Kconfig | 6 tristate "Freescale i.MX8M USB3 PHY"
12 tristate "Mixel LVDS PHY support"
17 Enable this to add support for the Mixel LVDS PHY as found
21 tristate "Mixel MIPI DSI PHY support"
27 Enable this to add support for the Mixel DSI PHY as found
31 tristate "Freescale i.MX8M PCIE PHY"
35 Enable this to add support for the PCIE PHY as found on
39 tristate "Freescale i.MX8QM HSIO PHY"
43 Enable this to add support for the HSIO PHY as found on
47 tristate "Samsung HDMI PHY support"
[all …]
|
| /linux/Documentation/networking/ |
| H A D | phy.rst | 2 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
37 Most network devices are connected to a PHY by means of a management bus.
47 mii_id is the address on the bus for the PHY, and regnum is the register
75 between the clock line (RXC or TXC) and the data lines to let the PHY (clock
77 PHY library offers different types of PHY_INTERFACE_MODE_RGMII* values to let
78 the PHY driver and optionally the MAC driver, implement the required delay. The
[all …]
|
| H A D | phy-link-topology.rst | 5 PHY link topology
11 The PHY link topology representation in the networking stack aims at representing
21 | MAC | ------ | PHY | ---- | Port | ---... to LP
25 Commands that needs to configure the PHY will go through the net_device.phydev
26 field to reach the PHY and perform the relevant configuration.
41 Knowing that some modules embed a PHY, the actual link is more like ::
44 | MAC | -------- | PHY (on SFP) |
47 In this case, the SFP PHY is handled by phylib, and registered by phylink through
56 | MAC | ------- | PHY (media converter) | ------- | PHY (on SFP) |
63 PHY on the link, for use by both kernel drivers and subsystems, but also to
[all …]
|
| H A D | oa-tc6-framework.rst | 4 OPEN Alliance 10BASE-T1x MAC-PHY Serial Interface (TC6) Framework Support
12 PHY supporting full duplex point-to-point operation over 1 km of single
14 PHY supporting full / half duplex point-to-point operation over 15 m of
21 works in conjunction with the 10BASE-T1S PHY operating in multidrop mode.
29 The MAC-PHY solution integrates an IEEE Clause 4 MAC and a 10BASE-T1x PHY
38 The MAC-PHY is specified to carry both data (Ethernet frames) and control
54 low to the MAC-PHY and ends with the deassertion of CSn high. In between
78 10BASE-T1x MAC-PHY Serial Interface Specification,
88 | | | MAC-PHY |
90 | SPI Host | | | SPI Slave | | MAC | | PHY | |
[all …]
|
| /linux/drivers/phy/hisilicon/ |
| H A D | Kconfig | 6 tristate "hi6220 USB PHY support"
12 Enable this to support the HISILICON HI6220 USB PHY.
17 tristate "hi3660 USB PHY support"
22 Enable this to support the HISILICON HI3660 USB PHY.
27 tristate "hi3670 USB PHY support"
32 Enable this to support the HISILICON HI3670 USB PHY.
37 tristate "hi3670 PCIe PHY support"
42 Enable this to support the HiSilicon hi3670 PCIe PHY.
56 tristate "HiSilicon INNO USB2 PHY support"
61 Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports
[all …]
|
| /linux/drivers/phy/starfive/ |
| H A D | Kconfig | 9 tristate "StarFive JH7110 D-PHY RX support"
14 Choose this option if you have a StarFive D-PHY in your
19 tristate "StarFive JH7110 D-PHY TX Support"
24 Choose this option if you have a StarFive D-PHY TX in your
29 tristate "Starfive JH7110 PCIE 2.0/USB 3.0 PHY support"
33 Enable this to support the StarFive PCIe 2.0 PHY,
34 or used as USB 3.0 PHY.
39 tristate "Starfive JH7110 USB 2.0 PHY support"
43 Enable this to support the StarFive USB 2.0 PHY,
|
| /linux/drivers/phy/renesas/ |
| H A D | Kconfig | 14 tristate "Renesas R-Car generation 2 USB PHY driver"
18 Support for USB PHY found on Renesas R-Car generation 2 SoCs.
21 tristate "Renesas R-Car generation 3 PCIe PHY driver"
25 Support for the PCIe PHY found on Renesas R-Car generation 3 SoCs.
28 tristate "Renesas R-Car generation 3 USB 2.0 PHY driver"
35 Support for USB 2.0 PHY found on Renesas R-Car generation 3 SoCs.
38 tristate "Renesas R-Car generation 3 USB 3.0 PHY driver"
42 Support for USB 3.0 PHY found on Renesas R-Car generation 3 SoCs.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-phydev | 6 Symbolic link to the network device this PHY device is
14 This attribute contains the boolean value whether a given PHY
17 PHY configurations.
24 This attribute contains the 32-bit PHY Identifier as reported
34 This attribute contains the PHY interface as configured by the
37 appropriate mode for its data lines to the PHY hardware.
51 Boolean value indicating whether the PHY device is used in
61 configuration bits passed from the consumer of the PHY
62 (Ethernet MAC, switch, etc.) to the PHY driver. The flags are
65 for facilitating the debugging of PHY drivers.
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | micrel.txt | 1 Micrel PHY properties.
21 See the respective PHY datasheet for the mode values.
29 Note that this option in only needed for certain PHY revisions with a
40 - micrel,fiber-mode: If present the PHY is configured to operate in fiber mode
43 by the FXEN boot strapping pin. It can't be determined from the PHY
44 registers whether the PHY is in fiber mode, so this boolean device tree
47 In fiber mode, auto-negotiation is disabled and the PHY can only work in
51 PHY is probed.
53 Some PHYs have a COMA mode input pin which puts the PHY into
|
| /linux/Documentation/networking/device_drivers/ethernet/davicom/ |
| H A D | dm9000.rst | 94 device, whether or not an external PHY is attached to the device and
113 The chip is connected to an external PHY.
122 Switch to using the simpler PHY polling method which does not
123 try and read the MII PHY state regularly. This is only available
124 when using the internal PHY. See the section on link state polling
128 "Force simple NSR based PHY polling" allows this flag to be
132 PHY Link state polling
137 depending on the version of the chip and on which PHY is being used.
139 For the internal PHY, the original (and currently default) method is
144 To reduce the overhead for the internal PHY, there is now the option
[all …]
|