/linux-4.4.14/drivers/media/dvb-frontends/ |
D | as102_fe.c | 134 switch (c->hierarchy) { in as102_fe_set_frontend() 136 tune_args.hierarchy = HIER_NONE; in as102_fe_set_frontend() 139 tune_args.hierarchy = HIER_ALPHA_1; in as102_fe_set_frontend() 142 tune_args.hierarchy = HIER_ALPHA_2; in as102_fe_set_frontend() 145 tune_args.hierarchy = HIER_ALPHA_4; in as102_fe_set_frontend() 148 tune_args.hierarchy = HIER_UNKNOWN; in as102_fe_set_frontend() 161 if ((tune_args.hierarchy != HIER_NONE) && in as102_fe_set_frontend() 178 tune_args.hierarchy, in as102_fe_set_frontend() 219 switch (tps.hierarchy) { in as102_fe_get_frontend() 221 c->hierarchy = HIERARCHY_NONE; in as102_fe_get_frontend() [all …]
|
D | l64781.c | 169 if (p->hierarchy != HIERARCHY_NONE && in apply_frontend_param() 187 if ((int)p->hierarchy < HIERARCHY_NONE || in apply_frontend_param() 188 p->hierarchy > HIERARCHY_4) in apply_frontend_param() 212 if (p->hierarchy != HIERARCHY_NONE) in apply_frontend_param() 215 val0x06 = (p->hierarchy << 2) | p->modulation; in apply_frontend_param() 335 p->hierarchy = HIERARCHY_NONE; in get_frontend() 338 p->hierarchy = HIERARCHY_1; in get_frontend() 341 p->hierarchy = HIERARCHY_2; in get_frontend() 344 p->hierarchy = HIERARCHY_4; in get_frontend()
|
D | mt352.c | 215 if (op->hierarchy == HIERARCHY_AUTO || in mt352_set_parameters() 216 op->hierarchy == HIERARCHY_NONE) in mt352_set_parameters() 264 switch (op->hierarchy) { in mt352_set_parameters() 386 op->hierarchy = HIERARCHY_NONE; in mt352_get_parameters() 389 op->hierarchy = HIERARCHY_1; in mt352_get_parameters() 392 op->hierarchy = HIERARCHY_2; in mt352_get_parameters() 395 op->hierarchy = HIERARCHY_4; in mt352_get_parameters() 398 op->hierarchy = HIERARCHY_AUTO; in mt352_get_parameters()
|
D | dib3000mb.c | 233 switch (c->hierarchy) { in dib3000mb_set_frontend() 257 if (c->hierarchy == HIERARCHY_NONE) { in dib3000mb_set_frontend() 262 } else if (c->hierarchy != HIERARCHY_AUTO) { in dib3000mb_set_frontend() 341 c->hierarchy == HIERARCHY_AUTO || in dib3000mb_set_frontend() 516 c->hierarchy = HIERARCHY_NONE; in dib3000mb_get_frontend() 520 c->hierarchy = HIERARCHY_1; in dib3000mb_get_frontend() 524 c->hierarchy = HIERARCHY_2; in dib3000mb_get_frontend() 528 c->hierarchy = HIERARCHY_4; in dib3000mb_get_frontend() 541 c->hierarchy = HIERARCHY_NONE; in dib3000mb_get_frontend()
|
D | zl10353.c | 274 if (c->hierarchy == HIERARCHY_AUTO || in zl10353_set_parameters() 275 c->hierarchy == HIERARCHY_NONE) in zl10353_set_parameters() 323 switch (c->hierarchy) { in zl10353_set_parameters() 442 c->hierarchy = HIERARCHY_NONE; in zl10353_get_parameters() 445 c->hierarchy = HIERARCHY_1; in zl10353_get_parameters() 448 c->hierarchy = HIERARCHY_2; in zl10353_get_parameters() 451 c->hierarchy = HIERARCHY_4; in zl10353_get_parameters() 454 c->hierarchy = HIERARCHY_AUTO; in zl10353_get_parameters()
|
D | cx22702.c | 171 p->hierarchy = HIERARCHY_NONE; in cx22702_get_tps() 174 p->hierarchy = HIERARCHY_1; in cx22702_get_tps() 177 p->hierarchy = HIERARCHY_2; in cx22702_get_tps() 180 p->hierarchy = HIERARCHY_4; in cx22702_get_tps() 298 if ((p->hierarchy == HIERARCHY_AUTO) || in cx22702_set_tps() 333 switch (p->hierarchy) { /* mask 0x07 */ in cx22702_set_tps()
|
D | cx22700.c | 155 if ((int)p->hierarchy < HIERARCHY_NONE || in cx22700_set_tps() 156 p->hierarchy > HIERARCHY_4) in cx22700_set_tps() 168 val |= p->hierarchy - HIERARCHY_NONE; in cx22700_set_tps() 208 p->hierarchy = HIERARCHY_AUTO; in cx22700_get_tps() 210 p->hierarchy = HIERARCHY_NONE + (val & 0x7); in cx22700_get_tps()
|
D | as102_fe_types.h | 110 uint8_t hierarchy; member 131 uint8_t hierarchy; member
|
D | cxd2820r_t.c | 190 c->hierarchy = HIERARCHY_NONE; in cxd2820r_get_frontend_t() 193 c->hierarchy = HIERARCHY_1; in cxd2820r_get_frontend_t() 196 c->hierarchy = HIERARCHY_2; in cxd2820r_get_frontend_t() 199 c->hierarchy = HIERARCHY_4; in cxd2820r_get_frontend_t()
|
D | rtl2830.c | 340 c->hierarchy = HIERARCHY_NONE; in rtl2830_get_frontend() 343 c->hierarchy = HIERARCHY_1; in rtl2830_get_frontend() 346 c->hierarchy = HIERARCHY_2; in rtl2830_get_frontend() 349 c->hierarchy = HIERARCHY_4; in rtl2830_get_frontend() 541 unsigned hierarchy, constellation; in rtl2830_stat_work() local 558 hierarchy = (u8tmp >> 4) & 0x07; /* [6:4] */ in rtl2830_stat_work() 559 if (hierarchy > HIERARCHY_NUM - 1) in rtl2830_stat_work() 568 tmp = (constant[constellation][hierarchy] - in rtl2830_stat_work()
|
D | rtl2832.c | 636 c->hierarchy = HIERARCHY_NONE; in rtl2832_get_frontend() 639 c->hierarchy = HIERARCHY_1; in rtl2832_get_frontend() 642 c->hierarchy = HIERARCHY_2; in rtl2832_get_frontend() 645 c->hierarchy = HIERARCHY_4; in rtl2832_get_frontend() 777 unsigned hierarchy, constellation; in rtl2832_stat_work() local 794 hierarchy = (u8tmp >> 4) & 0x07; /* [6:4] */ in rtl2832_stat_work() 795 if (hierarchy > HIERARCHY_NUM - 1) in rtl2832_stat_work() 804 tmp = (constant[constellation][hierarchy] - in rtl2832_stat_work()
|
D | tda1004x.c | 742 (fe_params->hierarchy == HIERARCHY_AUTO)) { in tda1004x_set_fe() 781 switch (fe_params->hierarchy) { in tda1004x_set_fe() 1001 fe_params->hierarchy = HIERARCHY_NONE; in tda1004x_get_fe() 1004 fe_params->hierarchy = HIERARCHY_1; in tda1004x_get_fe() 1007 fe_params->hierarchy = HIERARCHY_2; in tda1004x_get_fe() 1010 fe_params->hierarchy = HIERARCHY_4; in tda1004x_get_fe()
|
D | dib3000mc.c | 512 if (ch->hierarchy == 1) in dib3000mc_set_channel_cfg() 516 switch ((ch->hierarchy == 0 || 1 == 1) ? ch->code_rate_HP : ch->code_rate_LP) { in dib3000mc_set_channel_cfg() 571 schan.hierarchy = 0; in dib3000mc_autosearch_start() 671 fep->hierarchy = HIERARCHY_NONE; in dib3000mc_get_frontend()
|
D | tda10048.c | 612 p->hierarchy = HIERARCHY_NONE; in tda10048_get_tps() 615 p->hierarchy = HIERARCHY_1; in tda10048_get_tps() 618 p->hierarchy = HIERARCHY_2; in tda10048_get_tps() 621 p->hierarchy = HIERARCHY_4; in tda10048_get_tps()
|
D | af9013.c | 724 switch (c->hierarchy) { in af9013_set_frontend() 919 c->hierarchy = HIERARCHY_NONE; in af9013_get_frontend() 922 c->hierarchy = HIERARCHY_1; in af9013_get_frontend() 925 c->hierarchy = HIERARCHY_2; in af9013_get_frontend() 928 c->hierarchy = HIERARCHY_4; in af9013_get_frontend()
|
D | stv0367.c | 71 enum stv0367_ter_hierarchy hierarchy; member 1686 if (ter_state->hierarchy == FE_TER_HIER_LOW_PRIO) in stv0367ter_algo() 1880 ter_state->hierarchy = FE_TER_HIER_NONE; in stv0367ter_set_frontend() 1968 p->hierarchy = HIERARCHY_NONE; in stv0367ter_get_frontend() 1971 p->hierarchy = HIERARCHY_1; in stv0367ter_get_frontend() 1974 p->hierarchy = HIERARCHY_2; in stv0367ter_get_frontend() 1977 p->hierarchy = HIERARCHY_4; in stv0367ter_get_frontend() 1980 p->hierarchy = HIERARCHY_AUTO; in stv0367ter_get_frontend() 1985 if (ter_state->hierarchy == FE_TER_HIER_LOW_PRIO) in stv0367ter_get_frontend()
|
D | af9033.c | 734 c->hierarchy = HIERARCHY_NONE; in af9033_get_frontend() 737 c->hierarchy = HIERARCHY_1; in af9033_get_frontend() 740 c->hierarchy = HIERARCHY_2; in af9033_get_frontend() 743 c->hierarchy = HIERARCHY_4; in af9033_get_frontend()
|
D | dib9000.c | 1269 state->fe[0]->dtv_property_cache.hierarchy = HIERARCHY_NONE; in dib9000_fw_get_channel() 1272 state->fe[0]->dtv_property_cache.hierarchy = HIERARCHY_1; in dib9000_fw_get_channel() 1276 state->fe[0]->dtv_property_cache.hierarchy = HIERARCHY_AUTO; in dib9000_fw_get_channel() 1407 switch (state->fe[0]->dtv_property_cache.hierarchy) { in dib9000_fw_set_channel_union() 1924 state->fe[sub_index_frontend]->dtv_property_cache.hierarchy = in dib9000_get_frontend() 1925 state->fe[index_frontend]->dtv_property_cache.hierarchy; in dib9000_get_frontend() 1950 state->fe[index_frontend]->dtv_property_cache.hierarchy = fe->dtv_property_cache.hierarchy; in dib9000_get_frontend()
|
D | dib7000m.c | 880 if (ch->hierarchy == 1) in dib7000m_set_channel() 884 switch ((ch->hierarchy == 0 || 1 == 1) ? ch->code_rate_HP : ch->code_rate_LP) { in dib7000m_set_channel() 975 schan.hierarchy = 0; in dib7000m_autosearch_start() 1187 fep->hierarchy = HIERARCHY_NONE; in dib7000m_get_frontend()
|
D | lgs8gl5.c | 352 p->hierarchy = HIERARCHY_NONE; in lgs8gl5_get_frontend()
|
D | sp8870.c | 193 switch (p->hierarchy) { in configure_reg0xc05()
|
D | dib7000p.c | 1025 if (ch->hierarchy == 1) in dib7000p_set_channel() 1029 switch ((ch->hierarchy == 0 || 1 == 1) ? ch->code_rate_HP : ch->code_rate_LP) { in dib7000p_set_channel() 1131 schan.hierarchy = 0; in dib7000p_autosearch_start() 1459 fep->hierarchy = HIERARCHY_NONE; in dib7000p_get_frontend() 1834 switch ((c->hierarchy == 0 || 1 == 1) ? c->code_rate_HP : c->code_rate_LP) { in dib7000p_get_time_us()
|
D | atbm8830.c | 324 c->hierarchy = HIERARCHY_NONE; in atbm8830_get_fe()
|
D | sp887x.c | 234 switch (p->hierarchy) { in configure_reg0xc05()
|
D | lgs8gxx.c | 719 fe_params->hierarchy = HIERARCHY_NONE; in lgs8gxx_get_fe()
|
D | drxd_hard.c | 2021 switch (p->hierarchy) { in DRX_Start()
|
D | drxk_hard.c | 3817 switch (state->props.hierarchy) { in set_dvbt()
|
/linux-4.4.14/Documentation/cgroups/ |
D | cgroups.txt | 56 A *hierarchy* is a set of cgroups arranged in a tree, such that 58 hierarchy, and a set of subsystems; each subsystem has system-specific 59 state attached to each cgroup in the hierarchy. Each hierarchy has 63 cgroups. Each hierarchy is a partition of all tasks in the system. 68 a cgroup. Those creations and assignments only affect the hierarchy 95 Multiple hierarchy support is provided to allow for situations where 98 hierarchy to be a natural division of tasks, without having to handle 104 separate hierarchy; at the other extreme, all subsystems 105 would be attached to the same hierarchy. 143 With only a single hierarchy, he now would potentially have to create [all …]
|
D | unified-hierarchy.txt | 2 Cgroup unified hierarchy 6 This document describes the changes made by unified hierarchy and 39 cgroup allows an arbitrary number of hierarchies and each hierarchy 47 populated. Another issue is that all controllers bound to a hierarchy 48 are forced to have exactly the same view of the hierarchy. It isn't 52 on the same hierarchy and most configurations resort to putting each 53 controller on its own hierarchy. Only closely related ones, such as 55 hierarchy. This often means that userland ends up managing multiple 56 similar hierarchies repeating the same steps on each hierarchy 57 whenever a hierarchy management operation is necessary. [all …]
|
D | pids.txt | 7 The process number controller is used to allow a cgroup hierarchy to stop any 12 preventable in the scope of a cgroup hierarchy by allowing resource limiting of 31 limit in the hierarchy is followed). 43 Then we create a hierarchy, set limits and attach processes to it: 61 not be able to overcome the most stringent limit in the hierarchy (in this case,
|
D | 00-INDEX | 29 unified-hierarchy.txt
|
D | devices.txt | 54 device cgroups maintain hierarchy by making sure a cgroup never has more 114 to devices will be propagated down the hierarchy.
|
D | blkio-controller.txt | 7 both at leaf nodes as well as at intermediate nodes in a storage hierarchy. 98 Both CFQ and throttling implement hierarchy support; however, 99 throttling's hierarchy support is enabled iff "sane_behavior" is 103 If somebody created a hierarchy like as follows. 112 hierarchy correctly. For details on CFQ hierarchy support, refer to 392 If both the blkio and memory controllers are used on the v2 hierarchy
|
D | memcg_test.txt | 179 When using hierarchy, mkdir/rmdir test should be done. 228 the memcg. When hierarchy is used, a task under hierarchy
|
D | cpuacct.txt | 7 The CPU accounting controller supports multi-hierarchy groups. An accounting
|
D | memory.txt | 507 # status considering hierarchy (see memory.use_hierarchy settings) 509 hierarchical_memory_limit - # of bytes of memory limit with regard to hierarchy 512 hierarchy under which memory cgroup is. 593 The memory controller supports a deep hierarchy and hierarchical accounting. 594 The hierarchy is created by creating the appropriate cgroups in the 596 hierarchy 614 A memory cgroup by default disables the hierarchy feature. Support
|
D | cpusets.txt | 46 hierarchy visible in a virtual file system. These are the essential 131 - The hierarchy of cpusets can be mounted at /dev/cpuset, for 211 These rules, and the natural hierarchy of cpusets, enable efficient 215 to represent the cpuset hierarchy provides for a familiar permission
|
/linux-4.4.14/Documentation/ |
D | IRQ-domain.txt | 168 interrupt controller and those irq_domains are organized into hierarchy. 169 When building irq_domain hierarchy, the irq_domain near to the device is 170 child and the irq_domain near to CPU is parent. So a hierarchy structure 180 There are four major interfaces to use hierarchy irq_domain: 190 Following changes are needed to support hierarchy irq_domain. 192 maintain irq_domain hierarchy information. 194 build hierarchy irq_data to match hierarchy irq_domains. The irq_data 196 3) new callbacks are added to struct irq_domain_ops to support hierarchy 199 With support of hierarchy irq_domain and hierarchy irq_data ready, an 202 IRQ. Now we could go one step further to support stacked(hierarchy) [all …]
|
D | sysfs-rules.txt | 96 There is only one valid place in sysfs where hierarchy can be examined 128 at the same level, never in a hierarchy. Assuming the block subsystem to
|
D | kobject.txt | 214 in the sysfs hierarchy, and not have to mess with the whole complication of 322 the sysfs hierarchy are constructed in this way.
|
D | kernel-parameters.txt | 595 a single hierarchy
|
/linux-4.4.14/drivers/media/usb/dvb-usb-v2/ |
D | mxl111sf-demod.c | 184 enum fe_hierarchy *hierarchy) in mxl1x1sf_demod_get_tps_hierarchy() argument 194 *hierarchy = HIERARCHY_NONE; in mxl1x1sf_demod_get_tps_hierarchy() 197 *hierarchy = HIERARCHY_1; in mxl1x1sf_demod_get_tps_hierarchy() 200 *hierarchy = HIERARCHY_2; in mxl1x1sf_demod_get_tps_hierarchy() 203 *hierarchy = HIERARCHY_4; in mxl1x1sf_demod_get_tps_hierarchy() 531 &p->hierarchy); in mxl111sf_demod_get_frontend()
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
D | prcm.txt | 4 a DT hierarchy. Each TI SoC can have multiple PRCM entities listed for it, 5 each describing one module and the clock hierarchy under it. see [1] for
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | topology.txt | 9 In an ARM system, the hierarchy of CPUs is defined through three entities that 17 correspond to physical CPUs and are to be mapped to the hierarchy levels. 19 The bottom hierarchy level sits at core or thread level depending on whether 23 threads existing in the system and map to the hierarchy level "thread" above. 25 in the system and map to the hierarchy level "core" above. 28 corresponding to the system hierarchy; syntactically they are defined as device 94 levels) since name uniqueness will be guaranteed by the device tree hierarchy.
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/uniphier/ |
D | cache-uniphier.txt | 16 - cache-level: specifies the level in the cache hierarchy. The value should 23 The L2 cache must exist to use the L3 cache; the cache hierarchy must be
|
/linux-4.4.14/drivers/media/usb/as102/ |
D | as10x_cmd.c | 128 preq->body.set_tune.req.args.hierarchy = ptune->hierarchy; in as10x_cmd_set_tune() 254 ptps->hierarchy = prsp->body.get_tps.rsp.tps.hierarchy; in as10x_cmd_get_tps()
|
/linux-4.4.14/Documentation/devicetree/bindings/power/ |
D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should 52 This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-bwc.txt | 8 specification of the maximum CPU bandwidth available to a group or hierarchy. 14 hierarchy will be throttled and are not allowed to run again until the next 81 within a hierarchy.
|
D | sched-domains.txt | 2 hierarchy is built from these base domains via the ->parent pointer. ->parent 50 The "base" domain will "span" the first level of the hierarchy. In the case
|
D | sched-design-CFS.txt | 142 Classes," an extensible hierarchy of scheduler modules. These modules
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | spear1310-evb.dts | 361 pl022,hierarchy = <0>; 394 pl022,hierarchy = <0>; 410 pl022,hierarchy = <0>;
|
D | spear1340-evb.dts | 454 pl022,hierarchy = <0>; 470 pl022,hierarchy = <0>; 504 pl022,hierarchy = <0>;
|
D | dm816x.dtsi | 58 * the whole bus hierarchy.
|
D | omap3.dtsi | 79 * hierarchy.
|
D | am33xx.dtsi | 91 * the whole bus hierarchy.
|
D | omap4.dtsi | 113 * hierarchy.
|
D | omap5.dtsi | 128 * hierarchy.
|
D | dra7.dtsi | 92 * hierarchy.
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
D | qcom,idle-state.txt | 18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings 20 cache hierarchy is also out of standby, and then the cpu is allowed to resume 39 system state including cache hierarchy is ready before allowing core to
|
/linux-4.4.14/arch/arm64/boot/dts/amd/ |
D | amd-overdrive.dts | 54 pl022,hierarchy = <0>;
|
/linux-4.4.14/Documentation/acpi/ |
D | i2c-muxes.txt | 4 Describing an I2C device hierarchy that includes I2C muxes requires an ACPI
|
D | namespace.txt | 12 hierarchy there is a corresponding symbolic link in the 80 is a hierarchy of objects identified by names and paths. 281 objects in the Linux' device hierarchy that represent "physical" devices 314 The sysfs hierarchy of struct acpi_device objects corresponding to the
|
D | scan_handlers.txt | 10 and the hierarchy of those struct acpi_device objects reflects the namespace
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
D | clockdomain.txt | 11 hardware hierarchy.
|
/linux-4.4.14/include/linux/amba/ |
D | pl022.h | 282 enum ssp_hierarchy hierarchy; member
|
/linux-4.4.14/Documentation/PCI/ |
D | pcieaer-howto.txt | 122 hierarchy and links. These errors do not include any device specific 155 with downstream device drivers associated with a hierarchy in question 179 pci_channel_io_normal) to all drivers associated within a hierarchy in 182 If Upstream port A captures an AER error, the hierarchy consists of 191 a hierarchy in question. Then, performing link reset at upstream is
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-firmware-ofw | 24 hierarchy of directories, one per device tree node. The
|
D | sysfs-class-powercap | 42 Power zones may be organized in a hierarchy in which child
|
D | sysfs-devices-system-cpu | 246 level: the cache hierarchy in the multi-level cache configuration
|
/linux-4.4.14/Documentation/driver-model/ |
D | binding.txt | 63 the device's directory in the physical hierarchy. 66 to the device's directory in the physical hierarchy.
|
D | porting.txt | 144 the device hierarchy. Accurately setting the parent guarantees that 145 sysfs will accurately represent the hierarchy. 207 that point to the device's directory in the physical hierarchy.
|
D | bus.txt | 109 hierarchy:
|
D | class.txt | 103 device's directory in the physical hierarchy:
|
/linux-4.4.14/Documentation/filesystems/configfs/ |
D | configfs.txt | 269 the item hierarchy. If a client needs to do some cleanup before this 316 config_items are arranged in a hierarchy due to the fact that they 318 parts, but the subsystem might be interested in this hierarchy. For 319 this reason, the hierarchy is mirrored via the config_group->cg_children 324 management of the hierarchy, so configfs uses the subsystem mutex to 326 hierarchy, it must do so under the protection of the subsystem 330 allocated item has not been linked into this hierarchy. Similarly, it
|
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/ |
D | TREE_RCU-kconfig.txt | 19 CONFIG_RCU_FANOUT -- Cover hierarchy, but overlap with others.
|
D | initrd.txt | 1 This document describes one way to create the initrd directory hierarchy
|
/linux-4.4.14/Documentation/devicetree/bindings/spi/ |
D | spi_pl022.txt | 59 pl022,hierarchy = <0>;
|
/linux-4.4.14/Documentation/locking/ |
D | lockdep-design.txt | 135 is some sort of hierarchy within objects of the same type. In these 137 (defined by the properties of the hierarchy), and the kernel grabs the 140 An example of such an object hierarchy that results in "nested locking" 169 check really thoroughly that the hierarchy is correctly mapped; otherwise
|
/linux-4.4.14/Documentation/DocBook/ |
D | genericirq.xml.db | 69 API-irq-chip-retrigger-hierarchy
|
/linux-4.4.14/drivers/media/usb/dvb-usb/ |
D | af9005-fe.c | 1271 fep->hierarchy = HIERARCHY_NONE; in af9005_fe_get_frontend() 1275 fep->hierarchy = HIERARCHY_1; in af9005_fe_get_frontend() 1279 fep->hierarchy = HIERARCHY_2; in af9005_fe_get_frontend() 1283 fep->hierarchy = HIERARCHY_4; in af9005_fe_get_frontend()
|
D | cinergyT2-fe.c | 121 switch (op->hierarchy) { in compute_tps()
|
D | friio-fe.c | 296 p->hierarchy = HIERARCHY_AUTO; in jdvbt90502_get_frontend()
|
/linux-4.4.14/drivers/media/common/siano/ |
D | smsdvb-main.c | 236 c->hierarchy = sms_to_hierarchy(p->hierarchy); in smsdvb_update_tx_params() 299 c->hierarchy = sms_to_hierarchy(p->hierarchy); in smsdvb_update_dvb_stats()
|
D | smscoreapi.h | 719 u32 hierarchy; /* hierarchy from SMSHOSTLIB_HIERARCHY_ET, member 944 u32 hierarchy; /* hierarchy from SMSHOSTLIB_HIERARCHY_ET */ member
|
D | smsdvb-debugfs.c | 102 "hierarchy = %d\n", p->hierarchy); in smsdvb_print_dvb_stats()
|
/linux-4.4.14/net/bluetooth/ |
D | Kconfig | 83 are run late in the initcall hierarchy.
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | fake-numa-for-cpusets | 65 cpusets. Since cpusets can form a hierarchy, you can create some pretty
|
/linux-4.4.14/drivers/media/dvb-core/ |
D | dvb_frontend.h | 580 enum fe_hierarchy hierarchy; member
|
D | dvb_frontend.c | 1029 c->hierarchy = HIERARCHY_AUTO; in dvb_frontend_clear_cache() 1249 c->hierarchy = p->u.ofdm.hierarchy_information; in dtv_property_cache_sync() 1329 p->u.ofdm.hierarchy_information = c->hierarchy; in dtv_property_legacy_params_sync() 1437 tvp->u.data = c->hierarchy; in dtv_property_process_get() 1905 c->hierarchy = tvp->u.data; in dtv_property_process_set() 2209 if (c->hierarchy == HIERARCHY_NONE && c->code_rate_LP == FEC_NONE) in dtv_set_frontend()
|
/linux-4.4.14/fs/reiserfs/ |
D | Kconfig | 48 Create under /proc/fs/reiserfs a hierarchy of files, displaying
|
/linux-4.4.14/drivers/spi/ |
D | spi-pl022.c | 1626 if ((chip_info->hierarchy != SSP_MASTER) in verify_controller_parameters() 1627 && (chip_info->hierarchy != SSP_SLAVE)) { in verify_controller_parameters() 1812 .hierarchy = SSP_SLAVE, 1867 chip_info_dt.hierarchy = SSP_MASTER; in pl022_setup() 2051 SSP_WRITE_BITS(chip->cr1, chip_info->hierarchy, SSP_CR1_MASK_MS, 2); in pl022_setup()
|
/linux-4.4.14/Documentation/block/ |
D | cfq-iosched.txt | 160 configured by leaf_weight[_device]. Let's assume a blkio hierarchy 162 weights where the names represent the hierarchy. 175 parent level. Considering only the weights which matter, the hierarchy
|
D | biodoc.txt | 622 or hierarchy of allocation needs to be consistent, just the way one deals
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | fsl,imx-pinctrl.txt | 53 name describe the pin function and group hierarchy.
|
D | atmel,at91-pinctrl.txt | 109 name describe the pin function and group hierarchy.
|
/linux-4.4.14/fs/proc/ |
D | Kconfig | 20 meaning it has to be given a location in the directory hierarchy.
|
/linux-4.4.14/Documentation/hid/ |
D | hiddev.txt | 112 also returns the level the collection lives in the hierarchy. 186 indicates where in the collection hierarchy this usage sits.
|
/linux-4.4.14/Documentation/filesystems/ |
D | sysfs.txt | 274 directly to the internal kernel device tree, which is a hierarchy of 291 filesystem wanting to export attributes must create its own hierarchy
|
D | sysfs-pci.txt | 93 underlying platform supports them. They're located in the PCI class hierarchy,
|
D | nilfs2.txt | 252 corresponding checkpoint entry in the cpfile. Thus, the hierarchy
|
D | debugfs.txt | 227 top-level directory, the entire hierarchy below that directory will be
|
D | proc.txt | 226 NStgid descendant namespace thread group ID hierarchy 227 NSpid descendant namespace process ID hierarchy 228 NSpgid descendant namespace process group ID hierarchy 229 NSsid descendant namespace session ID hierarchy 1378 by reading files in the hierarchy.
|
/linux-4.4.14/Documentation/sh/ |
D | new-machine.txt | 20 hierarchy looks like the following: 109 arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
|
/linux-4.4.14/Documentation/filesystems/caching/ |
D | netfs-api.txt | 18 hierarchy for each netfs is structured according the whim of the netfs. 67 entire in-cache hierarchy for this netfs will be scrapped and begun 184 in the hierarchy may be stored in multiple caches. This function does not 331 The third step is to inform FS-Cache about part of an index hierarchy that can 351 object needs to be created somewhere down the hierarchy. Furthermore, an index
|
D | fscache.txt | 107 (6) The netfs is allowed to propose - dynamically - any index hierarchy it 120 them as obsolete and the index hierarchy rooted at that point will get
|
/linux-4.4.14/Documentation/device-mapper/ |
D | switch.txt | 48 device hierarchy:
|
/linux-4.4.14/drivers/media/dvb-frontends/drx39xyj/ |
D | drx_driver.h | 1015 enum drx_hierarchy hierarchy; member 1132 enum drx_hierarchy hierarchy; member
|
/linux-4.4.14/Documentation/power/powercap/ |
D | powercap.txt | 23 controls), those power zones may also be organized in a hierarchy with one
|
/linux-4.4.14/scripts/ |
D | spelling.txt | 478 hierachy||hierarchy 479 hierarchie||hierarchy
|
/linux-4.4.14/Documentation/arm/ |
D | vlocks.txt | 95 vlocks can be cascaded in a voting hierarchy to permit better scaling
|
/linux-4.4.14/drivers/media/firewire/ |
D | firedtv-avc.c | 505 | (p->hierarchy != HIERARCHY_AUTO ? 1 << 3 : 0) in avc_tuner_dsd_dvb_t() 538 switch (p->hierarchy) { in avc_tuner_dsd_dvb_t()
|
/linux-4.4.14/Documentation/vm/ |
D | frontswap.txt | 196 swap hierarchy. Perhaps it could be rewritten to accommodate a hierarchy,
|
/linux-4.4.14/Documentation/RCU/ |
D | trace.txt | 49 Displays the struct rcu_node hierarchy. 329 structure. Each line represents one level of the hierarchy, 368 in working out how the hierarchy is wired together.
|
/linux-4.4.14/Documentation/nvdimm/ |
D | nvdimm.txt | 260 corresponding object hierarchy diagram as viewed through the LIBNDCTL 537 for the REGION level of the device-hierarchy old userspace 541 named "namespace". This generic format of the device-model hierarchy
|
/linux-4.4.14/Documentation/usb/ |
D | mass-storage.txt | 152 hierarchy. Inside of it the following three files are created:
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | mmu.txt | 133 The level in the shadow paging hierarchy that this shadow page belongs to. 317 - walk the shadow page hierarchy and drop affected translations
|
/linux-4.4.14/tools/perf/ |
D | design.txt | 114 cache references and misses at different levels of the cache hierarchy).
|
/linux-4.4.14/drivers/staging/unisys/Documentation/ |
D | overview.txt | 150 Documentation/driver-model/, the hierarchy of s-Par virtual devices is
|
/linux-4.4.14/arch/m68k/ifpsp060/src/ |
D | isp.S | 38 # extra layer of hierarchy adds a slight performance penalty but
|
D | pfpsp.S | 38 # extra layer of hierarchy adds a slight performance penalty but
|
D | fpsp.S | 39 # extra layer of hierarchy adds a slight performance penalty but
|
/linux-4.4.14/Documentation/trace/ |
D | events.txt | 60 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
|
/linux-4.4.14/Documentation/devicetree/ |
D | usage-model.txt | 345 same hierarchy is also found in the DT, where I2C device nodes only
|
D | booting-without-of.txt | 1260 hierarchy and routing of interrupts in the hardware. 1305 _device tree_ hierarchy.
|
/linux-4.4.14/Documentation/power/ |
D | runtime_pm.txt | 308 removing the device from device hierarchy 659 different levels of device hierarchy. Namely, if a system suspend .prepare()
|
D | pci.txt | 244 they are in-band messages that have to pass through the PCI Express hierarchy,
|
/linux-4.4.14/net/sched/ |
D | Kconfig | 52 into a tree-like hierarchy of classes; the leaves of this tree are
|
/linux-4.4.14/tools/power/cpupower/po/ |
D | de.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | it.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | cs.po | 106 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | fr.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | pt.po | 101 msgid "\t -t: show CPU topology/hierarchy\n"
|
/linux-4.4.14/Documentation/networking/ |
D | scaling.txt | 333 which is local to the application thread’s CPU in the cache hierarchy.
|
/linux-4.4.14/Documentation/blockdev/ |
D | README.DAC960 | 285 special files created in the /proc/rd/... hierarchy along with the normal
|
/linux-4.4.14/Documentation/kbuild/ |
D | makefiles.txt | 762 To delete a directory hierarchy use:
|
/linux-4.4.14/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 2156 It's possible to boot from a directory hierarchy on the host using 2159 To start, you need that hierarchy. The easiest way is to loop mount
|
/linux-4.4.14/init/ |
D | Kconfig | 971 to a cgroup hierarchy will *not* be blocked by the PIDs subsystem),
|
/linux-4.4.14/ |
D | CREDITS | 120 D: hierarchy and the Linux Device List; various kernel hacks
|