diff options
| author | Brian Norris <briannorris@chromium.org> | 2026-10-01 08:50:08 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2026-10-14 20:58:53 +0200 |
| commit | 15ef5c343b250c7ffe3c3e8311101089c0a4e001 (patch) | |
| tree | 1d34b285acded8bb5389b72712c9a9972fdde6d8 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | dd2f2b9b1082c1e4283cb5e0aea0bc8ebd966c81 (diff) | |
PM: runtime: Expand introduction with core concepts and structure
I commonly see people have difficulty learning how runtime PM works
because of the following key points [*]:
1) there are several boolean concepts in runtime PM, with somewhat
similar meanings:
enabled / disabled
active / suspended
allowed / forbidden
2) if these concepts are documented at all, they're scattered across
the kerneldoc or Documentation/
3) the runtime_pm.rst docs don't make any attempt to ease a reader into
understanding the concepts, and instead jump straight into how it's
implemented (queues, 'struct device' fields, helpers).
Let's try to remedy this a bit by discussing the core concepts and
highlights at the top of the introduction, and introduce a few
sub-headings, so it's easier to navigate different aspects of the
introduction.
While shuffling the intro around, I also see that the existing text
largely mirrors the layout of the following sections (2, 3, and 4), but
does so out of order. Reorder those, and point to section numbers.
[*] In addition to API complexity. I count 61 pm_*() helpers, 7 of which
are variations of put() and 8 of which are variations of get().
Signed-off-by: Brian Norris <briannorris@chromium.org>
Link: https://patch.msgid.link/20261001085009.v4.1.I45a794e4452e3df22419acdd8f11e2b788b3413f@changeid
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
