Home
last modified time | relevance | path

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

12345678910>>...19

/Linux-v5.4/Documentation/driver-api/phy/
Dphy.rst2 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-v5.4/drivers/phy/ti/
DKconfig6 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
37 tristate "OMAP CONTROL PHY Driver"
40 Enable this to add support for the PHY part present in the control
41 module. This driver has API to power on the USB2 PHY and to write to
43 power on the USB2 PHY is present in OMAP4 and OMAP5. OMAP5 has an
44 additional register to power on USB3 PHY/SATA PHY/PCIE PHY
[all …]
/Linux-v5.4/drivers/phy/broadcom/
DKconfig6 tristate "Broadcom Cygnus PCIe PHY driver"
11 Enable this to support the Broadcom Cygnus PCIe PHY.
15 tristate "Broadcom Stingray USB PHY driver"
20 Enable this to support the Broadcom Stingray USB PHY
26 tristate "Broadcom Kona USB2 PHY Driver"
30 Enable this to support the Broadcom Kona USB 2.0 PHY.
33 tristate "Broadcom Northstar USB 2.0 PHY Driver"
38 Enable this to support Broadcom USB 2.0 PHY connected to the USB
42 tristate "Broadcom Northstar USB 3.0 PHY Driver"
48 Enable this to support Broadcom USB 3.0 PHY connected to the USB
[all …]
/Linux-v5.4/drivers/phy/rockchip/
DKconfig6 tristate "Rockchip Display Port PHY Driver"
10 Enable this to support the Rockchip Display Port PHY.
13 tristate "Rockchip EMMC PHY Driver"
17 Enable this to support the Rockchip EMMC PHY.
20 tristate "Rockchip INNO HDMI PHY Driver"
25 Enable this to support the Rockchip Innosilicon HDMI PHY.
36 Support for Rockchip USB2.0 PHY with Innosilicon IP block.
39 tristate "Rockchip PCIe PHY Driver"
45 Enable this to support the Rockchip PCIe PHY.
48 tristate "Rockchip TYPEC PHY Driver"
[all …]
/Linux-v5.4/drivers/phy/qualcomm/
DKconfig6 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 IPQ806x SATA SerDes/PHY driver"
29 tristate "Qualcomm PCIe Gen2 PHY Driver"
33 Enable this to support the Qualcomm PCIe PHY, used with the Synopsys
37 tristate "Qualcomm QMP PHY Driver"
41 Enable this to support the QMP PHY transceiver that is used
45 tristate "Qualcomm QUSB2 PHY Driver"
50 Enable this to support the HighSpeed QUSB2 PHY transceiver for USB
[all …]
/Linux-v5.4/drivers/phy/
DKconfig3 # PHY
6 menu "PHY Subsystem"
9 bool "PHY Core"
11 Generic PHY support.
13 This framework is designed to provide a generic interface for PHY
15 API by which phy drivers can create PHY using the phy framework and
16 phy users can obtain reference to the PHY. All the users of this
22 Generic MIPI D-PHY support.
24 Provides a number of helpers a core functions for MIPI D-PHY
28 tristate "NXP LPC18xx/43xx SoC USB OTG PHY driver"
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/phy/
Dphy-hisi-inno-usb2.txt1 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 suppports 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 …]
Dphy-bindings.txt2 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 …]
Dphy-mtk-ufs.txt1 MediaTek Universal Flash Storage (UFS) M-PHY binding
4 UFS M-PHY nodes are defined to describe on-chip UFS M-PHY hardware macro.
5 Each UFS M-PHY node should have its own node.
7 To bind UFS M-PHY with UFS host controller, the controller node should
8 contain a phandle reference to UFS M-PHY node.
10 Required properties for UFS M-PHY nodes:
14 - reg : Address and length of the UFS M-PHY register set.
21 "mp": M-PHY core control clock.
Dsamsung-phy.txt14 In case of exynos5433 compatible PHY:
21 the PHY specifier identifies the PHY and its meaning is as follows:
27 supports additional fifth PHY:
30 Samsung EXYNOS SoC series Display Port PHY
39 - #phy-cells : from the generic PHY bindings, must be 0;
41 Samsung S5P/EXYNOS SoC series USB PHY
59 PHY module
64 The first phandle argument in the PHY specifier identifies the PHY, its
90 Then the PHY can be used in other nodes such as:
97 Refer to DT bindings documentation of particular PHY consumer devices for more
[all …]
Dbrcm,stingray-usb-phy.txt1 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
Dphy-stm32-usbphyc.txt1 STMicroelectronics STM32 USB HS PHY controller
3 The STM32 USBPHYC block contains a dual port High Speed UTMI+ PHY and a UTMI
4 switch. It controls PHY configuration and status, and the UTMI+ switch that
5 selects either OTG or HOST controller for the second PHY port. It also sets
11 |_ PHY port#1 _________________ HOST controller
14 |_ PHY port#2 ----| |________________
41 - phy-supply: phandle to the regulator providing 3V3 power to the PHY,
43 - vdda1v1-supply: phandle to the regulator providing 1V1 power to the PHY
44 - vdda1v8-supply: phandle to the regulator providing 1V8 power to the PHY
45 - #phy-cells: see phy-bindings.txt in the same directory, must be <0> for PHY
[all …]
Duniphier-usb2-phy.txt1 Socionext UniPhier USB2 PHY
3 This describes the devicetree bindings for PHY interface built into
7 controller doesn't include its own High-Speed PHY. This needs to specify
8 USB2 PHY instead of USB3 HS-PHY.
16 Each PHY should be represented as a sub-node.
20 - reg: The number of the PHY.
25 Refer to phy/phy-bindings.txt for the generic PHY binding properties.
Dti-phy.txt1 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 OMAP USB2 PHY
34 Should be "ti,dra7x-usb2" for the 1st instance of USB2 PHY on
36 Should be "ti,dra7x-usb2-phy2" for the 2nd instance of USB2 PHY
49 - ctrl-module : phandle of the control module used by PHY driver to power on
[all …]
Dqcom-dwc3-usb-phy.txt1 Qualcomm DWC3 HS AND SS PHY CONTROLLER
4 DWC3 PHY nodes are defined to describe on-chip Synopsis Physical layer
5 controllers. Each DWC3 PHY controller should have its own node.
9 - "qcom,dwc3-hs-usb-phy" for High Speed Synopsis PHY controller
10 - "qcom,dwc3-ss-usb-phy" for Super Speed Synopsis PHY controller
11 - reg: offset and length of the DWC3 PHY controller register set
15 - clock-names: Should contain "ref" for the PHY reference clock
Dqcom-qusb2-phy.txt8 "qcom,msm8996-qusb2-phy" for 14nm PHY on msm8996,
9 "qcom,msm8998-qusb2-phy" for 10nm PHY on msm8998,
10 "qcom,sdm845-qusb2-phy" for 10nm PHY on sdm845.
12 - reg: offset and length of the PHY register set.
21 - vdda-pll-supply: Phandle to 1.8V regulator supply to PHY refclk pll block.
32 added to PHY refgen RESCODE via IMP_CTRL1 register. It is a PHY
34 This property is applicable to only QUSB2 v2 PHY (sdm845).
39 This property is applicable to only QUSB2 v2 PHY (sdm845).
44 This property is applicable to only QUSB2 v2 PHY (sdm845).
50 This property is applicable to only QUSB2 v2 PHY (sdm845).
/Linux-v5.4/Documentation/networking/
Dphy.rst2 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 …]
/Linux-v5.4/drivers/phy/socionext/
DKconfig3 # 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
/Linux-v5.4/drivers/phy/samsung/
DKconfig6 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 "Samsung USB 2.0 PHY driver"
40 Enable this to support the Samsung USB 2.0 PHY driver for Samsung
41 SoCs. This driver provides the interface for USB 2.0 PHY. Support
65 Enable USB PHY support for S5PV210. This option requires that Samsung
[all …]
/Linux-v5.4/drivers/phy/marvell/
DKconfig12 tristate "Marvell Berlin SATA PHY driver"
16 Enable this to support the SATA PHY on Marvell Berlin SoCs.
19 tristate "Marvell Berlin USB PHY Driver"
23 Enable this to support the USB PHY on Marvell Berlin SoCs.
44 Enable this to support Marvell A3700 UTMI PHY driver.
75 tristate "Marvell USB HSIC 28nm PHY Driver"
79 Enable this to support Marvell USB HSIC PHY driver for Marvell
80 SoC. This driver will do the PHY initialization and shutdown.
81 The PHY driver will be used by Marvell ehci driver.
86 tristate "Marvell USB 2.0 28nm PHY Driver"
[all …]
/Linux-v5.4/net/mac80211/
Ddebugfs_sta.c695 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_40MHZ_IN_2G, in sta_he_capa_read()
697 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_40MHZ_80MHZ_IN_5G, in sta_he_capa_read()
699 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_160MHZ_IN_5G, in sta_he_capa_read()
701 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_80PLUS80_MHZ_IN_5G, in sta_he_capa_read()
703 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_RU_MAPPING_IN_2G, in sta_he_capa_read()
705 PFLAG(PHY, 0, CHANNEL_WIDTH_SET_RU_MAPPING_IN_5G, in sta_he_capa_read()
723 PFLAG(PHY, 1, DEVICE_CLASS_A, in sta_he_capa_read()
725 PFLAG(PHY, 1, LDPC_CODING_IN_PAYLOAD, in sta_he_capa_read()
727 PFLAG(PHY, 1, HE_LTF_AND_GI_FOR_HE_PPDUS_0_8US, in sta_he_capa_read()
731 PFLAG(PHY, 2, NDP_4x_LTF_AND_3_2US, "NDP-4X-LTF-AND-3-2US"); in sta_he_capa_read()
[all …]
/Linux-v5.4/drivers/phy/renesas/
DKconfig6 tristate "Renesas R-Car generation 2 USB PHY driver"
10 Support for USB PHY found on Renesas R-Car generation 2 SoCs.
13 tristate "Renesas R-Car generation 3 PCIe PHY driver"
17 Support for the PCIe PHY found on Renesas R-Car generation 3 SoCs.
20 tristate "Renesas R-Car generation 3 USB 2.0 PHY driver"
27 Support for USB 2.0 PHY found on Renesas R-Car generation 3 SoCs.
30 tristate "Renesas R-Car generation 3 USB 3.0 PHY driver"
34 Support for USB 3.0 PHY found on Renesas R-Car generation 3 SoCs.
/Linux-v5.4/drivers/phy/mediatek/
DKconfig6 tristate "MediaTek T-PHY Driver"
10 Say 'Y' here to add support for MediaTek T-PHY driver,
12 SATA, and meanwhile supports two version T-PHY which have
13 different banks layout, the T-PHY with shared banks between
18 tristate "MediaTek UFS M-PHY driver"
22 Support for UFS M-PHY on MediaTek chipsets.
28 tristate "MediaTek XS-PHY Driver"
32 Enable this to support the SuperSpeedPlus XS-PHY transceiver for
/Linux-v5.4/drivers/phy/hisilicon/
DKconfig6 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.
36 tristate "HiSilicon INNO USB2 PHY support"
41 Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports
46 tristate "HIX5HD2 SATA PHY Driver"
51 Support for SATA PHY on Hisilicon hix5hd2 Soc.
/Linux-v5.4/drivers/phy/cadence/
DKconfig7 tristate "Cadence MHDP DisplayPort PHY driver"
12 Support for Cadence MHDP DisplayPort PHY.
15 tristate "Cadence D-PHY Support"
20 Choose this option if you have a Cadence D-PHY in your
25 tristate "Cadence Sierra PHY Driver"
29 Enable this to support the Cadence Sierra PHY driver

12345678910>>...19