pci_cfg_access_trylock(9)

✨ pci_cfg_access_trylock(9) ✨

okay bestie, welcome to the pci_cfg_access_trylock(9) page from the Kernel API Manual — this one's short and sweet and honestly kind of a vibe 🎀

---

💖 NAME 💖

pci_cfg_access_trylock — the "try" version of locking PCI config reads/writes. like, she attempts. she does not wait. 💅

---

🌸 SYNOPSIS 🌸

bool pci_cfg_access_trylock (struct pci_dev *dev );

---

🦋 ARGUMENTS 🦋

• dev — the pci device struct 🫶 this is your pci device, the one you're trying to get at

---

⭐ DESCRIPTION ⭐

okay so literally, pci_cfg_access_trylock does the same thing as pci_cfg_access_lock — no cap — but with a twist: it returns 0 if access is already locked, and 1 otherwise. that's it. that's the whole personality 🧚

the glowing part? this function can be used from atomic contexts 🔥 which is genuinely iconic of her, because regular lock-waiting is a big nope in atomic context.

lowkey the whole point: she tries, she tells you yes or no, she never blocks. if she says 0, don't just stand there — that access is taken, bestie 😭

---

💜 SEE ALSO 💜

• Kernel file ./drivers/pci/access.c — the source, go read her
• pci_bus_set_ops(9)
• pci_cfg_access_lock(9)
• pci_cfg_access_unlock(9)

those last two are her siblings — the lock and the unlock — and honestly you should know all three, iykyk 🌈

---

anyway that's the page 💖 it lives over in ./drivers/pci, dated October 2026, and yes the manual is literally called pci_cfg_access_trylock(9) so we came full circle, periodt 👑✨