Home
last modified time | relevance | path

Searched full:domain (Results 1 – 25 of 583) sorted by relevance

12345678910>>...24

/Documentation/devicetree/bindings/clock/
Dfsl,imx8-acm.yaml64 - description: power domain of IMX_SC_R_AUDIO_CLK_0
65 - description: power domain of IMX_SC_R_AUDIO_CLK_1
66 - description: power domain of IMX_SC_R_MCLK_OUT_0
67 - description: power domain of IMX_SC_R_MCLK_OUT_1
68 - description: power domain of IMX_SC_R_AUDIO_PLL_0
69 - description: power domain of IMX_SC_R_AUDIO_PLL_1
70 - description: power domain of IMX_SC_R_ASRC_0
71 - description: power domain of IMX_SC_R_ASRC_1
72 - description: power domain of IMX_SC_R_ESAI_0
73 - description: power domain of IMX_SC_R_SAI_0
[all …]
Dkeystone-gate.txt11 - reg : psc control and domain address address space
12 - reg-names : psc control and domain registers
13 - domain-id : psc domain id needed to check the transition state register
25 reg-names = "control", "domain";
26 domain-id = <0>;
/Documentation/devicetree/bindings/power/
Dpower-domain.yaml4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
20 This device tree binding can be used to bind PM domain consumer devices with
21 their PM domains provided by PM domain providers. A PM domain provider can be
24 phandle arguments (so called PM domain specifiers) of length specified by the
25 \#power-domain-cells property in the PM domain provider node.
29 pattern: "^(power-controller|power-domain|performance-domain)([@-].*)?$"
31 domain-idle-states:
37 power-domain provider. The idle state definitions are compatible with the
38 domain-idle-state bindings, specified in ./domain-idle-state.yaml.
40 Note that, the domain-idle-state property reflects the idle states of this
[all …]
Dmediatek,power-controller.yaml17 IP cores belonging to a power domain should contain a 'power-domains'
18 property that is a phandle for SCPSYS node representing the domain.
36 '#power-domain-cells':
46 "^power-domain@[0-9a-f]+$":
47 $ref: "#/$defs/power-domain-node"
49 "^power-domain@[0-9a-f]+$":
50 $ref: "#/$defs/power-domain-node"
52 "^power-domain@[0-9a-f]+$":
53 $ref: "#/$defs/power-domain-node"
55 "^power-domain@[0-9a-f]+$":
[all …]
Dpower_domain.txt7 This device tree binding can be used to bind PM domain consumer devices with
8 their PM domains provided by PM domain providers. A PM domain provider can be
11 phandle arguments (so called PM domain specifiers) of length specified by the
12 #power-domain-cells property in the PM domain provider node.
14 ==PM domain providers==
16 See power-domain.yaml.
18 ==PM domain consumers==
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
22 the power controller that is the PM domain provider.
25 - power-domain-names : A list of power domain name strings sorted in the same
[all …]
Dfsl,imx-gpcv2.yaml16 Power domains contained within GPC node are generic power domain
18 Documentation/devicetree/bindings/power/power-domain.yaml, which are
21 IP cores belonging to a power domain should contain a 'power-domains'
22 property that is a phandle for PGC node representing the domain.
56 "power-domain@[0-9a-f]+$":
62 '#power-domain-cells':
67 Power domain index. Valid values are defined in
76 A number of phandles to clocks that need to be enabled during domain
78 inside this power domain.
90 power-up sequencing of the domain. The resets belong to devices
[all …]
Drockchip,power-controller.yaml19 generic power domain providers documented in
20 Documentation/devicetree/bindings/power/power-domain.yaml.
22 IP cores belonging to a power domain should contain a
24 power domain node representing the domain.
48 "#power-domain-cells":
59 - "#power-domain-cells"
64 "^power-domain@[0-9a-f]+$":
78 "^power-domain@[0-9a-f]+$":
92 "^power-domain@[0-9a-f]+$":
99 "#power-domain-cells":
[all …]
Drenesas,sysc-rmobile.yaml36 This node contains a hierarchy of PM domain nodes, which should match the
37 Power Area Hierarchy in the Power Domain Specifications section of the
61 PM domain node representing a PM domain. This node should be named by
68 If the PM domain is not always-on, this property must contain the
71 If the PM domain is always-on, this property must be omitted.
79 '#power-domain-cells':
83 - '#power-domain-cells'
90 // This shows a subset of the r8a7740 PM domain hierarchy, containing the
91 // C5 "always-on" domain, 2 of its subdomains (A4S and A4SU), and the A3SP
92 // domain, which is a subdomain of A4S.
[all …]
Ddomain-idle-state.yaml4 $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
7 title: PM Domain Idle States
13 A domain idle state node represents the state parameters that will be used to
14 select the state when there are no active components in the PM domain.
18 const: domain-idle-states
21 "^(cpu|cluster|domain)-":
25 Each state node represents a domain idle state description.
29 const: domain-idle-state
68 domain-idle-states {
69 domain_retention: domain-retention {
[all …]
Drockchip-io-domain.yaml4 $id: http://devicetree.org/schemas/power/rockchip-io-domain.yaml#
13 IO domain voltages on some Rockchip SoCs are variable but need to be
42 to report their voltage. The IO Voltage Domain for any non-specified
48 - rockchip,px30-io-voltage-domain
49 - rockchip,px30-pmu-io-voltage-domain
50 - rockchip,rk3188-io-voltage-domain
51 - rockchip,rk3228-io-voltage-domain
52 - rockchip,rk3288-io-voltage-domain
53 - rockchip,rk3308-io-voltage-domain
54 - rockchip,rk3328-io-voltage-domain
[all …]
Dfsl,imx-gpc.yaml16 The power domains are generic power domain providers as documented in
17 Documentation/devicetree/bindings/power/power-domain.yaml. They are
20 IP cores belonging to a power domain should contain a 'power-domains'
21 property that is a phandle pointing to the power domain the device belongs
66 "power-domain@[0-9]$":
72 '#power-domain-cells':
88 A number of phandles to clocks that need to be enabled during domain
90 inside this power domain.
97 - '#power-domain-cells'
130 power-domain@0 {
[all …]
Dpd-samsung.yaml17 - $ref: power-domain.yaml#
38 Human readable string with domain name. Will be visible in userspace
41 "#power-domain-cells":
49 - "#power-domain-cells"
56 lcd0_pd: power-domain@10023c80 {
59 #power-domain-cells = <0>;
63 mfc_pd: power-domain@10044060 {
66 #power-domain-cells = <0>;
/Documentation/devicetree/bindings/dvfs/
Dperformance-domain.yaml4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml#
14 CPUs that run in the same performance domain. Performance domains must not
15 be confused with power domains. A performance domain is defined by a set
17 performance domain, there is a single point of control that affects all the
18 devices in the domain, making it impossible to set the performance level of
19 an individual device in the domain independently from other devices in
20 that domain. For example, a set of CPUs that share a voltage domain, and
22 domain.
24 This device tree binding can be used to bind performance domain consumer
25 devices with their performance domains provided by performance domain
[all …]
/Documentation/scheduler/
Dsched-stats.rst18 per-domain. Note that domains (and their associated information) will only
21 In version 14 of schedstat, there is at least one level of domain
23 domain. Domains have no particular names in this implementation, but
25 cpus on the machine, while domain0 is the most tightly focused domain,
27 are no architectures which need more than three domain levels. The first
28 field in the domain stats is a bit map indicating which cpus are affected
29 by that domain.
70 Domain statistics
72 One of these is produced per domain for each cpu described. (Note that if
76 domain<N> <cpumask> 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 3…
[all …]
Dsched-domains.rst5 Each CPU has a "base" scheduling domain (struct sched_domain). The domain
7 MUST be NULL terminated, and domain structures should be per-CPU as they are
10 Each scheduling domain spans a number of CPUs (stored in the ->span field).
11 A domain's span MUST be a superset of it child's span (this restriction could
12 be relaxed if the need arises), and a base domain for CPU i MUST span at least
13 i. The top domain for each CPU will generally span all CPUs in the system
16 explicitly set. A sched domain's span means "balance process load among these
19 Each scheduling domain must have one or more CPU groups (struct sched_group)
22 domain's span. The group pointed to by the ->groups pointer MUST contain the CPU
23 to which the domain belongs. Groups may be shared among CPUs as they contain
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,apr.yaml27 qcom,apr-domain:
31 Selects the processor domain for apr
33 2 = PC Domain
34 3 = Modem Domain
35 4 = ADSP Domain
36 5 = Application processor Domain
37 6 = Modem2 Domain
38 7 = Application Processor2 Domain
41 qcom,domain:
46 Selects the processor domain for apr
[all …]
/Documentation/devicetree/bindings/soc/imx/
Dfsl,imx8mm-vpu-blk-ctrl.yaml15 located in the VPU domain of the SoC.
26 '#power-domain-cells':
32 power-domain-names:
51 - power-domain-names
65 - description: bus power domain
66 - description: G1 decoder power domain
67 - description: G2 decoder power domain
68 - description: H1 encoder power domain
70 power-domain-names:
93 - description: H1 encoder power domain
[all …]
/Documentation/devicetree/bindings/soc/mediatek/
Dscpsys.txt8 domain control.
10 The driver implements the Generic PM domain bindings described in
11 power/power-domain.yaml. It provides the power domains defined in
30 - #power-domain-cells: Must be 1
48 - vdec-supply: Power supply for the vdec power domain
49 - venc-supply: Power supply for the venc power domain
50 - isp-supply: Power supply for the isp power domain
51 - mm-supply: Power supply for the mm power domain
52 - venc_lt-supply: Power supply for the venc_lt power domain
53 - audio-supply: Power supply for the audio power domain
[all …]
/Documentation/devicetree/bindings/soc/ti/
Dsci-pm-domain.yaml4 $id: http://devicetree.org/schemas/soc/ti/sci-pm-domain.yaml#
7 title: TI-SCI generic power domain
13 - $ref: /schemas/power/power-domain.yaml#
22 This PM domain node represents the global PM domain managed by the TI-SCI
28 const: ti,sci-pm-domain
30 "#power-domain-cells":
51 compatible = "ti,sci-pm-domain";
52 #power-domain-cells = <1>;
57 compatible = "ti,sci-pm-domain";
58 #power-domain-cells = <2>;
/Documentation/devicetree/bindings/arm/hisilicon/controller/
Dhi6220-domain-ctrl.yaml4 $id: http://devicetree.org/schemas/arm/hisilicon/controller/hi6220-domain-ctrl.yaml#
7 title: Hisilicon Hi6220 domain controller
13 Hisilicon designs some special domain controllers for mobile platform,
14 such as: the power Always On domain controller, the Media domain
15 controller(e.g. codec, G3D ...) and the Power Management domain
18 The compatible names of each domain controller are as follows:
19 Power Always ON domain controller --> hisilicon,hi6220-aoctrl
20 Media domain controller --> hisilicon,hi6220-mediactrl
21 Power Management domain controller --> hisilicon,hi6220-pmctrl
/Documentation/power/regulator/
Doverview.rst52 - Power Domain
55 domain.
67 - Domain 1: Switch-1, Consumers D & E.
68 - Domain 2: Switch-2, Consumers B & C.
69 - Domain 3: Consumer A.
73 Domain-1 --> Domain-2 --> Domain-3.
75 A power domain may have regulators that are supplied power
84 - Domain 1: Regulator-2, Consumer B.
85 - Domain 2: Consumer A.
89 Domain-1 --> Domain-2
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Driscv,aplic.yaml19 interrupt sources connect to the root APLIC domain and a parent APLIC
20 domain can delegate interrupt sources to it's child APLIC domains. There
21 is one device tree node for each APLIC domain.
45 Given APLIC domain directly injects external interrupts to a set of
51 Given APLIC domain forwards wired interrupts as MSIs to a AIA incoming
54 domain supports both MSI mode and Direct mode in HW. In this case, the
63 APLIC domain.
72 A list of child APLIC domains for the given APLIC domain. Each child
73 APLIC domain is assigned a child index in increasing order, with the
74 first child APLIC domain assigned child index 0. The APLIC domain child
[all …]
/Documentation/devicetree/bindings/arm/ux500/
Dpower_domain.txt6 The implementation of PM domains for UX500 are based upon the generic PM domain
9 ==PM domain providers==
13 - #power-domain-cells : Number of cells in a power domain specifier, must be 1.
18 #power-domain-cells = <1>;
21 ==PM domain consumers==
24 - power-domains: A phandle and PM domain specifier. Below are the list of
/Documentation/devicetree/bindings/remoteproc/
Dqcom,sc7180-pas.yaml86 - description: LCX power domain
87 - description: LMX power domain
88 power-domain-names:
102 - description: CX power domain
103 - description: MX power domain
104 - description: MSS power domain
105 power-domain-names:
120 - description: CX power domain
121 - description: MSS power domain
122 power-domain-names:
[all …]
/Documentation/devicetree/bindings/soc/dove/
Dpmu.txt13 - domains: sub-node containing domain descriptions
20 Power domain descriptions are listed as child nodes of the "domains"
21 sub-node. Each domain has the following properties:
24 - #power-domain-cells: must be 0.
42 vpu_domain: vpu-domain {
43 #power-domain-cells = <0>;
49 gpu_domain: gpu-domain {
50 #power-domain-cells = <0>;

12345678910>>...24