gaokun_ec_register_notify(9)

✨ NAME ✨

okay so bestie, welcome to gaokun_ec_register_notify(9) — the Kernel API Manual page for this lil EC-notify registration moment. It’s giving “register a notifier callback for EC events,” and the vibe check is simple: hand over the right struct and the right notifier block, and you’re slaying. 💅

gaokun_ec_register_notify — register a notifier callback for EC events. 🦋 no cap, literally what it says on the tin.

---

🌸 SYNOPSIS 🌸

Here’s the exact summoning circle, bestie — copy it character for character:

int gaokun_ec_register_notify (struct gaokun_ec *ec , struct
notifier_block *nb );

The way that signature is formatted is iconic — keep the spacing and line break fr fr. ✨

---

🎀 ARGUMENTS 🎀

These are the two besties you gotta pass in:

• ec — The gaokun_ec structure. That’s the EC main character right there. 👑
• nb — Notifier block pointer to register. Hand over the pointer, let it register, periodt. 💖

---

💫 RETURN 💫

0 on success or negative error code. That’s it. No mysterious side-quest vibes — just the classic kernel return situation. ✨

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/platform/arm64/huawei-gaokun-ec.c — the source file, iykyk. 📁

Then the whole bestie lineup:

• gaokun_ec_read(9)
• gaokun_ec_write(9)
• gaokun_ec_unregister_notify(9)
• gaokun_ec_psy_multi_read(9)
• gaokun_ec_psy_get_smart_charge(9)
• gaokun_ec_psy_set_smart_charge(9)
• gaokun_ec_psy_get_smart_charge_enable(9)
• gaokun_ec_psy_set_smart_charge_enable(9)
• gaokun_ec_ucsi_read(9)
• gaokun_ec_ucsi_write(9)
• gaokun_ec_ucsi_get_reg(9)
• gaokun_ec_ucsi_pan_ack(9)

---

and that’s the whole page, bestie. 🫶 This one lives under ./drivers/platform/arm64, and the date on it is October 2026. Go forth and register those notifiers responsibly. 💜