platform_profile_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– platform_profile_register(9) β€” Kernel API Manual, but make it bestie πŸ’–

🌸 NAME 🌸

platform_profile_register β€” creates and registers a platform profile class device. That’s the whole assignment, and it lowkey slays πŸ’…βœ¨

✨ SYNOPSIS ✨

okay so here’s the exact signature, bestie β€” character-for-character, no cap:

struct device * platform_profile_register (struct device *dev , const char *name , void *drvdata , const struct platform_profile_ops *ops );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” parent device 🫢
  • name β€” name of the class device 🏷️
  • drvdata β€” driver data that will be attached to the class device πŸ”—
  • ops β€” platform profile’s mandatory operations (mandatory, bestie πŸ’€)

🌈 RETURN 🌈

On success you get a pointer to the new class device ✨; on failure you get ERR_PTR 😭. That’s the whole return vibe β€” pointer or ERR_PTR, periodt.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/acpi/platform_profile.c β€” here’s the whole squad, iykyk:


source/version check: this page lives under ./drivers/acpi, it’s dated October 2026, and the page is platform_profile_register(9) β€” mwah, bye bestie πŸ«ΆπŸ’‹

πŸ“¦ where this page comes from