pcie_walk_rcec(9)

💖 pcie_walk_rcec(9) 💖

okay so bestie, welcome to the Kernel API Manual — today's main character is pcie_walk_rcec(9) and honestly? she's a little recursive road-trip through your RCiEP devices. buckle up 🎀

---

✨ NAME ✨

pcie_walk_rcec — walk RCiEP devices associating with RCEC and call callback.

like, literally that. walk the devices, call the callback. no cap. 🦋

---

🌸 SYNOPSIS 🌸

void pcie_walk_rcec (struct pci_dev *rcec , int (*cb)(struct pci_dev *,
                     void *) , void *userdata );

yes she takes a function pointer, yes that's iconic, yes you're gonna need to actually read the args 👑

---

💅 ARGUMENTS 💅

• rcec — the RCEC whose RCiEP devices should be walked. she's the one holding the map 🗺️
• cb — callback to be called for each RCiEP device found. one call per device, no skipping, fr fr 💖
• userdata — arbitrary pointer to be passed to callback. literally whatever you want, she won't judge 🫶

---

🧚 DESCRIPTION 🧚

Walk the given RCEC. Call the callback on each RCiEP found. that's the whole vibe ✨

If cb returns anything other than 0, break out. that's your escape hatch, use it wisely 💀

ngl, "anything other than 0" means anything — that's your bail signal, bestie. don't sleep on it.

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/pci/pcie/rcec.c
• pcie_link_rcec(9)

go read the source, it's giving "the real documentation was the code we read along the way" 😭💜

---

and that's the whole page, periodt 🌈 — brought to you by the fine folks over in ./drivers/pci/pcie, dated October 2026, straight from the Kernel API Manual. mwah, ily, go walk some devices 💅🎀⭐