blob: ad18b2326b689a41471216f3889480b11768ca82 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
.. SPDX-License-Identifier: GPL-2.0-only
.. Copyright 2024 Linaro Ltd.
====================
Power Sequencing API
====================
:Author: Bartosz Golaszewski
Introduction
============
This framework is designed to abstract complex power-up sequences that are
shared between multiple logical devices in the Linux kernel.
The intention is to allow consumers to obtain a power sequencing handle
exposed by the power sequence provider and delegate the actual requesting and
control of the underlying resources as well as to allow the provider to
mitigate any potential conflicts between multiple users behind the scenes.
Glossary
--------
The power sequencing API uses a number of terms specific to the subsystem:
Unit
A unit is a discrete chunk of a power sequence. For instance one unit may
enable a set of regulators, another may enable a specific GPIO. Units can
define dependencies in the form of other units that must be enabled before
it itself can be.
Target
A target is a set of units (composed of the "final" unit and its
dependencies) that a consumer selects by its name when requesting a handle
to the power sequencer. Via the dependency system, multiple targets may
share the same parts of a power sequence but ignore parts that are
irrelevant.
Descriptor
A handle passed by the pwrseq core to every consumer that serves as the
entry point to the provider layer. It ensures coherence between different
users and keeps reference counting consistent.
Consumer interface
==================
The consumer API is aimed to be as simple as possible. The driver interested in
getting a descriptor from the power sequencer should call pwrseq_get() and
specify the name of the target it wants to reach in the sequence after calling
pwrseq_power_up(). The descriptor can be released by calling pwrseq_put() and
the consumer can request the powering down of its target with
pwrseq_power_off(). Note that there is no guarantee that pwrseq_power_off()
will have any effect as there may be multiple users of the underlying resources
who may keep them active.
Provider interface
==================
The provider API is admittedly not nearly as straightforward as the one for
consumers but it makes up for it in flexibility.
Each provider can logically split the power-up sequence into discrete chunks
(units) and define their dependencies. They can then expose named targets that
consumers may use as the final point in the sequence that they wish to reach.
To that end the providers fill out a set of configuration structures and
register with the pwrseq subsystem by calling pwrseq_device_register().
Dynamic consumer matching
-------------------------
The main difference between pwrseq and other Linux kernel providers is the
mechanism for dynamic matching of consumers and providers. Every power sequence
provider driver must implement the `match()` callback and pass it to the pwrseq
core when registering with the subsystems.
When a client requests a sequencer handle, the core will call this callback for
every registered provider and let it flexibly figure out whether the proposed
client device is indeed its consumer. For example: if the provider binds to the
device-tree node representing a power management unit of a chipset and the
consumer driver controls one of its modules, the provider driver may parse the
relevant regulator supply properties in device tree and see if they lead from
the PMU to the consumer.
API reference
=============
.. kernel-doc:: include/linux/pwrseq/provider.h
:internal:
.. kernel-doc:: drivers/power/sequencing/core.c
:export:
|
