scmi_handle_get(9)

💅 scmi_handle_get — bestie, let's get that handle ✨

Okay so real talk, this is a kernel API manual page for scmi_handle_get. It's giving "I need my SCMI handle and I need it now" energy, and honestly? We love that for you. Let's get into it.

---

🌸 SYNOPSIS 🌸

struct scmi_handle * scmi_handle_get (struct device *dev );

Like, you call it with a device pointer and it hands you back a struct scmi_handle *. Simple slay. 🫶

---

🎀 ARGUMENTS 🎀

• dev — pointer to the device for which we want the SCMI handle. That's it, that's the whole vibe. You point at a device, you get a handle. 🔥

---

⚠️ NOTE (read this bestie, fr fr) ⚠️

The function does not track individual clients of the framework, and it is expected to be maintained by the caller of the SCMI protocol library. Translating that from corporate: it's not keeping tabs on who's using it, so YOU gotta keep track, okay? 👑

scmi_handle_put must be balanced with a successful scmi_handle_get. This is non-negotiable. Like, if you get a handle and don't put it back, that's giving memory leak main character energy and we are NOT here for it. Every get needs its put. Periodt. 💀

---

👑 RETURN 👑

• Pointer to the handle if it's successful — slay, iconic, we love to see it ✨
• NULL on error — it's giving "it's not me, it's you" and you gotta handle that gracefully 😭

---

🦋 SEE ALSO 🦋

Okay so this list is long but honestly every single one of these is a baddie in their own right. Respect the whole squad. 💜

• Kernel file ./drivers/firmware/arm_scmi/driver.c
• struct scmi_xfers_info(9)
• struct scmi_protocol_instance(9)
• struct scmi_info(9)
• scmi_create_protocol_devices(9)
• scmi_xfer_token_set(9)
• scmi_xfer_token_clear(9)
• scmi_xfer_inflight_register_unlocked(9)
• scmi_xfer_inflight_register(9)
• scmi_xfer_raw_inflight_register(9)
• scmi_xfer_pending_set(9)
• scmi_xfer_get(9)
• scmi_xfer_raw_get(9)
• scmi_xfer_raw_channel_get(9)
• __scmi_xfer_put(9)
• scmi_xfer_raw_put(9)
• scmi_xfer_lookup_unlocked(9)
• scmi_bad_message_trace(9)
• scmi_msg_response_validate(9)
• scmi_xfer_state_update(9)
• scmi_xfer_command_acquire(9)
• scmi_rx_callback(9)
• xfer_put(9)
• scmi_wait_for_message_response(9)
• scmi_xfer_raw_wait_for_message_response(9)
• do_xfer(9)
• do_xfer_with_response(9)
• xfer_get_init(9)
• version_get(9)
• scmi_set_protocol_priv(9)
• scmi_get_protocol_priv(9)
• scmi_common_extended_name_get(9)
• scmi_common_get_max_msg_size(9)
• scmi_protocol_msg_check(9)
• struct scmi_iterator(9)
• scmi_revision_area_get(9)
• scmi_protocol_version_negotiate(9)
• scmi_protocol_version_initialize(9)
• scmi_alloc_init_protocol_instance(9)
• scmi_get_protocol_instance(9)
• scmi_protocol_acquire(9)
• scmi_protocol_release(9)
• scmi_devm_protocol_get(9)
• scmi_devm_protocol_acquire(9)
• scmi_devm_protocol_put(9)
• scmi_is_transport_atomic(9)
• scmi_handle_put(9)
• scmi_channels_setup(9)

Like I said. Whole squad. No cap. 🌈

---

Anyway bestie, that's the whole manual. Go forth and handle responsibly. Don't forget the put. I'm literally begging you. 🙈

Source: ./drivers/firmware/arm_scmi · Date: October 2026 · Title: scmi_handle_get(9) — mwah, love u, bye! 💖✨🎀