Searched full:domain (Results 1 – 25 of 293) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/power/ |
| 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==
17 - #power-domain-cells : Number of cells in a PM domain specifier;
18 Typically 0 for nodes representing a single PM domain and 1 for nodes
23 - power-domains : A phandle and PM domain specifier as defined by bindings of
25 Some power domains might be powered from another power domain (or have
27 a standard PM domain consumer binding is used. When provided, all domains
[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
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
53 C5 "always-on" domain, 2 of its subdomains (A4S and A4SU), and the A3SP domain,
[all …]
|
| D | pd-samsung.txt | 8 * samsung,exynos4210-pd - for exynos4210 type power domain.
9 * samsung,exynos5433-pd - for exynos5433 type power domain.
12 - #power-domain-cells: number of cells in power domain specifier;
16 - label: Human readable string with domain name. Will be visible in userspace
18 - power-domains: phandle pointing to the parent power domain, for more details
26 defined with a phandle to respective power domain.
30 lcd0: power-domain-lcd0 {
33 #power-domain-cells = <0>;
37 mfc_pd: power-domain@10044060 {
40 #power-domain-cells = <0>;
|
| D | fsl,imx-gpc.txt | 21 The power domains are generic power domain providers as documented in
27 - reg: Must contain the DOMAIN_INDEX of this power domain
36 - #power-domain-cells: Should be 0
39 - clocks: a number of phandles to clocks that need to be enabled during domain
41 this power domain
42 - power-supply: a phandle to the regulator powering this domain
58 power-domain@0 {
60 #power-domain-cells = <0>;
63 pd_pu: power-domain@1 {
65 #power-domain-cells = <0>;
[all …]
|
| D | fsl,imx-gpcv2.txt | 18 Power domains contained within GPC node are generic power domain
26 - reg: Power domain index. Valid values are defined in
30 - #power-domain-cells: Should be 0
34 - power-supply: Power supply used to power the domain
36 domain power-up sequencing to ensure reset propagation into devices
37 located inside this power domain
53 pgc_pcie_phy: power-domain@1 {
54 #power-domain-cells = <0>;
63 Specifying power domain for IP modules
66 IP cores belonging to a power domain should contain a 'power-domains'
[all …]
|
| D | qcom,rpmpd.txt | 8 * qcom,msm8996-rpmpd: RPM Power domain for the msm8996 family of SoC
9 * qcom,msm8998-rpmpd: RPM Power domain for the msm8998 family of SoC
10 * qcom,qcs404-rpmpd: RPM Power domain for the qcs404 family of SoC
11 * qcom,sdm845-rpmhpd: RPMh Power domain for the sdm845 family of SoC
12 - #power-domain-cells: number of cells in Power domain specifier
14 - operating-points-v2: Phandle to the OPP table for the Power domain.
19 various OPPs for different platforms as well as Power domain indexes
21 Example: rpmh power domain controller and OPP table
31 #power-domain-cells = <1>;
79 Example: rpm power domain controller and OPP table
[all …]
|
| 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 | xlnx,zynqmp-genpd.txt | 5 generic PM domain binding[1].
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 | 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
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 intersection of cpumasks from any two of these groups
24 contain the CPU to which the domain belongs. Groups may be shared among
[all …]
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | scpsys.txt | 8 domain control.
10 The driver implements the Generic PM domain bindings described in
28 - #power-domain-cells: Must be 1
42 - vdec-supply: Power supply for the vdec power domain
43 - venc-supply: Power supply for the venc power domain
44 - isp-supply: Power supply for the isp power domain
45 - mm-supply: Power supply for the mm power domain
46 - venc_lt-supply: Power supply for the venc_lt power domain
47 - audio-supply: Power supply for the audio power domain
48 - usb-supply: Power supply for the usb power domain
[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
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
46 Hardware blocks belonging to a PM domain should contain a "power-domains"
[all …]
|
| /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/networking/ |
| D | regulatory.txt | 16 to the kernel one regulatory domain to be used as the central
17 core regulatory domain all wireless devices should adhere to.
22 When the regulatory domain is first set up, the kernel will request a
30 Userspace gets a regulatory domain in the kernel by having
35 is CRDA - central regulatory domain agent. Its documented here:
40 it needs a new regulatory domain. A udev rule can be put in place
41 to trigger crda to send the respective regulatory domain for a
62 # set regulatory domain to "Costa Rica"
65 This will request the kernel to set the regulatory domain to
67 to provide a regulatory domain for the alpha2 specified by the user
[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>;
|
| D | renesas,r8a7778-cpg-clocks.txt | 5 The CPG also provides a Clock Domain for SoC devices, in combination with the
15 - #power-domain-cells: Must be 0
17 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
19 "power-domains" property, as documented by the generic PM domain bindings in
35 #power-domain-cells = <0>;
39 - CPG/MSTP Clock Domain member device node:
|
| D | renesas,r8a7779-cpg-clocks.txt | 5 The CPG also provides a Clock Domain for SoC devices, in combination with the
17 - #power-domain-cells: Must be 0
19 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
21 "power-domains" property, as documented by the generic PM domain bindings in
37 #power-domain-cells = <0>;
41 - CPG/MSTP Clock Domain member device node:
|
| D | renesas,rz-cpg-clocks.txt | 5 The CPG also provides a Clock Domain for SoC devices, in combination with the
19 - #power-domain-cells: Must be 0
21 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
23 "power-domains" property, as documented by the generic PM domain bindings in
39 #power-domain-cells = <0>;
43 - CPG/MSTP Clock Domain member device node:
|
| /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>;
|
12345678910>>...12