driver_find(9)

💖 driver_find(9) 💖

okay bestie, this page comes straight from the Kernel API Manual, and it's giving “find that driver by name on a bus” energy. no cap, it's a small routine with a big safety warning at the end. 🫶

🌸 NAME 🌸

driver_find — locate driver on a bus by its name. literally the whole mission, periodt. 💅

✨ SYNOPSIS ✨

struct device_driver * driver_find (const char *name , const struct
       bus_type *bus );

🎀 ARGUMENTS 🎀

• name — name of the driver. yep, the string you're hunting for. 🔎
• bus — bus to scan for the driver. this is the bus you're searching, bestie. 🚌

🦋 DESCRIPTION 🦋

okay so driver_find calls kset_find_obj to iterate over the list of drivers on a bus and find the driver by name. if it finds it, it returns the driver. simple, iconic, ate. ✨

⚠️ safety check, bestie: this routine provides no locking to prevent the driver it returns from being unregistered or unloaded while the caller is using it. the caller is responsible for preventing this. that's not a vibe you can ignore — protect that driver yourself, fr fr. 😭

🔥 SEE ALSO 🔥

• Kernel file ./drivers/base/bus.c
• 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)
• device_reprobe(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)
• bus_get_dev_root(9)

and that's the page, bestie! source/version spot: ./drivers/base · date: October 2026 · from the Kernel API Manual. mwah 💋✨