sh_early_pl..._add_devices(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– sh_early_platform_add_devices πŸ’–

okay so bestie, welcome to the Kernel API Manual, section 9 β€” yes we're in the big-kid kernel docs now, and this one is literally about registering early platform devices before the rest of the world wakes up. slay.


✨ NAME ✨

sh_early_platform_add_devices β€” adds a number of early platform devices

like, it adds several of them at once. not one. a whole little squad. 🫢


🌸 SYNOPSIS 🌸

void sh_early_platform_add_devices (struct platform_device **devs , int
num );

that's the whole vibe check right there, no cap.


πŸŽ€ ARGUMENTS πŸŽ€

  • devs β€” array of early platform devices to add. it's a struct platform_device **, so it's a pointer-to-pointer situation, she's fancy like that πŸ’…
  • num β€” number of early platform devices in array. an int. literally just how many of them you're handing over.
fr fr: devs is an array, not one device. don't be out here passing a single pointer and hoping for the best 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

Used by early architecture code to register early platform devices and their platform data.

that's it, that's the tea. the early arch code calls this so the kernel knows about these devices early (the name was a hint, iykyk), and it scoops up their platform data right along with them. main character energy for the sh architecture's early boot era ✨


πŸ”₯ SEE ALSO πŸ”₯

the whole early-platform friend group, honestly. they all show up together πŸ‘‘


πŸ’œ the sign-off πŸ’œ

this page lives in ./arch/sh/drivers, it's from October 2026, and it's part of the Kernel API Manual, section 9. periodt. πŸŽ€βœ¨

k byeeee, go register some devices early πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from