pwm_get_wave..._might_sleep(9)

🌸 pwm_get_waveform_might_sleep — Kernel API Manual 🦋

okay bestie, so this is a page from the Kernel API Manual, and the star of the show is pwm_get_waveform_might_sleep. The header up there is pwm_get_wave..._might_sleep(9) — yes it's truncated, no it's not a typo, that's just how the manual renders it, iykyk. 💅

---

✨ NAME ✨

pwm_get_waveform_might_sleep — the way you query the hardware about its current configuration. Girlypop, this one cannot be used in atomic context. Like, at all. 🫶

---

🎀 SYNOPSIS 🎀

int pwm_get_waveform_might_sleep (struct pwm_device *pwm , struct pwm_waveform *wf );

---

💖 ARGUMENTS 💖

• pwm — PWM device 💜
• wf — output parameter

---

🌈 DESCRIPTION 🌈

So basically this stores the current configuration of the PWM in wf. ✨ And lowkey the important part: this is the equivalent of pwm_get_state_hw (and not pwm_get_state) for pwm_waveform. No cap, that distinction is doing main character energy here — don't mix them up. 🙈

---

⭐ RETURN ⭐

0 on success, or a negative errno. Periodt. 💀

---

🧚 CONTEXT 🧚

May sleep. 😴 (Which, yeah, is exactly why the whole "cannot be used in atomic context" thing up in NAME is a big deal.)

ngl this is the vibe check that matters most — if you're in atomic context, you do not pass go, you do not call this function. 😭

---

👑 SEE ALSO 👑

Kernel file ./drivers/pwm/core.c

• pwm_round_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)
• devm_fwnode_pwm_get(9)
• __pwmchip_add(9)
• pwmchip_remove(9)
• pwm_add_table(9)
• pwm_remove_table(9)

---

that's the whole page bestie, you ate it up 💅

sign-off time 🎀 — this lil beauty lives under ./drivers/pwm, it's tagged October 2026, and the footer names it pwm_get_wave..._might_sleep(9). slay, go read the source, ily 💖✨