dprc_scan_objects(9)

💅 dprc_scan_objects(9) 💅

okay bestie, this page is from the Kernel API Manual and it's giving "the bus driver does a little object sweep" energy. we are keeping every detail, no cap. periodt.

✨ NAME ✨

dprc_scan_objects — literally discovers objects in a DPRC. yes bestie, that's the whole name vibe.

🌸 SYNOPSIS 🌸

int dprc_scan_objects (struct fsl_mc_device *mc_bus_dev , bool alloc_interrupts );

🎀 ARGUMENTS 🎀

• mc_bus_dev — a pointer to the fsl-mc device that represents a DPRC object. it's the "who are we scanning" bestie.
• alloc_interrupts — if true, the function allocates the interrupt pool; otherwise the interrupt allocation is delayed. so this one is lowkey the "handle interrupts now or later" switch, iykyk.

🦋 DESCRIPTION 🦋

okay so picture this: dprc_scan_objects detects objects added to and removed from a DPRC, and it synchronizes the state of the Linux bus driver, MC by adding and removing devices accordingly. it's literally keeping the device roster updated, bestie. main character energy.

A DPRC can have two types of devices:

• allocatable objects — for example dpbp, dpmcp
• non-allocatable devices — for example dprc, dpni

Here's the important ordering tea: all allocatable devices needed to be probed before all non-allocatable devices, to ensure that device drivers for non-allocatable devices can allocate any type of allocatable devices. that is, we need to ensure that the corresponding resource pools are populated before they can get allocation requests from probe callbacks of the device drivers for the non-allocatable devices. the way that ordering matters is so real. ngl, it ate.

🌈 SEE ALSO 🌈

Kernel file ./drivers/bus/fsl-mc/dprc-driver.c, plus the whole squad:

• dprc_remove_devices(9)
• check_plugged_state_change(9)
• dprc_add_new_devices(9)
• dprc_scan_container(9)
• dprc_irq0_handler_thread(9)
• dprc_setup(9)
• dprc_probe(9)
• dprc_cleanup(9)
• dprc_remove(9)

that's the whole sweep, bestie 💖 source/version: ./drivers/bus/fsl-mc • date: October 2026 — mwah 🫶✨