pci_scan_child_bus_extend(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pci_scan_child_bus_extend β€” like, the Linux Kernel API Manual page for it, bestie πŸŽ€

okay so real talk, this is pci_scan_child_bus_extend(9) from the Kernel API Manual, and it's genuinely one of those functions that sounds scary but is actually just "go look at everything under this bus, and also plan ahead for hotplug." we love a forward-thinking icon ✨


✨ NAME ✨

pci_scan_child_bus_extend β€” scan devices below a bus πŸ¦‹


🌸 SYNOPSIS 🌸

unsigned int pci_scan_child_bus_extend (struct pci_bus *bus , unsigned
       int available_buses );

like, that's the whole signature, no cap πŸ’…


πŸ’– ARGUMENTS πŸ’–

  • bus β€” the bus you're scanning for devices. that's the main character right there πŸ‘‘
  • available_buses β€” the total number of buses you've got available. and btw, 0 means it does not try to extend beyond the minimal. so if you pass 0, it stays in its lane, respectfully πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

so what it does: it scans devices below bus, including the subordinate buses. then it returns the new subordinate number, which includes all the devices it found. literally just hands you back the updated count, periodt ✨

and here's the slay part β€” passing available_buses causes the remaining bus space to be distributed equally between hotplug-capable bridges, so the hierarchy can be extended later. it's giving "planning for your future self" energy and honestly? obsessed 🫢


🌈 SEE ALSO 🌈

kernel file ./drivers/pci/probe.c β€” and the whole squad of related pages:

every single one of them, no skips, iykyk πŸ’€πŸ’œ


okay bye bestie, that's the whole page β€” brought to you by ./drivers/pci, dated October 2026, from the Kernel API Manual set. go scan some buses, you've got this πŸ§šβ€β™€οΈπŸ’–β­

πŸ“¦ where this page comes from