tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Documentation: pwrseq: Fix trivial misspellings

Use proper spelling for 'discrete'. When at it, capitalize 'Linux',
which is common practice in the documentation.

Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20241120-pwrseq-doc-trivial-fixes-v1-1-19a70f4dd156@gmail.com

authored by

Javier Carrasco and committed by
Jonathan Corbet 72471fc7 1e726223

+4 -4
+4 -4
Documentation/driver-api/pwrseq.rst
··· 11 11 ============ 12 12 13 13 This framework is designed to abstract complex power-up sequences that are 14 - shared between multiple logical devices in the linux kernel. 14 + shared between multiple logical devices in the Linux kernel. 15 15 16 16 The intention is to allow consumers to obtain a power sequencing handle 17 17 exposed by the power sequence provider and delegate the actual requesting and ··· 25 25 26 26 Unit 27 27 28 - A unit is a discreet chunk of a power sequence. For instance one unit may 28 + A unit is a discrete chunk of a power sequence. For instance one unit may 29 29 enable a set of regulators, another may enable a specific GPIO. Units can 30 30 define dependencies in the form of other units that must be enabled before 31 31 it itself can be. ··· 62 62 The provider API is admittedly not nearly as straightforward as the one for 63 63 consumers but it makes up for it in flexibility. 64 64 65 - Each provider can logically split the power-up sequence into descrete chunks 65 + Each provider can logically split the power-up sequence into discrete chunks 66 66 (units) and define their dependencies. They can then expose named targets that 67 67 consumers may use as the final point in the sequence that they wish to reach. 68 68 ··· 72 72 Dynamic consumer matching 73 73 ------------------------- 74 74 75 - The main difference between pwrseq and other linux kernel providers is the 75 + The main difference between pwrseq and other Linux kernel providers is the 76 76 mechanism for dynamic matching of consumers and providers. Every power sequence 77 77 provider driver must implement the `match()` callback and pass it to the pwrseq 78 78 core when registering with the subsystems.