gpio_keys_enable_button(9)

✨ gpio_keys_enable_button(9) ✨

okay so we're in the Kernel API Manual today bestie, and the star of the show is gpio_keys_enable_button(9) — a whole kernel function whose entire personality is "turn a GPIO button back on." iconic behavior honestly 💅

🎀 NAME 🎀

gpio_keys_enable_button — enables given GPIO button. that's it. that's the whole job. and she does it slayfully 🫶

🌸 SYNOPSIS 🌸

void gpio_keys_enable_button (struct gpio_button_data *bdata );

void return, one pointer argument, zero drama. well — almost zero drama, keep reading 😭

🦋 ARGUMENTS 🦋

• bdata — button data for button to be disabled. and yes, the original manpage literally says "to be disabled" here even though the function is the enable one. not me catching that 🙈 but fr fr that's the actual wording, so I'm passing it straight to you, no cap. it's the struct gpio_button_data * for the button in question.

💖 DESCRIPTION 💖

Enables the given button, the one pointed at by bdata. that's the vibe. button goes from "nope" to "yep." ✨

⚠️ okay this part is the important part, bestie, pay attention: you gotta make sure that bdata->disable_lock is locked when you enter this function. why? to avoid races with concurrent threads that are trying to enable the same button at the same time. it's giving two people grabbing the same iced coffee at once. lock it or things get cursed 💀🔒

🌈 SEE ALSO 🌈

• Kernel file ./drivers/input/keyboard/gpio_keys.c
• get_n_events_by_type(9)
• get_bm_events_by_type(9)
• gpio_keys_disable_button(9)
• gpio_keys_attr_show_helper(9)
• gpio_keys_attr_store_helper(9)

that's the whole page, king 💜 it lives over in ./drivers/input/keyboard, and this lil doc is dated October 2026 — so yeah, bookmark it, screenshot it, send it to the group chat. bye bestie, go lock that disable_lock 🧚‍♀️🍓