dprc_remove_devices(9)
π dprc_remove_devices(9) β like, the Kernel API Manual one π
okay so bestie, welcome to page dprc_remove_devices(9) of the Kernel API Manual β¨ this is the whole vibe, let's go π¦
πΈ NAME πΈ
dprc_remove_devices β removes devices for objects that got yeeted out of a DPRC πβ¨
β SYNOPSIS β
void dprc_remove_devices (struct fsl_mc_device *mc_bus_dev , struct
fsl_mc_obj_desc *obj_desc_array , int num_child_objects_in_mc );
(no cap, that weird space before the commas is literally how it's written, we do not touch it π)
π§ ARGUMENTS π§
mc_bus_devβ a pointer to thefsl-mcdevice that represents a DPRC object π«Ά like, this is the main character of the call.obj_desc_arrayβ the array of object descriptors for the child objects that are currently present in the DPRC in the MC πnum_child_objects_in_mcβ the number of entries inobj_desc_array, i.e. how many of the above you're actually handing over π
π DESCRIPTION π
So here's the tea β: this function synchronizes the state of the Linux bus driver with the actual state of the MC π it does that by removing the devices that represent MC objects which have been dynamically removed in the physical DPRC.
tl;dr β the MC was like "these objects? gone." and this function is what makes the Linux side agree β¨ lowkey iconic behaviour, ngl π
π¦ SEE ALSO π¦
- Kernel file
./drivers/bus/fsl-mc/dprc-driver.cπ check_plugged_state_change(9)dprc_add_new_devices(9)dprc_scan_objects(9)dprc_scan_container(9)dprc_irq0_handler_thread(9)dprc_setup(9)dprc_probe(9)dprc_cleanup(9)dprc_remove(9)
all of them slay in their own way, go read them π«Άπ
ngl this whole page lives under ./drivers/bus/fsl-mc and it's dated October 2026, so like, mark your calendars bestie π
π that's the sign-off, mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms