mtk_xfi_tphy_probe(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ mtk_xfi_tphy_probe(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… today we're looking at mtk_xfi_tphy_probe β€” the little probe function that sets up your XFI T-PHY instance from Device Tree. it's giving "first day of school, gotta meet everybody" energy fr fr πŸŽ€


🌸 NAME 🌸

mtk_xfi_tphy_probe β€” probe the phy instance from Device Tree. yes that's the whole vibe. she finds out what she needs to know about the hardware and gets set up. πŸ¦‹


✨ SYNOPSIS ✨

int mtk_xfi_tphy_probe (struct platform_device *pdev );

πŸ’– ARGUMENTS πŸ’–

  • pdev β€” the matching platform device. that's her buddy, her plus-one, the device she's probing 🫢

🌈 DESCRIPTION 🌈

so like, the probe function literally goes to the Device Tree and gets all the essentials: the IO resource, the clocks, the reset controller, and whether the DA work-around for 10GBase-R is required. 🧚

then she allocates memory to hold all that info in a struct mtk_xfi_tphy. iconic. she has a whole little organizer for her data and honestly? we love to see it πŸ’œ


πŸ”₯ RETURN πŸ”₯

  • 0 β€” OK, we slayed, everything's good πŸ‘‘
  • -ENODEV β€” missing associated Device Tree node. and like… that should never happen πŸ™ˆ key word should, bestie
  • -ENOMEM β€” out of memory. πŸ’€ tragic, but she's honest about it
  • any error value which devm_platform_ioremap_resource, devm_clk_bulk_get, devm_reset_control_get_exclusive, devm_phy_create or devm_of_phy_provider_register may return. yeah any of them. they all got a say 😭

πŸ¦‹ SEE ALSO πŸ¦‹

go read those too, iykyk πŸ“šβœ¨


ok that's the whole page bestie, no cap. go forth and probe responsibly πŸ’…πŸŒΈ

✿ with love from ./drivers/phy/mediatek, October 2026, Kernel API Manual ✿ πŸ“β­πŸ’–

πŸ“¦ where this page comes from