fwnode_led_get(9)

💡 fwnode_led_get(9) — bestie's guide to the Kernel API Manual ✨

okay so like, this one's from the Kernel API Manual, section 9, and it's literally called fwnode_led_get. yes it's a mouthful. no we're not changing it. let's go 🎀

---

🌸 NAME 🌸

fwnode_led_get — request a LED device via the LED framework 👑

like, you're asking the LED framework very nicely for a LED device. that's the whole vibe. ✨

---

🦋 SYNOPSIS 🦋

struct led_classdev * fwnode_led_get (struct fwnode_handle *fwnode , int
       index , const char *name );

copy that exactly bestie, character for character, don't @ me 💅

---

💜 ARGUMENTS 💜

• fwnode — the firmware node you're grabbing the LED device from. that's your starting point, your source of truth, your main character 🫶
• index — the index of the LED. yes, the actual number. which one you want out of the pile 🔢
• name — the name of the LED, used to map it to its function, if present. if it's not there, well, it's not there 🙈

---

⭐ DESCRIPTION ⭐

okay so here's the tea: this returns the LED device parsed from the phandle specified in the "leds" property of a device tree node 🎀

and if it fails? it returns a negative error-code. not zero, not vibes, a negative error-code. so like, check your return value, bestie, fr fr 😭

lowkey important: "leds" is a literal property name and phandle is a literal thing — keep those exact, iykyk 🧚

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/leds/led-class.c 👑
• led_classdev_suspend(9)
• led_classdev_resume(9)
• led_put(9)
• devm_of_led_get(9)
• led_get(9)
• devm_led_get(9)
• led_add_lookup(9)
• led_remove_lookup(9)
• devm_of_led_get_optional(9)
• led_classdev_register_ext(9)
• led_classdev_unregister(9)
• devm_led_classdev_register_ext(9)
• devm_led_classdev_unregister(9)

like, that's the whole friend group right there, go say hi 💖

---

aaaand that's the page!! sourced from ./drivers/leds, dated October 2026, and it's fwnode_led_get(9) all day every day ✨ slay, go get your LED 🦋💅🍓