Searched full:domains (Results 1 – 25 of 191) sorted by relevance
12345678
| /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
19 providing multiple PM domains (e.g. power controllers), but can be any value
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
38 not the idle states of the devices or sub-domains in the PM domain. Devices
39 and sub-domains have their own idle-states independent of the parent
[all …]
|
| D | pd-samsung.txt | 1 * Samsung Exynos Power Domains
3 Exynos processors include support for multiple power domains which are used
17 to let user to distinguish between multiple domains in SoC.
18 - power-domains: phandle pointing to the parent power domain, for more details
25 Node of a device using power domains must have a power-domains property
|
| D | rockchip-io-domain.txt | 1 Rockchip SRAM for IO Voltage Domains:
35 - "rockchip,px30-pmu-io-voltage-domain" for px30 pmu-domains
41 - "rockchip,rk3368-pmu-io-voltage-domain" for rk3368 pmu-domains
43 - "rockchip,rk3399-pmu-io-voltage-domain" for rk3399 pmu-domains
45 - "rockchip,rv1108-pmu-io-voltage-domain" for rv1108 pmu-domains
49 Systems should move the io-domains to a sub-node of the grf simple-mfd.
65 Possible supplies for PX30 pmu-domains:
107 Possible supplies for rk3368 pmu-domains:
117 Possible supplies for rk3399 pmu-domains:
122 io-domains {
|
| D | fsl,imx-gpcv2.txt | 5 Control (PGC) for various power domains.
18 Power domains contained within GPC node are generic power domain
66 IP cores belonging to a power domain should contain a 'power-domains'
75 power-domains = <&pgc_pcie_phy>;
|
| D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
60 pm-domains {
89 Hardware blocks belonging to a PM domain should contain a "power-domains"
98 power-domains = <&pd_a3sp>;
|
| /Documentation/devicetree/bindings/media/ |
| D | mediatek-mdp.txt | 19 - power-domains: a phandle to the power domain, see
41 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
52 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
61 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
68 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
75 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
82 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
91 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
100 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
|
| D | qcom,venus.txt | 38 - power-domains:
76 - power-domains:
99 power-domains = <&gcc VENUS_GDSC>;
107 power-domains = <&mmcc VENUS_CORE0_GDSC>;
114 power-domains = <&mmcc VENUS_CORE1_GDSC>;
|
| D | rockchip-vpu.txt | 17 - power-domains: phandle to power domain node
30 power-domains = <&power RK3288_PD_VIDEO>;
41 power-domains = <&power RK3328_PD_VPU>;
|
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,disp.txt | 70 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
78 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
88 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
98 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
108 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
118 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
128 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
138 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
148 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
156 power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
[all …]
|
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 1 * Rockchip Power Domains
3 Rockchip processors include support for multiple power domains which can be
20 Should be 1 for multiple PM domains.
104 Node of a device using power domains must have a power-domains property,
122 power-domains = <&power RK3288_PD_GPU>;
128 power-domains = <&power RK3368_PD_GPU_1>;
134 power-domains = <&power RK3399_PD_VOPB>;
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas,dbsc.txt | 10 domains, and prevent these PM domains from being powered down, which would
32 - power-domains: Must contain a reference to the PM domain that the memory
43 power-domains = <&pd_a4bc0>;
|
| D | mediatek,smi-larb.txt | 14 - power-domains : a phandle to the power domain of this local arbiter.
32 power-domains = <&scpsys MT8173_POWER_DOMAIN_VDEC>;
47 power-domains = <&scpsys MT2701_POWER_DOMAIN_DISP>;
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 2 Scheduler Domains
6 hierarchy is built from these base domains via the ->parent pointer. ->parent
39 at the time the scheduler_tick() happened and iterates over all sched domains
53 Implementing sched domains
77 arch_init_sched_domains function. This function will attach domains to all
80 The sched-domains debugging infrastructure can be enabled by enabling
81 CONFIG_SCHED_DEBUG. This enables an error checking parse of the sched domains
|
| D | sched-energy.rst | 85 for futher details about performance domains).
88 scheduling domains are built, or re-built. For each root domain (rd), the
89 scheduler maintains a singly linked list of all performance domains intersecting
93 The lists are attached to the root domains in order to cope with exclusive
95 necessarily match those of performance domains, the lists of different root
96 domains can contain duplicate elements.
99 Let us consider a platform with 12 CPUs, split in 3 performance domains
107 exclusive cpusets, hence creating two independent root domains, each
108 containing 6 CPUs. The two root domains are denoted rd1 and rd2 in the
151 Let us consider a (fake) platform with 2 independent performance domains
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,scpi.txt | 87 Power domain bindings for the power domains based on SCPI Message Protocol
98 - num-domains: Total number of power domains provided by SCPI. This is
106 - power-domains : A phandle and PM domain specifier as defined by bindings of
168 scpi_devpd: scpi-power-domains {
169 compatible = "arm,scpi-power-domains";
170 num-domains = <2>;
185 power-domains = <&scpi_devpd 1>;
217 The num-domains property in scpi-power-domains domain specifies that
218 SCPI provides 2 power domains. The hdlcd node uses the power domain with
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | hdmi.txt | 14 - power-domains: Should be <&mmcc MDSS_GDSC>.
27 - power-domains: reference to the power domain(s), if available.
50 - power-domains: Should be <&mmcc MDSS_GDSC>.
65 power-domains = <&mmcc MDSS_GDSC>;
94 power-domains = <&mmcc MDSS_GDSC>;
|
| D | gmu.txt | 27 - power-domains: should be:
30 - power-domain-names: Matching names for the power domains
57 power-domains = <&gpucc GPU_CX_GDSC>,
|
| /Documentation/s390/ |
| D | vfio-ap.rst | 52 An adapter is partitioned into domains. An adapter can hold up to 256 domains
61 * Usage domains are domains that are targeted by an AP instruction to
64 * Control domains are domains that are changed by an AP command sent to a
68 The AP usage and control domains are assigned to a given LPAR via the system's
71 domains assigned to the LPAR. The domain number of each usage domain and
76 significant bit, correspond to domains 0-255.
91 domains 6 and 71 (0x47) are assigned to the LPAR, the AP bus will create the
116 command; this must be one of the usage domains. An AP command may modify a
117 domain that is not one of the usage domains, but the modified domain
118 must be one of the control domains.
[all …]
|
| /Documentation/devicetree/bindings/soc/zte/ |
| D | pd-2967xx.txt | 1 * ZTE zx2967 family Power Domains
3 zx2967 family includes support for multiple power domains which are used
|
| /Documentation/devicetree/bindings/gpu/ |
| D | nvidia,gk20a.txt | 19 power domains.
32 - power-domains: GPUs that make use of power domains can define this property
88 power-domains = <&bpmp TEGRA186_POWER_DOMAIN_GPU>;
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | raspberrypi,bcm2835-power.txt | 7 - #power-domain-cells: Should be <1>, we providing multiple power domains.
46 power-domains = <&power RPI_POWER_DOMAIN_USB>;
|
| /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"
41 domains {
|
| /Documentation/devicetree/bindings/clock/ |
| D | exynos5433-clock.txt | 11 domains and bus clocks.
180 - power-domains: a phandle to respective power domain node as described by
286 power-domains = <&pd_g2d>;
312 power-domains = <&pd_disp>;
322 power-domains = <&pd_aud>;
359 power-domains = <&pd_g3d>;
373 power-domains = <&pd_gscl>;
405 power-domains = <&pd_mscl>;
415 power-domains = <&pd_mfc>;
425 power-domains = <&pd_hevc>;
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | mediatek-crypto.txt | 10 - power-domains: Must contain a reference to the PM domain.
24 power-domains = <&scpsys MT2701_POWER_DOMAIN_ETH>;
|
12345678