driver_defe..._check_state(9)

✨ driver_deferred_probe_check_state(9) ✨

okay bestie, welcome to the Kernel API Manual — this is the page for driver_deferred_probe_check_state, and honestly it's a little icon of a function 🎀

🌸 NAME 🌸

driver_deferred_probe_check_state — check the deferred probe state, that's literally the whole vibe 💅

🦋 SYNOPSIS 🦋

int driver_deferred_probe_check_state (struct device *dev );

🌈 ARGUMENTS 🌈

• dev — the device you wanna check 👀 that's it, that's the argument

⭐ RETURN ⭐

so here's what you might get back, pay attention fr fr:

• -ENODEV — if initcalls have completed and modules are disabled 🚫
• -ETIMEDOUT — if the deferred probe timeout was set and has expired and modules are enabled ⏰😭
• -EPROBE_DEFER — in other cases, i.e. the classic "not yet bestie, try again later" 🫶

💜 DESCRIPTION 💜

so drivers or subsystems can opt-in to calling this function instead of directly returning -EPROBE_DEFER. that's the whole tea ☕ — you're swapping the raw "defer me" return for this little wrapper that actually checks the state first. no cap, it's giving "let me consult the vibes before I commit" energy ✨

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/dd.c plus the whole friend group 🫂 — driver_deferred_probe_trigger(9), device_block_probing(9), device_unblock_probing(9), device_set_deferred_probe_reason(9), deferred_probe_initcall(9), device_is_bound(9), device_bind_driver(9), driver_probe_done(9), wait_for_device_probe(9), driver_probe_device(9), device_attach(9), device_driver_attach(9), driver_attach(9), device_release_driver(9), device_driver_detach(9), driver_detach(9) 👑

ok that's the page!! go forth and probe responsibly, bestie 💖

and finally, the cute lil sign-off: this one lives in ./drivers/base, it's from October 2026, and yeah — that's the whole manual page, periodt 💅🎀🦋