pm8001_get_i...phy_settings(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pm8001_get_internal_phy_settings(9) β€” from the Kernel API Manual, bestie ✨

okay so picture this: we're deep in the kernel, right, in the Kernel API Manual, and there's this lil function called pm8001_get_internal_phy_settings and it is literally the moment your adapter's internal PHY settings get scooped up. no cap. πŸ¦‹


✨ NAME ✨

pm8001_get_internal_phy_settings β€” the one that retrieves the internal PHY settings. that's it, that's the vibe. πŸŽ€


🌸 SYNOPSIS 🌸

void pm8001_get_internal_phy_settings (struct pm8001_hba_info *pm8001_ha
, struct pm8001_mpi3_phy_pg_trx_config *phycfg );

returns void β€” no value back, she just does the thing and dips πŸ’…


🫢 ARGUMENTS 🫢

  • pm8001_ha β€” our adapter πŸ’– like, ours, the one we're working with, the main character of this whole operation
  • phycfg β€” the PHY config page to populate ✨ she comes in empty-ish and leaves with the settings, that's her glow-up arc

πŸ”₯ SEE ALSO πŸ”₯

the whole squad, fr fr β€” they're all in the kernel file ./drivers/scsi/pm8001/pm8001_init.c and honestly they're all icons:

go read them too bestie, they're giving supporting cast but honestly some of them are lowkey the leads 😭

that's the whole page, she's short and sweet β€” sourced from ./drivers/scsi/pm8001, dated October 2026, header pm8001_get_i...phy_settings(9) and all πŸ§šπŸ’œ stay slay, go populate that PHY config page πŸ’–βœ¨

πŸ“¦ where this page comes from