Searched full:domain (Results 1 – 25 of 345) sorted by relevance
12345678910>>...14
| /Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
19 This device tree binding can be used to bind PM domain consumer devices with
20 their PM domains provided by PM domain providers. A PM domain provider can be
23 phandle arguments (so called PM domain specifiers) of length specified by the
24 \#power-domain-cells property in the PM domain provider node.
28 pattern: "^(power-controller|power-domain)([@-].*)?$"
30 domain-idle-states:
34 power-domain provider. The idle state definitions are compatible with the
35 domain-idle-state bindings, specified in ./domain-idle-state.yaml.
37 Note that, the domain-idle-state property reflects the idle states of this
[all …]
|
| D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
24 match the Power Area Hierarchy in the Power Domain Specifications section of
28 == PM Domain Nodes ==
30 Each of the PM domain nodes represents a PM domain, as documented by the
31 generic PM domain bindings in
32 Documentation/devicetree/bindings/power/power-domain.yaml.
38 - #power-domain-cells: Must be 0.
41 - reg: If the PM domain is not always-on, this property must contain the bit
47 If the PM domain is always-on, this property must be omitted.
52 This shows a subset of the r8a7740 PM domain hierarchy, containing the
[all …]
|
| D | power_domain.txt | 7 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 …]
|
| D | fsl,imx-gpcv2.yaml | 16 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.
45 "power-domain@[0-9]$":
49 '#power-domain-cells':
54 Power domain index. Valid values are defined in
61 A number of phandles to clocks that need to be enabled during domain
63 inside this power domain.
70 - '#power-domain-cells'
[all …]
|
| D | domain-idle-state.yaml | 4 $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
7 title: PM Domain Idle States binding description
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)-":
24 Each state node represents a domain idle state description.
28 const: domain-idle-state
58 domain-idle-states {
59 domain_retention: domain-retention {
[all …]
|
| D | fsl,imx-gpc.yaml | 16 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
49 "power-domain@[0-9]$":
53 '#power-domain-cells':
69 A number of phandles to clocks that need to be enabled during domain
71 inside this power domain.
78 - '#power-domain-cells'
107 power-domain@0 {
[all …]
|
| D | pd-samsung.yaml | 17 - $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>;
|
| D | xlnx,zynqmp-genpd.txt | 5 generic PM domain binding[1].
7 [1] Documentation/devicetree/bindings/power/power-domain.yaml
9 == Zynq MPSoC Generic PM Domain Node ==
13 - #power-domain-cells: Number of cells in a PM domain specifier. Must be 1.
15 Power domain ID indexes are mentioned in
25 #power-domain-cells = <1>;
|
| D | rockchip-io-domain.txt | 4 IO domain voltages on some Rockchip SoCs are variable but need to be
34 - "rockchip,px30-io-voltage-domain" for px30
35 - "rockchip,px30-pmu-io-voltage-domain" for px30 pmu-domains
36 - "rockchip,rk3188-io-voltage-domain" for rk3188
37 - "rockchip,rk3228-io-voltage-domain" for rk3228
38 - "rockchip,rk3288-io-voltage-domain" for rk3288
39 - "rockchip,rk3328-io-voltage-domain" for rk3328
40 - "rockchip,rk3368-io-voltage-domain" for rk3368
41 - "rockchip,rk3368-pmu-io-voltage-domain" for rk3368 pmu-domains
42 - "rockchip,rk3399-io-voltage-domain" for rk3399
[all …]
|
| D | amlogic,meson-gx-pwrc.txt | 4 The Amlogic Meson SoCs embeds an internal Power domain controller.
6 VPU Power Domain
9 The Video Processing Unit power domain is controlled by this power controller,
10 but the domain requires some external resources to meet the correct power
12 The bindings must respect the power domain bindings as described in the file
13 power-domain.yaml
22 - #power-domain-cells: should be 0
43 #power-domain-cells = <0>;
|
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 6 Required properties for power domain controller:
19 - #power-domain-cells: Number of cells in a power-domain specifier.
24 Required properties for power domain sub nodes:
25 - reg: index of the power domain, should use macros in:
26 "include/dt-bindings/power/px30-power.h" - for PX30 type power domain.
27 "include/dt-bindings/power/rk3036-power.h" - for RK3036 type power domain.
28 "include/dt-bindings/power/rk3066-power.h" - for RK3066 type power domain.
29 "include/dt-bindings/power/rk3128-power.h" - for RK3128 type power domain.
30 "include/dt-bindings/power/rk3188-power.h" - for RK3188 type power domain.
31 "include/dt-bindings/power/rk3228-power.h" - for RK3228 type power domain.
[all …]
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 13 per-domain. Note that domains (and their associated information) will only
16 In version 14 of schedstat, there is at least one level of domain
18 domain. Domains have no particular names in this implementation, but
20 cpus on the machine, while domain0 is the most tightly focused domain,
22 are no architectures which need more than three domain levels. The first
23 field in the domain stats is a bit map indicating which cpus are affected
24 by that domain.
65 Domain statistics
67 One of these is produced per domain for each cpu described. (Note that if
71 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 …]
|
| D | sched-domains.rst | 5 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/ti/ |
| D | sci-pm-domain.txt | 1 Texas Instruments TI-SCI Generic Power Domain
11 PM Domain Node
13 The PM domain node represents the global PM domain managed by the PMMC, which
14 in this case is the implementation as documented by the generic PM domain
15 bindings in Documentation/devicetree/bindings/power/power-domain.yaml. Because
21 - compatible: should be "ti,sci-pm-domain"
22 - #power-domain-cells: Can be one of the following:
39 compatible = "ti,sci-pm-domain";
40 #power-domain-cells = <1>;
44 PM Domain Consumers
[all …]
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | scpsys.txt | 8 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/arm/hisilicon/controller/ |
| D | hi6220-domain-ctrl.yaml | 4 $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/ |
| D | overview.rst | 52 - 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/arm/ux500/ |
| D | power_domain.txt | 6 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/cpufreq/ |
| D | cpufreq-qcom-hw.txt | 27 each frequency domain.
31 Definition: Frequency domain name i.e.
34 - #freq-domain-cells:
36 Definition: Number of cells in a freqency domain specifier.
38 * Property qcom,freq-domain
39 Devices supporting freq-domain must set their "qcom,freq-domain" property with
40 phandle to a cpufreq_hw followed by the Domain ID(0/1) in the CPU DT node.
59 qcom,freq-domain = <&cpufreq_hw 0>;
75 qcom,freq-domain = <&cpufreq_hw 0>;
88 qcom,freq-domain = <&cpufreq_hw 0>;
[all …]
|
| /Documentation/devicetree/bindings/soc/dove/ |
| D | pmu.txt | 13 - 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>;
|
| /Documentation/devicetree/bindings/clock/ |
| D | keystone-gate.txt | 13 - reg : psc control and domain address address space
14 - reg-names : psc control and domain registers
15 - domain-id : psc domain id needed to check the transition state register
27 reg-names = "control", "domain";
28 domain-id = <0>;
|
| /Documentation/networking/ |
| D | regulatory.rst | 19 to the kernel one regulatory domain to be used as the central
20 core regulatory domain all wireless devices should adhere to.
25 When the regulatory domain is first set up, the kernel will request a
33 Userspace gets a regulatory domain in the kernel by having
38 is CRDA - central regulatory domain agent. Its documented here:
43 it needs a new regulatory domain. A udev rule can be put in place
44 to trigger crda to send the respective regulatory domain for a
65 # set regulatory domain to "Costa Rica"
68 This will request the kernel to set the regulatory domain to
70 to provide a regulatory domain for the alpha2 specified by the user
[all …]
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | raspberrypi,bcm2835-power.txt | 1 Raspberry Pi power domain driver
7 - #power-domain-cells: Should be <1>, we providing multiple power domains.
9 The valid defines for power domain are:
40 #power-domain-cells = <1>;
43 Example for using power domain:
|
| /Documentation/devicetree/bindings/clock/ti/davinci/ |
| D | psc.txt | 12 - #power-domain-cells: from generic power domain binding; shall be set to 1.
21 at least one local domain provides a local reset.
25 Clock, power domain and reset consumers shall use the local power domain
28 domains only provide a clock/power domain and not a reset.
36 #power-domain-cells = <1>;
47 #power-domain-cells = <1>;
70 - Documentation/devicetree/bindings/power/power-domain.yaml
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 107 "^power-domain-":
108 $ref: "../power/power-domain.yaml#"
127 [3] Documentation/devicetree/bindings/power/power-domain.yaml
128 [4] Documentation/devicetree/bindings/power/domain-idle-state.yaml
204 power-domain-names = "psci";
213 power-domain-names = "psci";
227 domain-idle-states {
230 compatible = "domain-idle-state";
238 compatible = "domain-idle-state";
251 CPU_PD0: power-domain-cpu0 {
[all …]
|
12345678910>>...14