Searched full:domains (Results 1 – 25 of 849) sorted by relevance
12345678910>>...34
| /Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 1 * ST-Ericsson UX500 PM Domains
3 UX500 supports multiple PM domains which are used to gate power to one or
6 The implementation of PM domains for UX500 are based upon the generic PM domain
12 - compatible: Must be "stericsson,ux500-pm-domains".
17 compatible = "stericsson,ux500-pm-domains";
24 - power-domains: A phandle and PM domain specifier. Below are the list of
34 power-domains = <&pm_domains DOMAIN_VAPE>
|
| /Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 1 * Generic PM domains
3 System on chip designs are often divided into multiple PM domains that can be
8 their PM domains provided by PM domain providers. A PM domain provider can be
10 domains. A consumer node can refer to the provider by a phandle and a set of
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
26 order as the power-domains property. Consumers drivers will use
27 power-domain-names to match power domains with power-domains
35 power-domains = <&power 0>;
42 power-domains = <&power 0>, <&power 1> ;
49 In the second example the consumer device are partitioned across two PM domains,
[all …]
|
| D | power-domain.yaml | 7 title: Generic PM domains
15 System on chip designs are often divided into multiple PM domains that can be
17 leakage current. Moreover, in some cases the similar PM domains may also be
21 their PM domains provided by PM domain providers. A PM domain provider can be
23 domains. A consumer node can refer to the provider by a phandle and a set of
41 PM domain and not the idle states of the devices or sub-domains in the PM
42 domain. Devices and sub-domains have their own idle states independent of
48 Phandles to the OPP tables of power domains that are capable of scaling
50 a single power domain only or all the power domains provided by the
58 domains (e.g. power controllers), but can be any value as specified
[all …]
|
| D | pd-samsung.yaml | 7 title: Samsung Exynos SoC Power Domains
13 Exynos processors include support for multiple power domains which are used
39 to let user to distinguish between multiple domains in SoC.
44 power-domains:
|
| /Documentation/devicetree/bindings/media/ |
| D | qcom,sdm845-venus.yaml | 23 power-domains:
53 power-domains:
60 - power-domains
79 power-domains:
86 - power-domains
111 power-domains = <&videocc VENUS_GDSC>;
121 power-domains = <&videocc VCODEC0_GDSC>;
129 power-domains = <&videocc VCODEC1_GDSC>;
|
| D | mediatek-mdp.txt | 19 - power-domains: a phandle to the power domain, see
38 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
48 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
56 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
63 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
70 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
77 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
85 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
93 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
|
| D | amphion,vpu.yaml | 31 power-domains:
67 power-domains:
95 - power-domains
105 - power-domains
120 power-domains = <&pd IMX_SC_R_VPU>;
127 power-domains = <&pd IMX_SC_R_VPU_MU_0>;
135 power-domains = <&pd IMX_SC_R_VPU_MU_1>;
143 power-domains = <&pd IMX_SC_R_VPU_MU_2>;
149 power-domains = <&pd IMX_SC_R_VPU_DEC_0>;
160 power-domains = <&pd IMX_SC_R_VPU_ENC_0>;
[all …]
|
| D | qcom,sdm660-venus.yaml | 45 power-domains:
62 power-domains:
69 - power-domains
87 power-domains:
94 - power-domains
144 power-domains = <&mmcc VENUS_GDSC>;
150 power-domains = <&mmcc VENUS_CORE0_GDSC>;
157 power-domains = <&mmcc VENUS_CORE0_GDSC>;
|
| D | qcom,msm8996-venus.yaml | 25 power-domains:
63 power-domains:
70 - power-domains
88 power-domains:
95 - power-domains
121 power-domains = <&mmcc VENUS_GDSC>;
148 power-domains = <&mmcc VENUS_CORE0_GDSC>;
155 power-domains = <&mmcc VENUS_CORE1_GDSC>;
|
| D | mediatek,mt8195-jpegdec.yaml | 19 power-domains:
69 power-domains:
79 - power-domains
85 - power-domains
105 power-domains = <&spm MT8195_POWER_DOMAIN_VDEC1>;
128 power-domains = <&spm MT8195_POWER_DOMAIN_VDEC0>;
143 power-domains = <&spm MT8195_POWER_DOMAIN_VDEC1>;
158 power-domains = <&spm MT8195_POWER_DOMAIN_VDEC2>;
|
| D | mediatek,mt8195-jpegenc.yaml | 19 power-domains:
69 power-domains:
79 - power-domains
85 - power-domains
105 power-domains = <&spm MT8195_POWER_DOMAIN_VENC_CORE1>;
124 power-domains = <&spm MT8195_POWER_DOMAIN_VENC>;
137 power-domains = <&spm MT8195_POWER_DOMAIN_VENC_CORE1>;
|
| /Documentation/devicetree/bindings/dvfs/ |
| D | performance-domain.yaml | 7 title: Generic performance domains
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
25 devices with their performance domains provided by performance domain
27 the device tree and can provide one or more performance domains. A consumer
39 multiple performance domains (e.g. performance controllers), but can be
44 performance-domains:
77 performance-domains = <&performance 1>;
|
| /Documentation/devicetree/bindings/gpu/ |
| D | arm,mali-bifrost.yaml | 72 power-domains:
132 power-domains:
157 power-domains:
169 - power-domains
179 power-domains:
190 - power-domains
204 power-domains:
213 - power-domains
222 power-domains:
230 - power-domains
[all …]
|
| /Documentation/devicetree/bindings/nvme/ |
| D | apple,nvme-ans.yaml | 34 power-domains:
35 # two domains for t8103, three for t6000
74 power-domains:
80 power-domains:
90 - power-domains
110 power-domains = <&ps_ans2>, <&ps_apcie_st>;
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 6 domains of substantially similar mean performance relative to resources outside
11 From the platform view, these groups are also referred to as domains.
29 device tree properties are used to determine the NUMA distance between resource groups/domains.
32 representing the resource’s platform grouping domains.
42 Linux kernel computes NUMA distance between two domains by recursively comparing
43 if they belong to the same higher-level domains. For mismatch at every higher
45 comparing domains.
68 computing the distance of domain 8 from other domains present in the system. For the rest of
72 distance between resource groups/domains present in the system.
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,sm7150-camcc.yaml | 16 domains on SM7150.
30 power-domains:
38 - power-domains
55 power-domains = <&rpmhpd RPMHPD_CX>;
|
| D | qcom,sm7150-videocc.yaml | 16 domains on SM7150.
29 power-domains:
37 - power-domains
53 power-domains = <&rpmhpd RPMHPD_CX>;
|
| D | qcom,gcc-sc8180x.yaml | 14 domains on SC8180x.
34 power-domains:
42 - power-domains
61 power-domains = <&rpmhpd SC8180X_CX>;
|
| D | qcom,sm8350-videocc.yaml | 14 domains on Qualcomm SoCs.
32 power-domains:
45 - power-domains
64 power-domains = <&rpmhpd RPMHPD_MMCX>;
|
| D | qcom,qcm2290-gpucc.yaml | 14 domains on Qualcomm SoCs.
33 power-domains:
46 - power-domains
70 power-domains = <&rpmpd QCM2290_VDDCX>;
|
| D | qcom,sm6375-gpucc.yaml | 14 domains on Qualcomm SoCs.
30 power-domains:
43 - power-domains
68 power-domains = <&rpmpd SM6375_VDDGX>;
|
| /Documentation/devicetree/bindings/usb/ |
| D | generic-xhci.yaml | 25 - description: Broadcom SoCs with power domains
54 power-domains:
73 - power-domains
76 power-domains: false
|
| /Documentation/misc-devices/ |
| D | tps6594-pfsm.rst | 17 some voltage domains remain energized while others can be off.
44 no voltage domains are energized.
56 All voltage domains are energized in both MCU and Main processor
65 Depending on the triggers set, some DDR/GPIO voltage domains can
66 remain energized, while all other domains are off to minimize
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra186-display.yaml | 62 power-domains:
112 - power-domains
142 power-domains = <&bpmp TEGRA186_POWER_DOMAIN_DISP>;
158 power-domains = <&bpmp TEGRA186_POWER_DOMAIN_DISP>;
177 power-domains = <&bpmp TEGRA186_POWER_DOMAIN_DISPB>;
196 power-domains = <&bpmp TEGRA186_POWER_DOMAIN_DISPC>;
230 power-domains = <&bpmp TEGRA194_POWER_DOMAIN_DISP>;
246 power-domains = <&bpmp TEGRA194_POWER_DOMAIN_DISP>;
264 power-domains = <&bpmp TEGRA194_POWER_DOMAIN_DISPB>;
282 power-domains = <&bpmp TEGRA194_POWER_DOMAIN_DISPC>;
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | ti,sa2ul.yaml | 23 power-domains:
80 power-domains: false
83 - power-domains
94 power-domains = <&k3_pds 264 TI_SCI_PD_EXCLUSIVE>;
|
12345678910>>...34