device_reprobe(9)

✨ NAME ✨

okay bestie, meet device_reprobe from the Kernel API Manual — it’s literally the “remove driver for a device and probe for a new driver” function. glow-up energy for device drivers, no cap 💅

🦋 SYNOPSIS 🦋

int device_reprobe (struct device *dev );

🎀 ARGUMENTS 🎀

• dev — the device to reprobe. that’s the main character getting the driver situation re-checked 💖

🌸 DESCRIPTION 🌸

so here’s the tea: this function detaches the attached driver (if any) for the given device and restarts the driver probing process. it is intended to use if probing criteria changed during a devices lifetime and driver attachment should change accordingly. translation: if the probing criteria shifted while the device was living its life, and the driver attachment should change to match, this is the function doing that work 🔥

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/bus.c, plus the whole squad:

• bus_to_subsys(9)
• bus_for_each_dev(9)
• bus_find_device(9)
• bus_for_each_drv(9)
• bus_add_device(9)
• bus_probe_device(9)
• bus_remove_device(9)
• bus_add_driver(9)
• bus_remove_driver(9)
• bus_rescan_devices(9)
• bus_register(9)
• bus_unregister(9)
• subsys_dev_iter_init(9)
• subsys_dev_iter_next(9)
• subsys_dev_iter_exit(9)
• subsys_system_register(9)
• subsys_virtual_register(9)
• driver_find(9)
• bus_get_dev_root(9)

source: ./drivers/base · date: October 2026 · page: device_reprobe(9) · Kernel API Manual signing off, periodt 🫶✨