spmi_controller_alloc(9)

💖 NAME 💖

Okay so this is the page for spmi_controller_alloc(9) from the Kernel API Manual — and it does exactly what the name says, bestie: Allocate a new SPMI controller. Slay. ✨

🦋 SYNOPSIS 🦋

struct spmi_controller * spmi_controller_alloc (struct device *parent ,
       size_t size );

🎀 ARGUMENTS 🎀

• parent — parent device. That’s the parent-device vibe you’re handing in. 💅
• size — size of private data. Yep, literally the size of the private data. 🫶

🌸 DESCRIPTION 🌸

Caller responsibility check, bestie: you are responsible for either calling spmi_controller_add to add the newly allocated controller, or calling spmi_controller_put to discard it. No cap. 😭

And the allocated private data region? You may access it via spmi_controller_get_drvdata. That’s the whole access situation. Iconic. 👑

👀 SEE ALSO 👀

Kernel file ./drivers/spmi/spmi.c — plus these cuties:

• spmi_device_add(9)
• spmi_device_remove(9)
• spmi_register_read(9)
• spmi_ext_register_read(9)
• spmi_ext_register_readl(9)
• spmi_register_write(9)
• spmi_register_zero_write(9)
• spmi_ext_register_write(9)
• spmi_ext_register_writel(9)
• spmi_command_reset(9)
• spmi_command_sleep(9)
• spmi_command_wakeup(9)
• spmi_command_shutdown(9)
• spmi_find_device_by_of_node(9)
• spmi_device_alloc(9)
• spmi_controller_add(9)
• spmi_controller_remove(9)
• __spmi_driver_register(9)

okay that’s the page, bestie 🫶 — it came from the Kernel API Manual, source ./drivers/spmi, dated October 2026. bye 💅✨