Home
last modified time | relevance | path

Searched refs:domains (Results 1 – 141 of 141) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/
Dpower_domain.txt3 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>
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dpower_domain.txt1 * 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
54 power-domains = <&parent 0>;
65 - power-domains : A phandle and PM domain specifier as defined by bindings of
[all …]
Dpd-samsung.txt3 Exynos processors include support for multiple power domains which are used
18 all domains which are powered on and off and not required for unused
19 domains.
29 - power-domains: phandle pointing to the parent power domain, for more details
32 Node of a device using power domains must have a power-domains property
Drenesas,sysc-rmobile.txt23 - 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>;
Dfsl,imx-gpc.txt6 domains.
42 IP cores belonging to a power domain should contain a 'power-domains' property
51 power-domains = <&gpc 1>;
Drockchip-io-domain.txt37 - "rockchip,rk3368-pmu-io-voltage-domain" for rk3368 pmu-domains
78 Possible supplies for rk3368 pmu-domains:
84 io-domains {
/linux-4.4.14/arch/arm/boot/dts/
Dr8a7794.dtsi75 power-domains = <&cpg_clocks>;
88 power-domains = <&cpg_clocks>;
101 power-domains = <&cpg_clocks>;
114 power-domains = <&cpg_clocks>;
127 power-domains = <&cpg_clocks>;
140 power-domains = <&cpg_clocks>;
153 power-domains = <&cpg_clocks>;
163 power-domains = <&cpg_clocks>;
183 power-domains = <&cpg_clocks>;
214 power-domains = <&cpg_clocks>;
[all …]
Dr8a7740.dtsi28 power-domains = <&pd_a3sm>;
43 power-domains = <&pd_a4s>;
53 power-domains = <&pd_d4>;
62 power-domains = <&pd_c5>;
88 power-domains = <&pd_a4s>;
110 power-domains = <&pd_a4s>;
132 power-domains = <&pd_a4s>;
154 power-domains = <&pd_a4s>;
163 power-domains = <&pd_a4s>;
180 power-domains = <&pd_a4r>;
[all …]
Dr8a7791.dtsi94 power-domains = <&cpg_clocks>;
107 power-domains = <&cpg_clocks>;
120 power-domains = <&cpg_clocks>;
133 power-domains = <&cpg_clocks>;
146 power-domains = <&cpg_clocks>;
159 power-domains = <&cpg_clocks>;
172 power-domains = <&cpg_clocks>;
185 power-domains = <&cpg_clocks>;
193 power-domains = <&cpg_clocks>;
211 power-domains = <&cpg_clocks>;
[all …]
Dr8a7779.dtsi176 power-domains = <&cpg_clocks>;
187 power-domains = <&cpg_clocks>;
198 power-domains = <&cpg_clocks>;
209 power-domains = <&cpg_clocks>;
219 power-domains = <&cpg_clocks>;
229 power-domains = <&cpg_clocks>;
239 power-domains = <&cpg_clocks>;
249 power-domains = <&cpg_clocks>;
259 power-domains = <&cpg_clocks>;
269 power-domains = <&cpg_clocks>;
[all …]
Dr8a7790.dtsi137 power-domains = <&cpg_clocks>;
150 power-domains = <&cpg_clocks>;
163 power-domains = <&cpg_clocks>;
176 power-domains = <&cpg_clocks>;
189 power-domains = <&cpg_clocks>;
202 power-domains = <&cpg_clocks>;
210 power-domains = <&cpg_clocks>;
228 power-domains = <&cpg_clocks>;
248 power-domains = <&cpg_clocks>;
265 power-domains = <&cpg_clocks>;
[all …]
Dr7s72100.dtsi161 power-domains = <&cpg_clocks>;
174 power-domains = <&cpg_clocks>;
187 power-domains = <&cpg_clocks>;
200 power-domains = <&cpg_clocks>;
213 power-domains = <&cpg_clocks>;
226 power-domains = <&cpg_clocks>;
239 power-domains = <&cpg_clocks>;
252 power-domains = <&cpg_clocks>;
264 power-domains = <&cpg_clocks>;
279 power-domains = <&cpg_clocks>;
[all …]
Dr8a73a4.dtsi31 power-domains = <&pd_a2sl>;
37 power-domains = <&pd_d4>;
51 power-domains = <&pd_a3bc>;
57 power-domains = <&pd_a3bc>;
100 power-domains = <&pd_a3sp>;
111 power-domains = <&pd_a3sp>;
122 power-domains = <&pd_c5>;
167 power-domains = <&pd_c4>;
202 power-domains = <&pd_c4>;
233 power-domains = <&pd_c5>;
[all …]
Dsh73a0.dtsi30 power-domains = <&pd_a2sl>;
37 power-domains = <&pd_a2sl>;
62 power-domains = <&pd_a4bc1>;
71 power-domains = <&pd_a4bc0>;
86 power-domains = <&pd_c5>;
111 power-domains = <&pd_a4s>;
133 power-domains = <&pd_a4s>;
155 power-domains = <&pd_a4s>;
177 power-domains = <&pd_a4s>;
191 power-domains = <&pd_a3sp>;
[all …]
Dr8a7778.dtsi56 power-domains = <&cpg_clocks>;
156 power-domains = <&cpg_clocks>;
167 power-domains = <&cpg_clocks>;
178 power-domains = <&cpg_clocks>;
189 power-domains = <&cpg_clocks>;
201 power-domains = <&cpg_clocks>;
216 power-domains = <&cpg_clocks>;
231 power-domains = <&cpg_clocks>;
299 power-domains = <&cpg_clocks>;
309 power-domains = <&cpg_clocks>;
[all …]
Dexynos4.dtsi107 power-domains = <&pd_lcd0>;
165 power-domains = <&pd_lcd0>;
190 power-domains = <&pd_cam>;
202 power-domains = <&pd_cam>;
214 power-domains = <&pd_cam>;
226 power-domains = <&pd_cam>;
239 power-domains = <&pd_cam>;
254 power-domains = <&pd_cam>;
420 power-domains = <&pd_mfc>;
696 power-domains = <&pd_lcd0>;
[all …]
Dexynos4x12.dtsi132 power-domains = <&pd_isp>;
143 power-domains = <&pd_isp>;
154 power-domains = <&pd_isp>;
225 power-domains = <&pd_isp>;
236 power-domains = <&pd_isp>;
247 power-domains = <&pd_isp>;
258 power-domains = <&pd_isp>;
269 power-domains = <&pd_isp>;
280 power-domains = <&pd_isp>;
Dexynos5250.dtsi265 power-domains = <&pd_mfc>;
721 power-domains = <&pd_gsc>;
731 power-domains = <&pd_gsc>;
741 power-domains = <&pd_gsc>;
751 power-domains = <&pd_gsc>;
760 power-domains = <&pd_disp1>;
773 power-domains = <&pd_disp1>;
822 power-domains = <&pd_mfc>;
833 power-domains = <&pd_mfc>;
854 power-domains = <&pd_gsc>;
[all …]
Dste-dbx5x0.dtsi217 compatible = "stericsson,ux500-pm-domains";
830 power-domains = <&pm_domains DOMAIN_VAPE>;
846 power-domains = <&pm_domains DOMAIN_VAPE>;
862 power-domains = <&pm_domains DOMAIN_VAPE>;
878 power-domains = <&pm_domains DOMAIN_VAPE>;
894 power-domains = <&pm_domains DOMAIN_VAPE>;
908 power-domains = <&pm_domains DOMAIN_VAPE>;
922 power-domains = <&pm_domains DOMAIN_VAPE>;
937 power-domains = <&pm_domains DOMAIN_VAPE>;
952 power-domains = <&pm_domains DOMAIN_VAPE>;
[all …]
Dr8a7793.dtsi71 power-domains = <&cpg_clocks>;
91 power-domains = <&cpg_clocks>;
114 power-domains = <&cpg_clocks>;
123 power-domains = <&cpg_clocks>;
133 power-domains = <&cpg_clocks>;
142 power-domains = <&cpg_clocks>;
Dexynos5420.dtsi180 power-domains = <&mfc_pd>;
702 power-domains = <&disp_pd>;
716 power-domains = <&disp_pd>;
726 power-domains = <&gsc_pd>;
736 power-domains = <&gsc_pd>;
978 power-domains = <&disp_pd>;
989 power-domains = <&gsc_pd>;
1000 power-domains = <&gsc_pd>;
1088 power-domains = <&mfc_pd>;
1099 power-domains = <&mfc_pd>;
[all …]
Dexynos3250.dtsi268 power-domains = <&pd_cam>;
282 power-domains = <&pd_cam>;
293 power-domains = <&pd_lcd0>;
304 power-domains = <&pd_lcd0>;
320 power-domains = <&pd_lcd0>;
417 power-domains = <&pd_mfc>;
428 power-domains = <&pd_mfc>;
Dexynos4210.dtsi246 power-domains = <&pd_lcd0>;
257 power-domains = <&pd_lcd1>;
Drk3288.dtsi789 power-domains = <&power RK3288_PD_VIO>;
811 power-domains = <&power RK3288_PD_VIO>;
822 power-domains = <&power RK3288_PD_VIO>;
844 power-domains = <&power RK3288_PD_VIO>;
857 power-domains = <&power RK3288_PD_VIO>;
Drk3288-firefly.dtsi66 io_domains: io-domains {
Drk3288-popmetal.dts82 io_domains: io-domains {
Drk3288-veyron.dtsi86 io_domains: io-domains {
Dexynos4415.dtsi278 power-domains = <&pd_lcd0>;
Ddove.dtsi435 domains {
Dimx6qdl.dtsi405 power-domains = <&gpc 1>;
/linux-4.4.14/Documentation/devicetree/bindings/soc/rockchip/
Dpower_domain.txt3 Rockchip processors include support for multiple power domains which can be
10 Should be 1 for multiple PM domains.
34 Node of a device using power domains must have a power-domains property,
44 power-domains = <&power RK3288_PD_GPU>;
/linux-4.4.14/drivers/powercap/
Dintel_rapl.c178 struct rapl_domain *domains; /* array of domains, sized at runtime */ member
283 kfree(p->domains); in rapl_cleanup_data()
335 rp->domains = NULL; in release_zone()
600 struct rapl_domain *rd = rp->domains; in rapl_init_domains()
1122 rp->domains[dmn].name); in rapl_update_domain_data()
1125 if (!rapl_read_data_raw(&rp->domains[dmn], prim, in rapl_update_domain_data()
1128 rp->domains[dmn].rdd.primitives[prim] = in rapl_update_domain_data()
1146 for (rd = rp->domains; rd < rp->domains + rp->nr_domains; in rapl_unregister_powercap()
1181 for (rd = rp->domains; rd < rp->domains + rp->nr_domains; rd++) { in rapl_package_register_powercap()
1213 for (rd = rp->domains; rd < rp->domains + rp->nr_domains; rd++) { in rapl_package_register_powercap()
[all …]
DKconfig27 In RAPL, the platform level settings are divided into domains for
28 fine grained control. These domains include processor package, DRAM
/linux-4.4.14/drivers/pci/hotplug/
Drpaphp_core.c174 const int *indexes, *names, *types, *domains; in get_children_props() local
179 domains = of_get_property(dn, "ibm,drc-power-domains", NULL); in get_children_props()
181 if (!indexes || !names || !types || !domains) { in get_children_props()
194 *drc_power_domains = domains; in get_children_props()
207 const int *types, *domains; in rpaphp_get_drc_props() local
218 rc = get_children_props(dn->parent, &indexes, &names, &types, &domains); in rpaphp_get_drc_props()
236 *drc_power_domain = be32_to_cpu(domains[i+1]); in rpaphp_get_drc_props()
/linux-4.4.14/drivers/soc/mediatek/
Dmtk-scpsys.c185 struct scp_domain domains[NUM_DOMAINS]; member
422 pd_data->domains = devm_kzalloc(&pdev->dev, in scpsys_probe()
423 sizeof(*pd_data->domains) * NUM_DOMAINS, GFP_KERNEL); in scpsys_probe()
424 if (!pd_data->domains) in scpsys_probe()
454 struct scp_domain *scpd = &scp->domains[i]; in scpsys_probe()
458 pd_data->domains[i] = genpd; in scpsys_probe()
492 ret = pm_genpd_add_subdomain(pd_data->domains[MT8173_POWER_DOMAIN_MFG_ASYNC], in scpsys_probe()
493 pd_data->domains[MT8173_POWER_DOMAIN_MFG_2D]); in scpsys_probe()
497 ret = pm_genpd_add_subdomain(pd_data->domains[MT8173_POWER_DOMAIN_MFG_2D], in scpsys_probe()
498 pd_data->domains[MT8173_POWER_DOMAIN_MFG]); in scpsys_probe()
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Drenesas-memory-controllers.txt10 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>;
/linux-4.4.14/drivers/gpu/drm/i915/
Dintel_runtime_pm.c60 if ((power_well)->domains & (domain_mask))
66 if ((power_well)->domains & (domain_mask))
1575 .domains = POWER_DOMAIN_MASK,
1598 .domains = HSW_ALWAYS_ON_POWER_DOMAINS,
1603 .domains = HSW_DISPLAY_POWER_DOMAINS,
1612 .domains = BDW_ALWAYS_ON_POWER_DOMAINS,
1617 .domains = BDW_DISPLAY_POWER_DOMAINS,
1647 .domains = VLV_ALWAYS_ON_POWER_DOMAINS,
1652 .domains = VLV_DISPLAY_POWER_DOMAINS,
1658 .domains = VLV_DPIO_TX_B_LANES_01_POWER_DOMAINS |
[all …]
Di915_drv.h692 enum forcewake_domains domains);
694 enum forcewake_domains domains);
1233 unsigned long domains; member
2730 enum forcewake_domains domains);
2732 enum forcewake_domains domains);
2737 enum forcewake_domains domains);
2739 enum forcewake_domains domains);
Dintel_display.c5329 unsigned long domains, new_domains, old_domains; in modeset_get_crtc_power_domains() local
5334 domains = new_domains & ~old_domains; in modeset_get_crtc_power_domains()
5336 for_each_power_domain(domain, domains) in modeset_get_crtc_power_domains()
5343 unsigned long domains) in modeset_put_power_domains() argument
5347 for_each_power_domain(domain, domains) in modeset_put_power_domains()
6319 unsigned long domains; in intel_crtc_disable_noatomic() local
6337 domains = intel_crtc->enabled_power_domains; in intel_crtc_disable_noatomic()
6338 for_each_power_domain(domain, domains) in intel_crtc_disable_noatomic()
Di915_debugfs.c2768 if (!(BIT(power_domain) & power_well->domains)) in i915_power_domain_info()
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
Dscpsys.txt11 power/power_domain.txt. It provides the power domains defined in
22 before enabling certain power domains.
42 power-domains = <&scpsys MT8173_POWER_DOMAIN_AUDIO>;
/linux-4.4.14/drivers/clk/qcom/
Dgdsc.c214 data->domains = devm_kcalloc(dev, num, sizeof(*data->domains), in gdsc_register()
216 if (!data->domains) in gdsc_register()
228 data->domains[i] = &scs[i]->pd; in gdsc_register()
/linux-4.4.14/Documentation/scheduler/
D00-INDEX9 sched-domains.txt
10 - information on scheduling domains.
Dsched-domains.txt2 hierarchy is built from these base domains via the ->parent pointer. ->parent
35 at the time the scheduler_tick() happened and iterates over all sched domains
49 *** Implementing sched domains ***
71 arch_init_sched_domains function. This function will attach domains to all
74 The sched-domains debugging infrastructure can be enabled by enabling
75 CONFIG_SCHED_DEBUG. This enables an error checking parse of the sched domains
Dsched-stats.txt9 per-domain. Note that domains (and their associated information) will only
60 CONFIG_SMP is not defined, *no* domains are utilized and these lines
/linux-4.4.14/drivers/soc/rockchip/
Dpm_domains.c61 struct generic_pm_domain *domains[]; member
304 pmu->genpd_data.domains[id] = &pd->genpd; in rockchip_pm_add_one_domain()
339 genpd = pmu->genpd_data.domains[i]; in rockchip_pm_domain_cleanup()
385 pmu_info->num_domains * sizeof(pmu->domains[0]), in rockchip_pm_domain_probe()
395 pmu->genpd_data.domains = pmu->domains; in rockchip_pm_domain_probe()
/linux-4.4.14/Documentation/tpm/
Dxen-tpmfront.txt17 these domains (manager, vTPM, and guest) is trusted, the vTPM subsystem extends
20 separation guaranteed by the hypervisor. The vTPM domains are implemented in
85 domains such as pv-grub that talk to the vTPM domain.
106 the vTPM and vTPM Manager stub domains. Once the stub domains are running, a
/linux-4.4.14/drivers/pinctrl/meson/
Dpinctrl-meson.c110 d = &pc->domains[i]; in meson_get_domain_and_bank()
207 domain = &pc->domains[group->domain]; in meson_pmx_disable_other_groups()
222 struct meson_domain *domain = &pc->domains[group->domain]; in meson_pmx_set_mux()
562 domain = &pc->domains[i]; in meson_gpiolib_register()
597 gpiochip_remove(&pc->domains[i].chip); in meson_gpiolib_register()
664 pc->domains = devm_kzalloc(pc->dev, num_domains * in meson_pinctrl_parse_dt()
666 if (!pc->domains) in meson_pinctrl_parse_dt()
673 domain = &pc->domains[i]; in meson_pinctrl_parse_dt()
Dpinctrl-meson.h155 struct meson_domain *domains; member
/linux-4.4.14/drivers/pinctrl/samsung/
Dpinctrl-s3c64xx.c208 struct irq_domain *domains[NUM_EINT0]; member
229 struct irq_domain *domains[]; member
439 virq = irq_linear_revmap(data->domains[group], pin); in s3c64xx_eint_gpio_irq()
492 + nr_domains * sizeof(*data->domains), GFP_KERNEL); in s3c64xx_eint_gpio_init()
505 data->domains[nr_domains++] = bank->irq_domain; in s3c64xx_eint_gpio_init()
621 virq = irq_linear_revmap(data->domains[irq], data->pins[irq]); in s3c64xx_irq_demux_eint()
768 data->domains[irq] = bank->irq_domain; in s3c64xx_eint_eint0_init()
Dpinctrl-s3c24xx.c95 struct irq_domain *domains[NUM_EINT]; member
250 virq = irq_linear_revmap(eint_data->domains[data->hwirq], data->hwirq); in s3c2410_demux_eint0_3()
308 virq = irq_linear_revmap(eint_data->domains[data->hwirq], data->hwirq); in s3c2412_demux_eint0_3()
381 virq = irq_linear_revmap(data->domains[irq], irq - offset); in s3c24xx_demux_eint()
553 eint_data->domains[irq] = bank->irq_domain; in s3c24xx_eint_init()
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Drenesas,r8a7778-cpg-clocks.txt19 "power-domains" property, as documented by the generic PM domain bindings in
46 power-domains = <&cpg_clocks>;
Drenesas,r8a7779-cpg-clocks.txt21 "power-domains" property, as documented by the generic PM domain bindings in
48 power-domains = <&cpg_clocks>;
Drenesas,rz-cpg-clocks.txt23 "power-domains" property, as documented by the generic PM domain bindings in
52 power-domains = <&cpg_clocks>;
Drenesas,rcar-gen2-cpg-clocks.txt29 "power-domains" property, as documented by the generic PM domain bindings in
58 power-domains = <&cpg_clocks>;
Drenesas,cpg-mssr.txt37 node in their "power-domains" property, as documented by the generic PM
67 power-domains = <&cpg>;
Dexynos4415-clock.txt10 (CMU_LEFTBUS, CMU_RIGHTBUS, CMU_TOP, CMU_CPU clock domains).
Dexynos5433-clock.txt11 domains and bus clocks.
/linux-4.4.14/arch/x86/xen/
DKconfig32 Limit paravirtualized user domains to 512GB of RAM.
35 pv-domains with more than 512 GB of RAM. This option controls the
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Dedp.txt11 - power-domains: Should be <&mmcc MDSS_GDSC>.
42 power-domains = <&mmcc MDSS_GDSC>;
Dhdmi.txt25 - power-domains: reference to the power domain(s), if available.
40 power-domains = <&mmcc MDSS_GDSC>;
Ddsi.txt13 - power-domains: Should be <&mmcc MDSS_GDSC>.
62 - power-domains: Should be <&mmcc MDSS_GDSC>.
81 power-domains = <&mmcc MDSS_GDSC>;
/linux-4.4.14/Documentation/devicetree/bindings/bus/
Dsimple-pm-bus.txt27 - power-domains: Must contain a reference to the PM domain.
43 power-domains = <&pd_a4s>;
Drenesas,bsc.txt31 - power-domains: Must contain a reference to the PM domain, if available.
45 power-domains = <&pd_a4s>;
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt48 - power-domains: Required if the System MMU is needed to gate its power.
57 power-domains = <&pd_gsc>;
69 power-domains = <&pd_gsc>;
/linux-4.4.14/Documentation/devicetree/bindings/media/
Ds5p-mfc.txt31 - power-domains : power-domain property defined with a phandle
41 power-domains = <&pd_mfc>;
/linux-4.4.14/Documentation/trace/
Devents-power.txt10 o Power domains related changes and transitions
57 3. Power domains events
59 The power domain events are used for power domains transitions
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/clk/
Dbase.c141 const struct nvkm_domain *domain = clk->domains; in nvkm_cstate_new()
253 const struct nvkm_domain *clock = clk->domains - 1; in nvkm_pstate_info()
310 const struct nvkm_domain *domain = clk->domains - 1; in nvkm_pstate_new()
499 const struct nvkm_domain *clock = clk->domains; in nvkm_clk_init()
565 clk->domains = func->domains; in nvkm_clk_ctor()
Dg84.c32 .domains = {
Dpriv.h15 struct nvkm_domain domains[]; member
Dnv04.c69 .domains = {
Dnv40.c210 .domains = {
Dmcp77.c403 .domains = {
Dgf100.c440 .domains = {
Dgt215.c523 .domains = {
Dgk104.c485 .domains = {
Dnv50.c547 .domains = {
Dgk20a.c639 .domains = {
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_gem.c181 if (args->in.domains & (AMDGPU_GEM_DOMAIN_GDS | in amdgpu_gem_create_ioctl()
184 if (args->in.domains == AMDGPU_GEM_DOMAIN_GDS) in amdgpu_gem_create_ioctl()
186 else if (args->in.domains == AMDGPU_GEM_DOMAIN_GWS) in amdgpu_gem_create_ioctl()
188 else if (args->in.domains == AMDGPU_GEM_DOMAIN_OA) in amdgpu_gem_create_ioctl()
198 (u32)(0xffffffff & args->in.domains), in amdgpu_gem_create_ioctl()
634 info.domains = robj->initial_domain; in amdgpu_gem_op_ioctl()
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Drenesas,intc-irqpin.txt34 - power-domains: Must contain a reference to the power domain. This property is
61 power-domains = <&pd_a4s>;
Darm,gic.txt72 - power-domains : A phandle and PM domain specifier as defined by bindings of
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/engine/
Dpm.h11 struct list_head domains; member
/linux-4.4.14/Documentation/networking/
Dregulatory.txt11 Keeping regulatory domains in userspace
14 Due to the dynamic nature of regulatory domains we keep them
19 How to get regulatory domains to the kernel
24 expected regulatory domains will be respected by the kernel.
43 Who asks for regulatory domains?
Dpolicy-routing.txt98 domains. Unfortunately, it is not widely used in the Internet.
De100.txt166 (2) installing the interfaces in separate broadcast domains (either
Dvrf.txt4 routing and forwarding domains (aka VRFs, VRF-lite to be specific) in the
Dixgb.txt402 - Install the interfaces in separate broadcast domains - either in
/linux-4.4.14/Documentation/devicetree/bindings/arm/rockchip/
Dpmu.txt4 The pmu is used to turn off and on different power domains of the SoCs
/linux-4.4.14/kernel/irq/
DKconfig25 # and should not be used in new code. Use irq domains instead.
62 # Support for hierarchical irq domains
/linux-4.4.14/arch/arm/mach-ux500/
Dpm_domains.c71 genpd_data->domains = ux500_pm_domains; in ux500_pm_domains_init()
/linux-4.4.14/arch/arm/mach-omap1/
Dsleep.S97 @ turn off clock domains
182 @ turn off clock domains
252 @ Turn off clock domains
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/pm/
Dbase.c39 list_for_each_entry(dom, &pm->domains, head) in nvkm_pm_count_perfdom()
65 list_for_each_entry(dom, &pm->domains, head) { in nvkm_perfdom_find()
253 list_for_each_entry(dom, &pm->domains, head) in nvkm_perfdom_sample()
794 list_add_tail(&dom->head, &pm->domains); in nvkm_perfdom_new()
836 list_for_each_entry_safe(dom, next_dom, &pm->domains, head) { in nvkm_pm_dtor()
862 INIT_LIST_HEAD(&pm->domains); in nvkm_pm_ctor()
/linux-4.4.14/drivers/xen/
DKconfig81 other domains. This makes sure that any confidential data
82 is not accidentally visible to other domains. Is it more
108 The xen filesystem provides a way for domains to share
154 to other domains. This can be used to implement frontend drivers
198 Only needed for systems running as XEN driver domains (e.g. Dom0) and
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos_dsim.txt26 - power-domains: a phandle to DSIM power domain node
67 power-domains = <&pd_lcd0>;
Dsamsung-fimd.txt41 - power-domains: a phandle to FIMD power domain node.
100 power-domains = <&pd_lcd0>;
/linux-4.4.14/drivers/iommu/
Dintel-iommu.c617 struct dmar_domain **domains; in get_iommu_domain() local
620 domains = iommu->domains[idx]; in get_iommu_domain()
621 if (!domains) in get_iommu_domain()
624 return domains[did & 0xff]; in get_iommu_domain()
630 struct dmar_domain **domains; in set_iommu_domain() local
633 if (!iommu->domains[idx]) { in set_iommu_domain()
635 iommu->domains[idx] = kzalloc(size, GFP_ATOMIC); in set_iommu_domain()
638 domains = iommu->domains[idx]; in set_iommu_domain()
639 if (WARN_ON(!domains)) in set_iommu_domain()
642 domains[did & 0xff] = domain; in set_iommu_domain()
[all …]
/linux-4.4.14/net/wireless/
Ddb.txt12 # regulatory rules that cover the regulatory domains you will be using. Your
/linux-4.4.14/drivers/power/avs/
DKconfig18 Say y here to enable support io domains on Rockchip SoCs. It is
/linux-4.4.14/Documentation/power/regulator/
Doverview.txt59 That is one regulator and three power domains:
76 This gives us two regulators and two power domains:
157 voltage/current domains (with constraints) for each regulator. It can
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Dclk.h77 const struct nvkm_domain *domains; member
/linux-4.4.14/drivers/gpu/drm/nouveau/
Dnouveau_gem.c294 uint32_t domains = valid_domains & nvbo->valid_domains & in nouveau_gem_set_domain() local
298 if (!domains) in nouveau_gem_set_domain()
307 if ((domains & NOUVEAU_GEM_DOMAIN_VRAM) && in nouveau_gem_set_domain()
311 else if ((domains & NOUVEAU_GEM_DOMAIN_GART) && in nouveau_gem_set_domain()
315 else if (domains & NOUVEAU_GEM_DOMAIN_VRAM) in nouveau_gem_set_domain()
/linux-4.4.14/Documentation/power/
Dopp.txt22 facilitate this, sub-modules in a SoC are grouped into domains, allowing some
23 domains to run at lower voltage and frequency while other domains run at
310 Typically an SoC contains multiple voltage domains which are variable. Each
325 representing the actual OPPs and domains are internal to the OPP library itself
Ddevices.txt137 writers of device drivers whose subsystems (PM domains, device types, device
300 This allows PM domains and device types to override callbacks provided by bus
612 Support for power domains is provided through the pm_domain field of struct
625 The support for device power management domains is only relevant to platforms
628 support for power domains into subsystem-level callbacks, for example by
/linux-4.4.14/arch/arm/mach-zx/
Dzx296702-pm-domain.c162 genpd_data->domains = zx296702_pm_domains; in zx296702_pd_probe()
/linux-4.4.14/Documentation/cgroups/
Dcpusets.txt386 domains such that it only load balances within each sched domain.
388 no two sched domains overlap; some CPUs might not be in any sched
391 Put simply, it costs less to balance between two smaller sched domains
393 two domains won't be load balanced to the other one.
441 There is an impedance mismatch here, between cpusets and sched domains.
442 Cpusets are hierarchical and nest. Sched domains are flat; they don't
445 It is necessary for sched domains to be flat because load balancing
492 domains as it can while still providing load balancing for any set
502 scheduler sched domain setup code, to have the sched domains rebuilt
511 This partition exactly defines what sched domains the scheduler should
[all …]
Dblkio-controller.txt383 mechanism. Writeback sits between the memory and IO domains and
/linux-4.4.14/Documentation/vm/
Dnuma100 NUMA topology of the platform--embodied in the "scheduling domains" data
101 structures [see Documentation/scheduler/sched-domains.txt]--and the scheduler
102 attempts to minimize task migration to distant scheduling domains. However,
/linux-4.4.14/include/linux/
Dpm_domain.h184 struct generic_pm_domain **domains; member
Dintel-iommu.h415 struct dmar_domain ***domains; /* ptr to domains */ member
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dmeson,pinctrl.txt9 The 2 power domains of the controller (regular and always-on) are
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/device/
Dctrl.c93 domain = clk->domains; in nvkm_control_mthd_pstate_attr()
/linux-4.4.14/Documentation/sysctl/
DREADME58 abi/ execution domains & personalities
/linux-4.4.14/Documentation/devicetree/bindings/net/
Drenesas,ravb.txt76 power-domains = <&cpg_clocks>;
/linux-4.4.14/Documentation/hwmon/
Dasc762160 PECI Extended configuration allows for having more than two domains per
296 1 Processor contains two domains (0,1)
/linux-4.4.14/drivers/pci/
DKconfig69 PCI devices from a PCI backend to support PCI driver domains.
/linux-4.4.14/include/uapi/drm/
Damdgpu_drm.h83 uint64_t domains; member
/linux-4.4.14/Documentation/
DIntel-IOMMU.txt49 Different DMA engines may support different number of domains.
DIRQ-domain.txt145 A typical use case for simple domains is where an irqchip provider
D00-INDEX43 - info on interrupt numbering and setting up IRQ domains.
Dkernel-parameters.txt2744 root domains (aka PCI segments, in ACPI-speak).
2911 Keep all power-domains already enabled by bootloader on,
4158 domains.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcpus.txt240 the cpu-core power-domains.
243 power domains.
/linux-4.4.14/arch/arm/mach-imx/
Dgpc.c393 .domains = imx_gpc_domains,
/linux-4.4.14/Documentation/filesystems/
Ddlmfs.txt56 Once you're heartbeating, DLM lock 'domains' can be easily created /
/linux-4.4.14/Documentation/arm/
Dtcm.txt74 device state when shutting off device power domains.
/linux-4.4.14/Documentation/power/powercap/
Dpowercap.txt196 It is possible that some domains have both power ranges and energy counter ranges;
/linux-4.4.14/Documentation/DocBook/
Dgpu.xml.db525 API-intel-power-domains-init
526 API-intel-power-domains-fini
527 API-intel-power-domains-init-hw
/linux-4.4.14/arch/arm64/boot/dts/mediatek/
Dmt8173.dtsi442 power-domains = <&scpsys MT8173_POWER_DOMAIN_AUDIO>;
/linux-4.4.14/drivers/base/power/
Ddomain.c1604 if (!genpd_data->domains[idx]) in __of_genpd_xlate_onecell()
1607 return genpd_data->domains[idx]; in __of_genpd_xlate_onecell()
/linux-4.4.14/kernel/
Dcpuset.c619 static int generate_sched_domains(cpumask_var_t **domains, in generate_sched_domains() argument
783 *domains = doms; in generate_sched_domains()
/linux-4.4.14/Documentation/s390/
Dmonreader.txt129 data), the monitor domains contained within it and the start and end address
/linux-4.4.14/Documentation/sound/alsa/soc/
Ddapm.txt22 There are 4 power domains within DAPM
/linux-4.4.14/drivers/regulator/
DKconfig698 for different voltage domains
707 for different voltage domains
/linux-4.4.14/kernel/power/
DKconfig272 representing individual voltage domains and provides SOC
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt23 technologies are working in their own isolated domains or at best
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt11 domains (for example VRAM vs system memory), and so on. And with
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt131 derived from different clock domains like your main system clock (provided
/linux-4.4.14/drivers/net/
DKconfig395 Xen domains. These devices can be accessed by any operating
/linux-4.4.14/Documentation/PCI/
Dpci.txt583 in the kernel as they aren't compatible with hotplug or PCI domains or
/linux-4.4.14/Documentation/security/
DSmack.txt311 This scheme organizes users, programs, and data into domains that are
/linux-4.4.14/arch/arm/
DKconfig1691 bool "Enable use of CPU domains to implement privileged no-access"
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt1284 mapping documentation for a detailed description of domains.