STRUCT CYGNUS_PCIE_PHY_CORE(9)
π STRUCT CYGNUS_PCIE_PHY_CORE(9) π
okay so bestie, welcome to the kernel API manual for struct cygnus_pcie_phy_core β literally the core control situation for the Cygnus PCIe PHY β¨. yes this is section 9, yes it's kernel API, yes we're doing this. pull up a chair π
πΈ NAME πΈ
struct cygnus_pcie_phy_core β Cygnus PCIe PHY core control. that's it, that's the vibe. it's the main character struct holding the whole PHY core together π
β¨ SYNOPSIS β¨
okay so here's the whole struct laid out, exactly as it lives:
struct cygnus_pcie_phy_core {
struct device *dev;
void __iomem *base;
struct mutex lock;
struct cygnus_pcie_phy phys[MAX_NUM_PHYS];
};
like, look at her. four members, one lock, an array of PHYs β she's giving organized and secure π no cap, that mutex is doing serious work.
π¦ Members π¦
devβ pointer to device π the actual device this whole thing belongs to.baseβ base register π₯ yourvoid __iomem *era. this is where the registers start, periodt.lockβ mutex to protect access to individual PHYs π like, access to individual PHYs is guarded by this mutex, and that's genuinely important, don't skip her.physβ pointer to Cygnus PHY device π§ the array ofstruct cygnus_pcie_phy, sizedMAX_NUM_PHYS. there can be more than one PHY bestie, they're not a solo act.
π SEE ALSO π
- Kernel file
./drivers/phy/broadcom/phy-bcm-cygnus-pcie.cπ β go read the source, iykyk struct cygnus_pcie_phy(9)β the sibling manpage, go give her a visit π«Ά
ok one gentle reminder bestie: this is literally just the struct layout, so don't go inventing behaviour that isn't here β what you see is what you get π
and that's the page!! π comes to you from ./drivers/phy/broadcom, dated October 2026, and it's struct cygnus_pcie_phy_core(9) all the way down πΈ slay, go read the kernel source, ily, bye πβ¨
π¦ 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