STRUCT MTK_PCIE_PHY_DATA(9)
π 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 anint, it's the count, she's booked and busy πsw_efuse_supportedβ aboolthat 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_supportedis abool, 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms