sh_early_pla...driver_probe(9)

💅 NAME 💅

ok so bestie, welcome to the sh_early_platform_driver_probe page ✨ — this is the Kernel API Manual, and this function? it probes a whole class of registered drivers. slay. 🎀

---

🌸 SYNOPSIS 🌸

int sh_early_platform_driver_probe (char *class_str , int nr_probe , int
       user_only );

like literally that's the whole signature, no cap, it returns an int 🫶

---

✨ ARGUMENTS ✨

• class_str — a string that identifies the early platform driver class you're after 🏷️ like, this is how you say "yeah that class, that one"
• nr_probe — how many platform devices you wanna successfully probe before it dips out and exits 👋 so it's the count of successful probes, and then it's done
• user_only — only probe the early platform devices that the user specified 🙈 so it narrows the whole thing down to just the user's picks

---

🦋 DESCRIPTION 🦋

so the architecture code is the one calling this, and what it does is probe the registered early platform drivers inside a certain class 💫 that's the whole vibe.

but here's the thing bestie, it doesn't just happen for free — for a probe to actually go down, you need a registered early platform device that matches a registered early platform driver. matching pair or it's giving nothing. 🤝

ngl this is a "both sides gotta show up" situation — no matching device, no matching driver, no probe. periodt. 💀

---

👑 SEE ALSO 👑

the kernel file itself, iconic source material:

• ./arch/sh/drivers/platform_early.c

and the whole friend group of related calls, all fr fr worth a read:

• sh_early_platform_driver_register(9)
• sh_early_platform_add_devices(9)
• sh_early_platform_driver_register_all(9)
• sh_early_platform_match(9)
• sh_early_platform_left(9)
• sh_early_platform_driver_probe_id(9)
• early_platform_cleanup(9)

---

and that's the page!! 🌈 source lives in ./arch/sh/drivers, dated October 2026 — mwah, go probe something cute 💖✨🧚‍♀️