Home
last modified time | relevance | path

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

/linux-4.1.27/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.1.27/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 …]
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.txt70 io-domains {
/linux-4.1.27/drivers/gpu/drm/i915/
Dintel_runtime_pm.c57 if ((power_well)->domains & (domain_mask))
63 if ((power_well)->domains & (domain_mask))
1016 .domains = POWER_DOMAIN_MASK,
1039 .domains = HSW_ALWAYS_ON_POWER_DOMAINS,
1044 .domains = HSW_DISPLAY_POWER_DOMAINS,
1053 .domains = BDW_ALWAYS_ON_POWER_DOMAINS,
1058 .domains = BDW_DISPLAY_POWER_DOMAINS,
1088 .domains = VLV_ALWAYS_ON_POWER_DOMAINS,
1093 .domains = VLV_DISPLAY_POWER_DOMAINS,
1099 .domains = VLV_DPIO_TX_B_LANES_01_POWER_DOMAINS |
[all …]
Di915_drv.h618 enum forcewake_domains domains);
620 enum forcewake_domains domains);
1113 unsigned long domains; member
2520 enum forcewake_domains domains);
2522 enum forcewake_domains domains);
Dintel_display.c5509 unsigned long domains; in intel_crtc_control() local
5513 domains = get_crtc_power_domains(crtc); in intel_crtc_control()
5514 for_each_power_domain(domain, domains) in intel_crtc_control()
5516 intel_crtc->enabled_power_domains = domains; in intel_crtc_control()
5524 domains = intel_crtc->enabled_power_domains; in intel_crtc_control()
5525 for_each_power_domain(domain, domains) in intel_crtc_control()
Di915_debugfs.c2481 if (!(BIT(power_domain) & power_well->domains)) in i915_power_domain_info()
/linux-4.1.27/arch/arm/boot/dts/
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 …]
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>;
166 power-domains = <&pd_c4>;
200 power-domains = <&pd_c4>;
224 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 …]
Dste-dbx5x0.dtsi48 compatible = "stericsson,ux500-pm-domains";
644 power-domains = <&pm_domains DOMAIN_VAPE>;
660 power-domains = <&pm_domains DOMAIN_VAPE>;
676 power-domains = <&pm_domains DOMAIN_VAPE>;
692 power-domains = <&pm_domains DOMAIN_VAPE>;
708 power-domains = <&pm_domains DOMAIN_VAPE>;
722 power-domains = <&pm_domains DOMAIN_VAPE>;
736 power-domains = <&pm_domains DOMAIN_VAPE>;
751 power-domains = <&pm_domains DOMAIN_VAPE>;
766 power-domains = <&pm_domains DOMAIN_VAPE>;
[all …]
Dexynos4.dtsi108 power-domains = <&pd_lcd0>;
166 power-domains = <&pd_lcd0>;
191 power-domains = <&pd_cam>;
202 power-domains = <&pd_cam>;
213 power-domains = <&pd_cam>;
224 power-domains = <&pd_cam>;
236 power-domains = <&pd_cam>;
251 power-domains = <&pd_cam>;
417 power-domains = <&pd_mfc>;
683 power-domains = <&pd_lcd0>;
[all …]
Dexynos5250.dtsi239 power-domains = <&pd_mfc>;
720 power-domains = <&pd_gsc>;
729 power-domains = <&pd_gsc>;
738 power-domains = <&pd_gsc>;
747 power-domains = <&pd_gsc>;
755 power-domains = <&pd_disp1>;
768 power-domains = <&pd_disp1>;
782 power-domains = <&pd_disp1>;
790 power-domains = <&pd_disp1>;
Dexynos4x12.dtsi214 power-domains = <&pd_isp>;
224 power-domains = <&pd_isp>;
234 power-domains = <&pd_isp>;
Dexynos5420.dtsi181 power-domains = <&mfc_pd>;
539 power-domains = <&disp_pd>;
564 power-domains = <&disp_pd>;
738 power-domains = <&disp_pd>;
752 power-domains = <&disp_pd>;
761 power-domains = <&gsc_pd>;
770 power-domains = <&gsc_pd>;
Dexynos3250.dtsi253 power-domains = <&pd_lcd0>;
263 power-domains = <&pd_lcd0>;
366 power-domains = <&pd_mfc>;
/linux-4.1.27/Documentation/devicetree/bindings/arm/exynos/
Dpower_domain.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.
28 - power-domains: phandle pointing to the parent power domain, for more details
31 Node of a device using power domains must have a power-domains property
/linux-4.1.27/drivers/powercap/
Dintel_rapl.c178 struct rapl_domain *domains; /* array of domains, sized at runtime */ member
281 kfree(p->domains); in rapl_cleanup_data()
333 rp->domains = NULL; in release_zone()
597 struct rapl_domain *rd = rp->domains; in rapl_init_domains()
1086 rp->domains[dmn].name); in rapl_update_domain_data()
1089 if (!rapl_read_data_raw(&rp->domains[dmn], prim, in rapl_update_domain_data()
1092 rp->domains[dmn].rdd.primitives[prim] = in rapl_update_domain_data()
1110 for (rd = rp->domains; rd < rp->domains + rp->nr_domains; in rapl_unregister_powercap()
1143 for (rd = rp->domains; rd < rp->domains + rp->nr_domains; rd++) { in rapl_package_register_powercap()
1175 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.1.27/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.1.27/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.1.27/arch/arm/mach-shmobile/
Dpm-rmobile.h41 extern void rmobile_init_domains(struct rmobile_pm_domain domains[], int num);
56 #define rmobile_init_domains(domains, num) do { } while (0) argument
Dpm-rmobile.c168 void rmobile_init_domains(struct rmobile_pm_domain domains[], int num) in rmobile_init_domains() argument
173 rmobile_init_pm_domain(&domains[j]); in rmobile_init_domains()
/linux-4.1.27/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.1.27/drivers/gpu/drm/nouveau/nvkm/engine/pm/
Dbase.c68 list_for_each_entry(dom, &ppm->domains, head) { in nvkm_perfsig_find()
129 list_for_each_entry(chk, &ppm->domains, head) { in nvkm_perfctr_query()
158 } while (&dom->head != &ppm->domains); in nvkm_perfctr_query()
182 list_for_each_entry(dom, &ppm->domains, head) { in nvkm_perfctr_sample()
411 list_add_tail(&dom->head, &ppm->domains); in nvkm_perfdom_new()
453 list_for_each_entry_safe(dom, tmp, &ppm->domains, head) { in _nvkm_pm_dtor()
474 INIT_LIST_HEAD(&ppm->domains); in nvkm_pm_create_()
/linux-4.1.27/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.1.27/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.1.27/drivers/pinctrl/samsung/
Dpinctrl-s3c64xx.c208 struct irq_domain *domains[NUM_EINT0]; member
229 struct irq_domain *domains[]; member
440 virq = irq_linear_revmap(data->domains[group], pin); in s3c64xx_eint_gpio_irq()
493 + nr_domains * sizeof(*data->domains), GFP_KERNEL); in s3c64xx_eint_gpio_init()
506 data->domains[nr_domains++] = bank->irq_domain; in s3c64xx_eint_gpio_init()
625 virq = irq_linear_revmap(data->domains[irq], data->pins[irq]); in s3c64xx_irq_demux_eint()
772 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()
556 eint_data->domains[irq] = bank->irq_domain; in s3c24xx_eint_init()
/linux-4.1.27/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.1.27/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.1.27/Documentation/devicetree/bindings/media/
Ds5p-mfc.txt31 - power-domains : power-domain property defined with a phandle
41 power-domains = <&pd_mfc>;
/linux-4.1.27/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.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/clk/
Dg84.c46 .domains = g84_domains,
Dnv50.h26 struct nvkm_domain *domains; member
Dbase.c139 struct nvkm_domain *domain = clk->domains; in nvkm_cstate_new()
249 struct nvkm_domain *clock = clk->domains - 1; in nvkm_pstate_info()
305 struct nvkm_domain *domain = clk->domains - 1; in nvkm_pstate_new()
485 struct nvkm_domain *clock = clk->domains; in _nvkm_clk_init()
549 clk->domains = clocks; in nvkm_clk_create_()
Dnv50.c511 ret = nvkm_clk_create(parent, engine, oclass, pclass->domains, in nv50_clk_ctor()
560 .domains = nv50_domains,
/linux-4.1.27/drivers/gpu/drm/nouveau/include/nvkm/engine/
Dpm.h13 struct list_head domains; member
/linux-4.1.27/kernel/irq/
DKconfig25 # and should not be used in new code. Use irq domains instead.
58 # Support for hierarchical irq domains
/linux-4.1.27/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
Dixgb.txt402 - Install the interfaces in separate broadcast domains - either in
/linux-4.1.27/Documentation/devicetree/bindings/arm/rockchip/
Dpmu.txt4 The pmu is used to turn off and on different power domains of the SoCs
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dexynos_dsim.txt24 - power-domains: a phandle to DSIM power domain node
56 power-domains = <&pd_lcd0>;
Dsamsung-fimd.txt41 - power-domains: a phandle to FIMD power domain node.
100 power-domains = <&pd_lcd0>;
/linux-4.1.27/arch/arm/mach-ux500/
Dpm_domains.c71 genpd_data->domains = ux500_pm_domains; in ux500_pm_domains_init()
/linux-4.1.27/arch/arm/mach-omap1/
Dsleep.S97 @ turn off clock domains
182 @ turn off clock domains
252 @ Turn off clock domains
/linux-4.1.27/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.1.27/net/wireless/
Ddb.txt12 # regulatory rules that cover the regulatory domains you will be using. Your
/linux-4.1.27/drivers/power/avs/
DKconfig18 Say y here to enable support io domains on Rockchip SoCs. It is
/linux-4.1.27/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.1.27/Documentation/devicetree/bindings/clock/
Dexynos4415-clock.txt10 (CMU_LEFTBUS, CMU_RIGHTBUS, CMU_TOP, CMU_CPU clock domains).
Dexynos5433-clock.txt11 domains and bus clocks.
/linux-4.1.27/drivers/gpu/drm/nouveau/
Dnouveau_gem.c292 uint32_t domains = valid_domains & nvbo->valid_domains & in nouveau_gem_set_domain() local
296 if (!domains) in nouveau_gem_set_domain()
305 if ((domains & NOUVEAU_GEM_DOMAIN_VRAM) && in nouveau_gem_set_domain()
309 else if ((domains & NOUVEAU_GEM_DOMAIN_GART) && in nouveau_gem_set_domain()
313 else if (domains & NOUVEAU_GEM_DOMAIN_VRAM) in nouveau_gem_set_domain()
/linux-4.1.27/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
605 Support for power domains is provided through the pm_domain field of struct
618 The support for device power management domains is only relevant to platforms
621 support for power domains into subsystem-level callbacks, for example by
/linux-4.1.27/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Dclk.h76 struct nvkm_domain *domains; member
/linux-4.1.27/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 …]
/linux-4.1.27/drivers/iommu/
Dintel-iommu.c1387 iommu_flush_dev_iotlb(iommu->domains[did], addr, mask); in iommu_flush_iotlb_psi()
1461 iommu->domains = kcalloc(ndomains, sizeof(struct dmar_domain *), in iommu_init_domains()
1463 if (!iommu->domains) { in iommu_init_domains()
1485 if ((iommu->domains) && (iommu->domain_ids)) { in disable_dmar_iommu()
1494 domain = iommu->domains[i]; in disable_dmar_iommu()
1508 if ((iommu->domains) && (iommu->domain_ids)) { in free_dmar_iommu()
1509 kfree(iommu->domains); in free_dmar_iommu()
1511 iommu->domains = NULL; in free_dmar_iommu()
1552 iommu->domains[num] = domain; in __iommu_attach_domain()
1583 if (iommu->domains[num] == domain) in iommu_attach_vm_domain()
[all …]
/linux-4.1.27/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.1.27/drivers/gpu/drm/nouveau/nvkm/engine/device/
Dctrl.c93 domain = clk->domains; in nvkm_control_mthd_pstate_attr()
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dmeson,pinctrl.txt9 The 2 power domains of the controller (regular and always-on) are
/linux-4.1.27/include/linux/
Dpm_domain.h259 struct generic_pm_domain **domains; member
Dintel-iommu.h340 struct dmar_domain **domains; /* ptr to domains */ member
/linux-4.1.27/Documentation/sysctl/
DREADME58 abi/ execution domains & personalities
/linux-4.1.27/Documentation/hwmon/
Dasc762160 PECI Extended configuration allows for having more than two domains per
296 1 Processor contains two domains (0,1)
/linux-4.1.27/drivers/pci/
DKconfig69 PCI devices from a PCI backend to support PCI driver domains.
/linux-4.1.27/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.txt2667 root domains (aka PCI segments, in ACPI-speak).
2834 Keep all power-domains already enabled by bootloader on,
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dcpus.txt236 the cpu-core power-domains.
239 power domains.
/linux-4.1.27/arch/arm/mach-imx/
Dgpc.c393 .domains = imx_gpc_domains,
/linux-4.1.27/Documentation/filesystems/
Ddlmfs.txt56 Once you're heartbeating, DLM lock 'domains' can be easily created /
/linux-4.1.27/Documentation/arm/
Dtcm.txt74 device state when shutting off device power domains.
/linux-4.1.27/Documentation/power/powercap/
Dpowercap.txt196 It is possible that some domains have both power ranges and energy counter ranges;
/linux-4.1.27/kernel/
Dcpuset.c617 static int generate_sched_domains(cpumask_var_t **domains, in generate_sched_domains() argument
781 *domains = doms; in generate_sched_domains()
/linux-4.1.27/Documentation/s390/
Dmonreader.txt129 data), the monitor domains contained within it and the start and end address
/linux-4.1.27/drivers/base/power/
Ddomain.c2024 if (!genpd_data->domains[idx]) in __of_genpd_xlate_onecell()
2027 return genpd_data->domains[idx]; in __of_genpd_xlate_onecell()
/linux-4.1.27/Documentation/sound/alsa/soc/
Ddapm.txt22 There are 4 power domains within DAPM
/linux-4.1.27/kernel/power/
DKconfig262 representing individual voltage domains and provides SOC
/linux-4.1.27/drivers/regulator/
DKconfig663 for different voltage domains
672 for different voltage domains
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt23 technologies are working in their own isolated domains or at best
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt131 derived from different clock domains like your main system clock (provided
/linux-4.1.27/Documentation/locking/
Dww-mutex-design.txt11 domains (for example VRAM vs system memory), and so on. And with
/linux-4.1.27/drivers/net/
DKconfig358 Xen domains. These devices can be accessed by any operating
/linux-4.1.27/Documentation/PCI/
Dpci.txt583 in the kernel as they aren't compatible with hotplug or PCI domains or
/linux-4.1.27/Documentation/security/
DSmack.txt276 This scheme organizes users, programs, and data into domains that are
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt1280 mapping documentation for a detailed description of domains.