devm_of_qcom_ice_get(9)

💅 devm_of_qcom_ice_get(9)

okay so bestie, welcome to the Kernel API Manual — this one lives in the kernel world and it's genuinely so useful once you get it. Let's go ✨

---

🌸 NAME

devm_of_qcom_ice_get — the devres-managed helper that grabs you an ICE instance straight from a DT node. no cap, that's the whole vibe 🎀

---

✨ SYNOPSIS

struct qcom_ice * devm_of_qcom_ice_get (struct device *dev );

---

🦋 ARGUMENTS

• dev — the device pointer for the consumer device. like, the one that's asking for the ICE instance 💖

---

🔥 DESCRIPTION

so here's the tea ☕ — this function hands you an ICE instance, but there are two whole paths it can take, and honestly both are iconic:

• if the consumer device's DT node provides the 'ice' reg range and the 'ice' clock (that's the legacy DT style, iykyk), the function creates an ICE instance for that consumer device 🫶
• on the other hand, if the consumer provides a phandle via the 'qcom,ice' property pointing at an ICE DT, then the ICE instance is already created — so this function just returns that one instead 💅

either way you get an instance, you just gotta know which lane you're in.

---

⭐ RETURN

ICE pointer on success, ERR_PTR on error. that's it, that's the deal 🙈

---

🌈 SEE ALSO

Kernel file ./drivers/soc/qcom/ice.c, plus the whole squad:

• qcom_ice_get_supported_key_type(9)
• qcom_ice_derive_sw_secret(9)
• qcom_ice_generate_key(9)
• qcom_ice_prepare_key(9)
• qcom_ice_import_key(9)
• of_qcom_ice_get(9)

---

mwah 💜 this page is from ./drivers/soc/qcom, dated October 2026, and it's the devm_of_qcom_ice_get(9) manual page — go forth and get those ICE instances bestie, you got this 🎀✨