pm_suspend_ignore_children(9)

okay bestie, you're reading pm_suspend_ignore_children(9) from the Kernel API Manual, and it's lowkey a tiny switch for runtime PM behavior 💅✨

🌸 NAME 🌸

pm_suspend_ignore_children — Set runtime PM behavior regarding children. No cap, that's the whole name vibe 🎀

✨ SYNOPSIS ✨

void pm_suspend_ignore_children (struct device *dev , bool enable );

🎀 ARGUMENTS 🎀

• dev — Target device. The main character device we're talking about 🎯
• enable — Whether or not to ignore possible dependencies on children. Like, yes/no, bestie 💖

💖 DESCRIPTION 💖

If enable is true, the dependencies of dev on its children will not be taken into account by the runtime PM framework going forward. Periodt.

Otherwise, those dependencies will be taken into account. That's the vibe check, fr fr 🦋

🦋 SEE ALSO 🦋

Kernel file: ./include/linux/pm_runtime.h

• pm_runtime_get_noresume(9)
• pm_runtime_put_noidle(9)
• pm_runtime_suspended(9)
• pm_runtime_active(9)
• pm_runtime_status_suspended(9)
• pm_runtime_enabled(9)
• pm_runtime_blocked(9)
• pm_runtime_has_no_callbacks(9)
• pm_runtime_mark_last_busy(9)
• pm_runtime_is_irq_safe(9)
• pm_runtime_idle(9)
• pm_runtime_suspend(9)
• pm_runtime_autosuspend(9)
• pm_runtime_resume(9)
• pm_request_idle(9)
• pm_request_resume(9)
• pm_request_autosuspend(9)
• pm_runtime_get(9)
• pm_runtime_get_sync(9)
• pm_runtime_resume_and_get(9)
• pm_runtime_put(9)
• __pm_runtime_put_autosuspend(9)
• pm_runtime_put_autosuspend(9)
• pm_runtime_put_sync(9)
• pm_runtime_put_sync_suspend(9)
• pm_runtime_put_sync_autosuspend(9)
• pm_runtime_set_active(9)
• pm_runtime_set_suspended(9)
• pm_runtime_disable(9)
• pm_runtime_use_autosuspend(9)
• pm_runtime_dont_use_autosuspend(9)

signing off with sparkle energy from source/version ./include/linux, dated October 2026, for page pm_suspend_ignore_children(9) — mwah, slay, bye bestie 🫶🌈💜