devm_fwnode_pwm_get(9)

💅 devm_fwnode_pwm_get(9)

okay bestie, welcome to the Kernel API Manual ✨ — today's main character is devm_fwnode_pwm_get(9), and she is literally the friend who handles all the cleanup so you don't have to 🫶

---

🌸 NAME 🌸

devm_fwnode_pwm_get — request a resource managed PWM from firmware node 💖

---

✨ SYNOPSIS ✨

struct pwm_device * devm_fwnode_pwm_get (struct device *dev , struct
fwnode_handle *fwnode , const char *con_id );

---

🎀 ARGUMENTS 🎀

• dev — the device that's gonna be the PWM consumer 🥰 this is who's asking for the PWM
• fwnode — the firmware node we're grabbing the PWM from, iykyk 🌈
• con_id — the consumer name, aka the vibe check label for who this PWM is for 🦋

---

💫 DESCRIPTION 💫

so basically it returns the PWM device parsed from the firmware node 🔥 that's the whole thing, ngl.

if u want the full detailed tea on how the parsing actually goes down, go read of_pwm_get and acpi_pwm_get — they spill it all 💅

---

👑 RETURN 👑

a pointer to the requested PWM device 💖 … OR an ERR_PTR-encoded error code if it fails 😭 fr fr, check for errors, bestie, don't just rawdog that pointer.

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/pwm/core.c
• pwm_round_waveform_might_sleep(9)
• pwm_get_waveform_might_sleep(9)
• pwm_set_waveform_might_sleep(9)
• pwm_apply_might_sleep(9)
• pwm_apply_atomic(9)
• pwm_get_state_hw(9)
• pwm_adjust_config(9)
• pwm_capture(9)
• pwm_request_from_chip(9)
• of_pwm_get(9)
• acpi_pwm_get(9)
• pwm_get(9)
• pwm_put(9)
• devm_pwm_get(9)
• __pwmchip_add(9)
• pwmchip_remove(9)
• pwm_add_table(9)
• pwm_remove_table(9)

---

that's the whole page, no cap 🎀 she lives in ./drivers/pwm, dated October 2026, and she ate 💅✨ go forth and devm responsibly bestie 🦋💜