pci_bridge_d3_possible(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

pci_bridge_d3_possible β€” so like… can we actually yeet this bridge into D3 or not? that's the whole vibe check πŸ’…

(this one lives in the Kernel API Manual, bestie β€” kernel-internal lore 🧚)


πŸ¦‹ SYNOPSIS πŸ¦‹

bool pci_bridge_d3_possible (struct pci_dev *bridge );

🌸 ARGUMENTS 🌸

  • bridge β€” the bridge you're side-eyeing. that's it, that's the argument πŸŽ€

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the deal: right now we only allow D3 for some PCIe ports and for Thunderbolt. that's the entire guest list, no plus-ones πŸ™ˆ

the return value is guaranteed to be constant across the entire lifetime of the bridge β€” including its hot-removal. like, the answer will not switch up on you mid-relationship, not even when the bridge gets yanked out of the machine. iconic commitment honestly πŸ‘‘


πŸ”₯ RETURN πŸ”₯

returns a bool telling you whether it's possible to move the bridge to D3. yes/no, that's the tea ⭐


🌈 SEE ALSO 🌈

kernel file ./drivers/pci/pci.c β€” and here's the whole extended friend group, no cap:


okay that's the whole page, hope it slayed for you 🫢 this one came out of ./drivers/pci in the October 2026 release of the Kernel API Manual πŸ’–βœ¨ go forth and check your bridges, bestie πŸ’…

πŸ“¦ where this page comes from