pwm_might_sleep(9)

💖 NAME 💖

okay so bestie, this page is pwm_might_sleep(9) straight out of the Kernel API Manual, and it's literally just one question in function form: is pwm_apply_atomic() supported? that's the whole vibe check. ✨

---

✨ SYNOPSIS ✨

bool pwm_might_sleep (struct pwm_device *pwm );

like, you hand it a PWM device and it hands you back a bool. that's it. that's the whole relationship. 🫶

---

🎀 ARGUMENTS 🎀

• pwm — the PWM device in question 👑 like, the actual device you're curious about, not a copy, not a vibe, the real one.

---

🦋 RETURN 🦋

so here's the tea, and pay attention because it's lowkey backwards-feeling: it returns false if pwm_apply_atomic can be called from atomic context.

yes, false is the good news here. don't @ me, that's just how it is. 💀 read it twice if you have to — false means atomic context is fine, pwm_apply_atomic is callable from there. no cap.

---

🌸 SEE ALSO 🌸

the whole friend group lives in the kernel file ./include/linux/pwm.h and honestly you should go say hi to all of them:

• enum pwm_polarity(9)
• struct pwm_args(9)
• struct pwm_waveform(9)
• struct pwm_device(9)
• pwm_get_state(9)
• pwm_init_state(9)
• pwm_get_relative_duty_cycle(9)
• pwm_set_relative_duty_cycle(9)
• struct pwm_capture(9)
• struct pwm_ops(9)
• struct pwm_chip(9)
• pwmchip_supports_waveform(9)
• pwm_config(9)
• pwm_enable(9)
• pwm_disable(9)

that's the entire squad, no one left behind 💅

---

mwah, that's the page!! 🎀 this little icon came to you from ./include/linux, dated October 2026 — go forth and check your atomic context responsibly, bestie 🦋💜