Home
last modified time | relevance | path

Searched full:xfi (Results 1 – 25 of 47) sorted by relevance

12

/linux-6.12.1/Documentation/devicetree/bindings/phy/
Dmediatek,mt7988-xfi-tphy.yaml4 $id: http://devicetree.org/schemas/phy/mediatek,mt7988-xfi-tphy.yaml#
7 title: MediaTek MT7988 XFI T-PHY
13 The MediaTek XFI SerDes T-PHY provides the physical SerDes lanes
20 const: mediatek,mt7988-xfi-tphy
27 - description: XFI PHY clock
28 - description: XFI register clock
45 is required for XFI Port0 of the MT7988 SoC to be in compliance with
69 compatible = "mediatek,mt7988-xfi-tphy";
Dapm-xgene-phy.txt11 1 (SGMII), 2 (PCIe), 3 (USB), and 4 (XFI).
/linux-6.12.1/Documentation/devicetree/bindings/clock/
Dmediatek,mt7988-xfi-pll.yaml4 $id: http://devicetree.org/schemas/clock/mediatek,mt7988-xfi-pll.yaml#
7 title: MediaTek MT7988 XFI PLL Clock Controller
13 The MediaTek XFI PLL controller provides the 156.25MHz clock for the
18 const: mediatek,mt7988-xfi-pll
43 compatible = "mediatek,mt7988-xfi-pll";
/linux-6.12.1/drivers/clk/mediatek/
Dclk-mt7988-xfipll.c15 /* Register to control USXGMII XFI PLL analog */
66 { .compatible = "mediatek,mt7988-xfi-pll", .data = &xfipll_desc },
81 MODULE_DESCRIPTION("MediaTek MT7988 XFI PLL clock driver");
/linux-6.12.1/drivers/net/ethernet/sfc/falcon/
Denum.h21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
25 * @LOOPBACK_XFI_FAR: loopback after XFI serdes
36 * @LOOPBACK_XFI_WS: wireside loopback excluding XFI serdes
37 * @LOOPBACK_XFI_WS_FAR: wireside loopback including XFI serdes
/linux-6.12.1/drivers/net/ethernet/sfc/siena/
Denum.h21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
25 * @LOOPBACK_XFI_FAR: loopback after XFI serdes
36 * @LOOPBACK_XFI_WS: wireside loopback excluding XFI serdes
37 * @LOOPBACK_XFI_WS_FAR: wireside loopback including XFI serdes
/linux-6.12.1/drivers/net/ethernet/sfc/
Denum.h21 * @LOOPBACK_XFI: loopback within BPX before XFI serdes
25 * @LOOPBACK_XFI_FAR: loopback after XFI serdes
36 * @LOOPBACK_XFI_WS: wireside loopback excluding XFI serdes
37 * @LOOPBACK_XFI_WS_FAR: wireside loopback including XFI serdes
/linux-6.12.1/drivers/phy/mediatek/
Dphy-mtk-xfi-tphy.c3 * MediaTek 10GE SerDes XFI T-PHY driver
60 * struct mtk_xfi_tphy - run-time data of the XFI phy instance
77 * @xfi_tphy: XFI phy instance.
434 { .compatible = "mediatek,mt7988-xfi-tphy", },
442 .name = "mtk-xfi-tphy",
448 MODULE_DESCRIPTION("MediaTek 10GE SerDes XFI T-PHY driver");
DKconfig17 tristate "MediaTek 10GE SerDes XFI T-PHY driver"
22 Say 'Y' here to add support for MediaTek XFI T-PHY driver.
DMakefile11 obj-$(CONFIG_PHY_MTK_XFI_TPHY) += phy-mtk-xfi-tphy.o
/linux-6.12.1/sound/pci/ctxfi/
Dxfi.c3 * xfi linux driver.
101 strcpy(card->driver, "SB-XFi"); in ct_card_probe()
DMakefile2 snd-ctxfi-y := xfi.o ctatc.o ctvmem.o ctpcm.o ctmixer.o ctresource.o \
/linux-6.12.1/Documentation/devicetree/bindings/net/
Dfsl,fman-dtsec.yaml109 reference will be assumed to be for "xfi". Otherwise, if pcs-handle-names is
119 - xfi
Dapm-xgene-mdio.txt6 - compatible: Must be "apm,xgene-mdio-rgmii" or "apm,xgene-mdio-xfi"
Dapm-xgene-enet.txt10 - "apm,xgene1-xgenet": XFI based 10G interface
/linux-6.12.1/arch/powerpc/boot/dts/fsl/
Dqoriq-fman3-0-10g-3.dtsi31 pcs-handle-names = "sgmii", "xfi";
Dqoriq-fman3-0-10g-2.dtsi31 pcs-handle-names = "sgmii", "xfi";
Dqoriq-fman3-0-10g-1.dtsi56 pcs-handle-names = "sgmii", "qsgmii", "xfi";
Dqoriq-fman3-1-10g-1.dtsi56 pcs-handle-names = "sgmii", "qsgmii", "xfi";
Dqoriq-fman3-1-10g-0.dtsi56 pcs-handle-names = "sgmii", "qsgmii", "xfi";
Dqoriq-fman3-0-10g-0.dtsi56 pcs-handle-names = "sgmii", "qsgmii", "xfi";
/linux-6.12.1/arch/arm64/boot/dts/freescale/
Dfsl-ls1046-post.dtsi58 pcs-handle-names = "sgmii", "qsgmii", "xfi";
/linux-6.12.1/drivers/net/mdio/
Dmdio-xgene.c309 .compatible = "apm,xgene-mdio-xfi",
386 "xgene-mii-xfi"); in xgene_mdio_probe()
/linux-6.12.1/drivers/net/ethernet/freescale/dpaa2/
Ddpmac.h47 * @DPMAC_ETH_IF_XFI: XFI interface
/linux-6.12.1/Documentation/networking/
Dphy.rst286 Note: 10GBASE-R is just one protocol that can be used with XFI and SFI.
287 XFI and SFI permit multiple protocols over a single SERDES lane, and
290 XFI and SFI are not PHY interface types in their own right.

12