pwm_get_state_hw(9)

📦 version 7.3.1, in nixpkgs unstable

✨ pwm_get_state_hw(9) — from the Kernel API Manual, bestie ✨

okay so this is a page straight out of the Kernel API Manual and it's lowkey one of the most useful lil functions ever — it's literally "hey hardware, what's your vibe rn?" 💅

🌸 NAME 🌸

pwm_get_state_hw — get the current PWM state from hardware 🫶

Like, actually from the hardware. Not the wishlist version. The real one. No cap.

🎀 SYNOPSIS 🎀

int pwm_get_state_hw (struct pwm_device *pwm , struct pwm_state *state
);

that's the whole signature, she's not complicated, she just works ✨

🦋 ARGUMENTS 🦋

  • pwm — the PWM device 👑 like, the actual one you're curious about
  • state — the state you're gonna fill with the current PWM state 💖 it's giving "empty cup, ready to be filled"

💜 DESCRIPTION 💜

So this is basically pwm_get_state's sibling, right? Same energy, but with one iconic plot twist: it reads the current PWM state from hardware instead of the requested state 😭

Requested state = what you asked for. Hardware state = what's actually happening. Not me trusting the hardware over the request... actually yes, that's exactly what we're doing 💀

⭐ RETURN ⭐

  • 0 on success 🎉 slay
  • a negative error code on failure 🙈 not slay, but at least it tells you

🌈 CONTEXT 🌈

May sleep. 😴

fr fr, this one is allowed to nap — don't go calling it from somewhere rude like an atomic context, okay? Be nice to her.

🔥 SEE ALSO 🔥

Kernel file ./drivers/pwm/core.c — go read the source, iykyk 📖

like an entire friend group of PWM functions, and honestly? obsessed 🫶💅

🧚 quick reminder bestie: read the hardware state when you want the truth, read the requested state when you want the dream. they are not the same and that's the whole point 💖

and that's the page!! sign-off time: this one lives under ./drivers/pwm, dated October 2026 — periodt, go touch some PWM hardware 💜🎀

📦 where this page comes from