STRUCT MTK_PCIE_PHY_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct mtk_pcie_phy_data β€” okay bestie, this is the per-SoC phy data situation. Like, every SoC gets its own little bundle of facts and this struct is the carrier pigeon πŸ•ŠοΈ


πŸŽ€ SYNOPSIS πŸŽ€

Here's the whole entire vibe, no notes:

struct mtk_pcie_phy_data {
    int num_lanes;
    bool sw_efuse_supported;
 };

That's it. That's the struct. Two fields. Lowkey iconic for how unbothered it is πŸ’…


✨ MEMBERS ✨

Let's do a little meet-and-greet with the fields, because they deserve it 🫢

  • num_lanes β€” the supported lane numbers, aka how many lanes this SoC is out here serving. It's an int, it's the count, she's booked and busy 🌈
  • sw_efuse_supported β€” a bool that says whether software is allowed to load eFuse data. Support software to load eFuse data β€” that's the whole job, and honestly? Slay πŸŽ€
Heads up bestie: sw_efuse_supported is a bool, so it's a yes/no situation, not a maybe. Don't be out here putting unsupported values in there πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

Go read the source, it's literally right there and it ate:

  • Kernel file ./drivers/phy/mediatek/phy-mtk-pcie.c
  • struct mtk_pcie_lane_efuse(9)
  • struct mtk_pcie_phy(9)
  • mtk_pcie_phy_init(9)

And that's the whole page, bestie! πŸ’œ This lil masterpiece lives under ./drivers/phy/mediatek, it's dated October 2026, it's from the Kernel API Manual, and it's filed as struct mtk_pcie_phy_data(9). Periodt. πŸ‘‘

πŸ“¦ where this page comes from