kbbl_init(9)

💖 kbbl_init(9) — Kernel API Manual 💖

okay so bestie, welcome to kbbl_init, straight out of the Kernel API Manual. this is the lil function that gets your keyboard backlight out of bed and into a known state. it's literally giving "let there be light" but make it firmware. ✨

---

🌸 NAME 🌸

kbbl_init — Initialize the state of the keyboard backlight. that's it, that's the whole job. 💅

---

🎀 SYNOPSIS 🎀

int kbbl_init (struct wilco_ec_device *ec );

yes queen, that's the whole signature. copy it exactly, spaces and all, don't come for me. 🫶

---

🦋 ARGUMENTS 🦋

• ec — the EC device to talk to. this is your main character, the embedded controller you're having the convo with. no ec, no vibes. 💜

---

✨ DESCRIPTION ✨

okay so here's the tea. kbbl_init goes and gets the current brightness, but it's not just gonna trust whatever state it finds — it's making sure the BIOS already initialized the backlight into PWM mode first. like, ground rules. 🌈

and if the backlight is not in PWM mode? then the current brightness reading is meaningless — total lies, a whole nothingburger, not me energy — so the function sets the brightness to WILCO_KBBL_DEFAULT_BRIGHTNESS instead. basically: no valid reading, no problem, we default. periodt. 🍓

---

🔥 RETURN 🔥

the final brightness of the keyboard on success 💡 — or a negative error code on failure. yeah, negative. if you see a negative number, that's not brightness, that's a cry for help. 😭

---

👑 SEE ALSO 👑

• Kernel file ./drivers/platform/chrome/wilco_ec/keyboard_leds.c — go read the source, it's iconic.
• struct wilco_keyboard_leds_msg(9) — the struct bestie you'll be keeping company with. 🧚

---

ngl, this one's short and sweet — but the mode check is the whole plot, so don't skip it. 💀

---

mwah, that's a wrap! this lil page came to you from ./drivers/platform/chrome/wilc..., dated October 2026, and it's still kbbl_init(9) at heart. go forth and light up that keyboard, bestie — slay. 💖✨🎀