Home
last modified time | relevance | path

Searched refs:each (Results 1 – 200 of 1231) sorted by relevance

1234567

/linux-4.1.27/drivers/net/ethernet/qlogic/qlcnic/
Dqlcnic_dcb.c571 struct qlcnic_dcb_param *each; in qlcnic_83xx_dcb_query_cee_param() local
598 each = &mbx_out.type[j]; in qlcnic_83xx_dcb_query_cee_param()
600 each->hdr_prio_pfc_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
601 each->hdr_prio_pfc_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
602 each->prio_pg_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
603 each->prio_pg_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
604 each->pg_bw_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
605 each->pg_bw_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
606 each->pg_tsa_map[0] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
607 each->pg_tsa_map[1] = cmd.rsp.arg[k++]; in qlcnic_83xx_dcb_query_cee_param()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/video/
Drenesas,du.txt10 - reg: A list of base address and length of each memory resource, one for
11 each entry in the reg-names property.
13 resource for the DU core (named "du") and one memory resource for each
20 - clocks: A list of phandles + clock-specifier pairs, one for each entry in
39 The following table lists for each supported model the port number
40 corresponding to each DU output.
Dti,omap-dss.txt8 Binding details for each OMAP SoC version are described in respective binding
29 and the properties for the ports and endpoints for each encoder are
39 name for each display. If no aliases are defined, a semi-random number is used
Dexynos_dsim.txt11 - clocks: list of clock specifiers, must contain an entry for each required
14 - phys: list of phy specifiers, must contain an entry for each required
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dapm-xgene-phy.txt19 Two set of 3-tuple setting for each (up to 3)
25 Two set of 3-tuple setting for each (up to 3)
28 gain control. Two set of 3-tuple setting for each
32 each (up to 3) supported link speed on the host.
36 3-tuple setting for each (up to 3) supported link
40 3-tuple setting for each (up to 3) supported link
46 - apm,tx-speed : Tx operating speed. One set of 3-tuple for each
Dphy-miphy365x.txt11 an entry for each port sub-node, specifying the control
14 Required nodes : A sub-node is required for each channel the controller
25 - reg : Address and length of register sets for each device in
Dti-phy.txt37 - clocks: a list of phandles and clock-specifier pairs, one for each entry in
68 - clocks: a list of phandles and clock-specifier pairs, one for each entry in
83 differentiate between each instance "id" can be used (e.g., multi-lane PCIe
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dqcom,lpass-cpu.txt8 - clocks : Must contain an entry for each entry in clock-names.
13 - interrupts : Must contain an entry for each entry in
17 - pinctrl-N : One property must exist for each entry in
21 - reg : Must contain an address for each entry in reg-names.
Dnvidia,tegra30-ahub.txt8 - reg : Should contain the register physical address and length for each of
13 - clocks : Must contain an entry for each entry in clock-names.
18 - resets : Must contain an entry for each entry in reset-names.
47 - dmas : Must contain an entry for each entry in clock-names.
Dtdm-slot.txt7 dai-tdm-slot-width : Width in bits for each slot.
13 And for each spcified driver, there could be one .of_xlate_tdm_slot_mask()
Dnvidia,tegra20-i2s.txt7 - resets : Must contain an entry for each entry in reset-names.
11 - dmas : Must contain an entry for each entry in clock-names.
Dsirf-usp.txt7 - dma-names: Identifier string for each DMA request line in the dmas property.
15 - pinctrl-NNN: One property must exist for each entry in pinctrl-names.
Dnvidia,tegra30-hda.txt9 - clocks : Must contain an entry for each required entry in clock-names.
12 - resets : Must contain an entry for each entry in reset-names.
Dnvidia,tegra20-ac97.txt7 - resets : Must contain an entry for each entry in reset-names.
11 - dmas : Must contain an entry for each entry in clock-names.
Dsirf-audio-port.txt7 - dma-names: Identifier string for each DMA request line in the dmas property.
/linux-4.1.27/Documentation/devicetree/bindings/gpu/
Dnvidia,tegra20-host1x.txt14 - resets: Must contain an entry for each entry in reset-names.
19 The host1x top-level node defines a number of children, each representing one
30 - resets: Must contain an entry for each entry in reset-names.
43 - resets: Must contain an entry for each entry in reset-names.
56 - resets: Must contain an entry for each entry in reset-names.
69 - resets: Must contain an entry for each entry in reset-names.
82 - resets: Must contain an entry for each entry in reset-names.
92 - clocks: Must contain an entry for each entry in clock-names.
99 - resets: Must contain an entry for each entry in reset-names.
111 - clocks: Must contain an entry for each entry in clock-names.
[all …]
Dnvidia,gk20a.txt11 - interrupts: Must contain an entry for each entry in interrupt-names.
17 - clocks: Must contain an entry for each entry in clock-names.
22 - resets: Must contain an entry for each entry in reset-names.
/linux-4.1.27/Documentation/devicetree/bindings/devfreq/event/
Dexynos-ppmu.txt5 each IP. PPMU provides the primitive values to get performance data. These
8 usages of each IP (DMC, CPU, RIGHTBUS, LEFTBUS, CAM interface, LCD, G3D, MFC).
11 derterming the current state of each IP.
15 - reg: physical base address of each PPMU and length of memory mapped region.
58 Example2 : Events of each PPMU node in exynos3250-rinato.dts are listed below.
/linux-4.1.27/Documentation/infiniband/
Dsysfs.txt3 For each InfiniBand device, the InfiniBand drivers create the
11 for each port. For example, if mthca0 is a 2-port HCA, there will
20 In each port subdirectory, the following files are created:
54 The "pkeys" and "gids" subdirectories contain one file for each
/linux-4.1.27/drivers/leds/
Dleds-lp55xx-common.c462 struct lp55xx_led *each; in lp55xx_register_leds() local
479 each = led + i; in lp55xx_register_leds()
480 ret = lp55xx_init_led(each, chip, i); in lp55xx_register_leds()
484 INIT_WORK(&each->brightness_work, cfg->brightness_work_fn); in lp55xx_register_leds()
487 each->chip = chip; in lp55xx_register_leds()
491 cfg->set_led_current(each, led_current); in lp55xx_register_leds()
505 struct lp55xx_led *each; in lp55xx_unregister_leds() local
508 each = led + i; in lp55xx_unregister_leds()
509 led_classdev_unregister(&each->cdev); in lp55xx_unregister_leds()
510 flush_work(&each->brightness_work); in lp55xx_unregister_leds()
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/
Dcpm.txt16 - unused-units : specifier consist of one cell. For each
20 - idle-doze : specifier consist of one cell. For each
24 - standby : specifier consist of one cell. For each
28 - suspend : specifier consist of one cell. For each
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dnvidia,tegra114-spi.txt11 - resets : Must contain an entry for each entry in reset-names.
15 - dmas : Must contain an entry for each entry in clock-names.
20 - clocks : Must contain an entry for each entry in clock-names.
Dnvidia,tegra20-sflash.txt9 - resets : Must contain an entry for each entry in reset-names.
13 - dmas : Must contain an entry for each entry in clock-names.
Dnvidia,tegra20-slink.txt9 - resets : Must contain an entry for each entry in reset-names.
13 - dmas : Must contain an entry for each entry in clock-names.
Dspi-img-spfi.txt7 - clocks: Must contain an entry for each entry in clock-names.
12 - dmas: Must contain an entry for each entry in dma-names.
Dspi-sirf.txt10 - dmas : Must contain an entry for each entry in clock-names.
15 - clocks : Must contain an entry for each entry in clock-names.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-kernel-livepatch9 each loaded live patch module.
16 The patch directory contains subdirectories for each kernel
33 The object directory contains subdirectories for each function
Dsysfs-devices-soc5 The /sys/devices/ directory contains a sub-directory for each
7 regarding each SoC can be obtained by reading sysfs files. This
10 The directory created for each SoC will also house information
56 interest, as it contains a symlink for each SoC device found on
Dsysfs-bus-usb-devices-usbsevseg24 raw: each character controls its segment manually
25 hex: each character is between 0-15
26 ascii: each character is between '0'-'9' and 'A'-'F'.
Dsysfs-kernel-iommu_groups6 directories, each representing an IOMMU group. The
8 for the group, which is an integer value. Within each
Dsysfs-gpio19 /gpioN ... for each exported GPIO #N
23 /gpiochipN ... for each gpiochip; #N is its first GPIO
Dsysfs-ata12 For each port, a directory ataX is created where X is the ata_port_id of
26 Behind each port, there is a ata_link. If there is a SATA PM in the
49 Behind each link, up to two ata device are created.
Dsysfs-class-pwm15 A /sys/class/pwm/pwmchipN directory is created for each
47 each exported PWM channel where X is the exported PWM
Dsysfs-driver-xen-blkback6 Maximum number of free pages to keep in each block
/linux-4.1.27/Documentation/devicetree/bindings/ata/
Dtegra-sata.txt11 - clocks : Must contain an entry for each entry in clock-names.
18 - resets : Must contain an entry for each entry in reset-names.
24 - phys : Must contain an entry for each entry in phy-names.
Dahci-platform.txt6 It is possible, but not required, to represent each port as a sub-node.
7 It allows to enable each port independently when dealing with multiple
/linux-4.1.27/Documentation/cpu-freq/
Dcpufreq-stats.txt20 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
23 in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
53 This gives the amount of time spent in each of the frequencies supported by
54 this CPU. The cat output will have "<frequency> <time>" pair in each line, which
56 will have one line for each of the supported frequencies. usertime units here
85 contains the actual freq values for each row and column for better readability.
Damd-powernow.txt5 there is a different cpu-freq driver for each generation.
8 so it is safe to try each driver in turn when in doubt as to
/linux-4.1.27/Documentation/vm/
Dpage_owner.txt1 page owner: Tracking about who allocated each page
6 page owner is for the tracking about who allocated each page.
9 and order of pages is stored into certain storage for each page.
14 using it for analyzing who allocate each page is rather complex. We need
22 each page. It is already implemented and activated if page owner is
80 See the result about who allocated each page
Dpagemap.txt11 physical frame each virtual page is mapped to. It contains one 64-bit
12 value for each virtual page, containing the following data (from
35 times each page is mapped, indexed by PFN.
37 * /proc/kpageflags. This file contains a 64-bit set of flags for each
147 4. Read a u64 for each page from pagemap.
148 5. Open /proc/kpagecount and/or /proc/kpageflags. For each PFN you just
/linux-4.1.27/Documentation/networking/
Dscaling.txt26 applying a filter to each packet that assigns it to one of a small number
27 of logical flows. Packets for each flow are steered to a separate receive
37 implementation of RSS uses a 128-entry indirection table where each entry
54 for each CPU if the device supports enough queues, or otherwise at least
55 one for each memory domain, where a memory domain is a set of CPUs that
71 that can route each interrupt to a particular CPU. The active mapping
76 affinity of each interrupt see Documentation/IRQ-affinity.txt. Some systems
90 interrupts (and thus work) grows with each additional queue.
93 processors with hyperthreading (HT), each hyperthread is represented as
129 RPS may enqueue packets for processing. For each received packet,
[all …]
Dnetif-msg.txt14 From the beginning of Linux, each network device driver has had a local
27 6 Status on each completed Tx packet and received Rx packets
30 Initially this message level variable was uniquely named in each driver
Dvxge.txt25 supported independently on each function.
80 Specifies maximum VPATH(s) configured for each device function.
Dfib_trie.txt38 instead of a pure binary tree, each internal node ("tnode") may
77 towards the root from a given tnode, doing a resize() at each step
104 entire trie for each prefix length. In comparison, fib_hash is organized
131 Inside each tnode, the search for longest matching prefix consists of searching
/linux-4.1.27/Documentation/devicetree/bindings/timer/
Drenesas,mtu2.txt18 - interrupts: interrupt specifiers for the timer, one for each entry in
20 - interrupt-names: must contain one entry named "tgi?a" for each enabled
24 - clocks: a list of phandle + clock-specifier pairs, one for each entry
Dti,keystone-timer.txt6 timers, each half can operate in conjunction (chain mode) or independently
7 (unchained mode) of each other.
Ddigicolor-timer.txt8 - interrupts : Contains 8 interrupts, one for each timer
Dstericsson-u300-apptimer.txt7 - interrupts : A list of 4 interrupts; one for each subtimer. These
Drockchip,rk3288-timer.txt7 - clocks : must contain an entry for each entry in clock-names
/linux-4.1.27/Documentation/devicetree/bindings/hsi/
Domap-ssi.txt9 - reg: Contains a matching register specifier for each entry
12 - interrupts: Contains matching interrupt information for each entry
20 - clocks: Contains a matching clock specifier for each entry in
31 - reg: Contains a matching register specifier for each entry
/linux-4.1.27/Documentation/block/
Dnull_blk.txt21 All of them have a completion queue for each core in the system.
52 2: Timer: Waits a specific period (completion_nsec) for each IO before
56 Combined with irqmode=2 (timer). The time each completion event must wait.
72 queue for each CPU node in the system.
Dqueue-sysfs.txt5 for each block device. Note that stacked devices typically do not export
93 queue maintains a separate request pool per each cgroup when
94 CONFIG_BLK_CGROUP is enabled, and this parameter applies to each such
96 each request queue may have up to N request pools, each independently
Dcfq-iosched.txt88 to recompute the slice time for each process based on the target_latency set
90 latency (setting it to 0) ignores target latency, allowing each process in the
101 time for each process to issue I/O request before the cfq queue is switched.
149 CFQ supports blkio cgroup and has "blkio." prefixed files in each
158 Another way to think about it is assuming that each internal node has
186 If all cgroups have active IOs and competing with each other, disk
241 On this tree we idle on each queue individually.
269 100ms each. If a REQ_NOIDLE request comes in, it will be scheduled
/linux-4.1.27/Documentation/device-mapper/
Dstatistics.txt10 Individual statistics will be collected for each step-sized area within
13 The I/O statistics counters for each step-sized area of a region are
25 on each other's data.
46 "<area_size>" - the range is subdivided into areas each containing
94 Print counters for each step-sized area of a region.
107 Output format for each step-sized area of a region:
171 Set the auxillary data string to "foo bar baz" (the escape for each
Ddm-queue-length.txt8 Table parameters for each path: [<repeat_count>]
14 Status for each path: <status> <fail-count> <in-flight>
Ddm-service-time.txt8 The service time for each path is estimated by dividing the total size
15 Table parameters for each path: [<repeat_count> [<relative_throughput>]]
27 Status for each path: <status> <fail-count> <in-flight-size> \
Dswitch.txt19 consists of a number of distinct storage arrays ("members") each having
24 how many members are being used. When iSCSI sessions are created, each
53 The lower tier consists of a single dm multipath device for each member.
63 use 4 bits for each address range in a 16 member group (which is very
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dmarvell,mvebu-pinctrl.txt4 (mpp) to a specific function. For each SoC family there is a SoC specific
17 Please refer to each marvell,<soc>-pinctrl.txt binding doc for supported SoCs.
24 valid pin/pin group names and available function names for each SoC.
Dfsl,imx-pinctrl.txt5 multiplexing the PAD input/output signals. For each PAD there are up to
22 Please refer to each fsl,<soc>-pinctrl.txt binding doc for supported SoCs.
25 - fsl,pins: each entry consists of 6 integers and represents the mux and config
41 Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
94 User should refer to each SoC spec to set the correct value.
Dpinctrl-bindings.txt9 designated client devices. Again, each client device must be represented as a
16 device is inactive. Hence, each client device can define a set of named
35 For each client device individually, every pin state is assigned an integer
36 ID. These numbers start at 0, and are contiguous. For each state ID, a unique
47 pinctrl-0: List of phandles, each pointing at a pin configuration
52 from multiple nodes for a single pin controller, each
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
120 The contents of each of those pin configuration child nodes is defined
/linux-4.1.27/Documentation/filesystems/nfs/
Dpnfs.txt5 reference multiple devices, each of which can reference multiple data servers.
18 We reference the header for the inode pointing to it, across each
20 LAYOUTCOMMIT), and for each lseg held within.
31 nfs4_deviceid_cache). The cache itself is referenced across each
33 the lifetime of each lseg referencing them.
61 layout types: "files", "objects", "blocks", and "flexfiles". For each
/linux-4.1.27/Documentation/auxdisplay/
Dks010841 Addresses: 64 each page
42 Data size: 1 byte each address
Dcfag12864b43 Pages: 8 each controller
44 Addresses: 64 each page
45 Data size: 1 byte each address
/linux-4.1.27/Documentation/devicetree/bindings/net/
Damd-xgbe.txt13 interrupt for each DMA channel supported by the device should be specified
30 a unique interrupt for each DMA channel - this requires an additional
31 interrupt be configured for each DMA channel
Dkeystone-netcp.txt16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
94 - interfaces: specification for each of the switch port to be registered as a
111 - secondary-slave-ports: specification for each of the switch port not be
124 - rx-queue-depth: number of descriptors in each of the free descriptor
127 - rx-buffer-size: the buffer size for each of the Rx flow FDQ.
139 - "netcp-device label": phandle to the device specification for each of NetCP
Dmdio-mux-gpio.txt9 - gpios : GPIO specifiers for each GPIO line. One or more must be specified.
25 PHYs each.
Dmdio-mux.txt5 bus multiplexer/switch will have one child node for each child bus.
34 PHYs each.
/linux-4.1.27/Documentation/devicetree/bindings/crypto/
Datmel-crypto.txt13 - dma-names: Contains one identifier string for each DMA specifier
35 - dma-names: Contains one identifier string for each DMA specifier
58 - dma-names: Contains one identifier string for each DMA specifier
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Dl3-noc.txt12 - reg: Contains L3 register address range for each noc domain.
13 - ti,hwmods: "l3_main_1", ... One hwmod for each noc domain.
/linux-4.1.27/Documentation/devicetree/bindings/nvec/
Dnvidia,nvec.txt10 - clocks : Must contain an entry for each entry in clock-names.
18 - resets : Must contain an entry for each entry in reset-names.
/linux-4.1.27/net/rds/
Dinfo.c220 BUG_ON(lens.each == 0); in rds_info_getsockopt()
222 total = lens.nr * lens.each; in rds_info_getsockopt()
231 ret = lens.each; in rds_info_getsockopt()
Dinfo.h6 unsigned int each; member
/linux-4.1.27/Documentation/scheduler/
Dsched-domains.txt9 i. The top domain for each CPU will generally span all CPUs in the system
23 Balancing within a sched domain occurs between groups. That is, each group
25 load of each of its member CPUs, and only when the load of a group becomes
28 In kernel/sched/core.c, trigger_load_balance() is run periodically on each CPU
51 of SMT, you'll span all siblings of the physical CPU, with each group being
56 of the SMP domain will span the entire machine, with each group having the
Dsched-design-CFS.txt17 power and which can run each task at precise equal speed, in parallel, each at
19 each at 50% physical power --- i.e., actually in parallel.
202 fair CPU time to each task. Sometimes, it may be desirable to group tasks and
203 provide fair CPU time to each such task group. For example, it may be
204 desirable to first provide fair CPU time to each user on the system and then to
205 each task belonging to a user.
220 When CONFIG_FAIR_GROUP_SCHED is defined, a "cpu.shares" file is created for each
Dsched-stats.txt13 statistics for each cpu listed, and there may well be more than one
24 the change in the counters at each subsequent observation. A perl script
59 One of these is produced per domain for each cpu described. (Note that if
76 4) sum of imbalances discovered (if any) with each call to
93 12) sum of imbalances discovered (if any) with each call to
109 20) sum of imbalances discovered (if any) with each call to
Dsched-bwc.txt11 each given "period" (microseconds), a group is allowed to consume only up to
18 above at each period boundary. As threads consume this bandwidth it is
20 within each of these updates is tunable and described as the "slice".
55 on large systems. The amount transferred each time such an update is required
/linux-4.1.27/Documentation/devicetree/bindings/hwmon/
Dltc2978.txt14 - regulators: A node that houses a sub-node for each regulator controlled by
16 values listed below. The content of each sub-node is defined by the
/linux-4.1.27/Documentation/devicetree/bindings/soc/mediatek/
Dpwrap.txt27 - reg: Must contain an entry for each entry in reg-names.
31 - resets: Must contain an entry for each entry in reset-names.
35 - clocks: Must contain an entry for each entry in clock-names.
/linux-4.1.27/Documentation/devicetree/bindings/pwm/
Dpwm.txt16 PWM properties should be named "pwms". The exact meaning of each pwms
17 property must be documented in the device tree binding for each device.
19 each of the PWM devices listed in the "pwms" property. If no "pwm-names"
Dpwm-fsl-ftm.txt28 - clocks: Must contain a phandle and clock specifier for each entry in
32 - pinctrl-NNN: One property must exist for each entry in pinctrl-names.
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Dinterrupt.txt33 The megamodule PIC consists of four interrupt mupliplexers each of which
37 One for each core interrupt priority level. In addition to the combined
50 - interrupts: This should have four cells; one for each interrupt combiner.
59 core priority 15. The value of each cell is the
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
D88pm800.txt6 - regulators: A node that houses a sub-node for each regulator within the
9 The content of each sub-node is defined by the standard binding for
Disl9305.txt7 - regulators: A node that houses a sub-node for each regulator within the
9 values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
Dda9211.txt7 - regulators: A node that houses a sub-node for each regulator within the
9 values listed below. The content of each sub-node is defined by the
Dmax8907.txt14 - regulators: A node that houses a sub-node for each regulator within the
17 The content of each sub-node is defined by the standard binding for
Dregulator.txt35 every hardware so the valid modes are documented on each regulator
38 modes depends on the capabilities of every hardware so each device binding
44 describes each regulator, then this property indicates which regulator
D88pm860x.txt6 - regulators: A node that houses a sub-node for each regulator within the
Dpwm-regulator.txt6 - voltage-table: voltage and duty table, include 2 members in each set of
/linux-4.1.27/Documentation/usb/
Dgadget_configfs.txt20 A gadget is seen by its host as a set of configurations, each of which contains
22 functions, each function representing e.g. a serial connection or a SCSI disk.
27 and which functions each configuration will provide.
62 For each gadget to be created its corresponding directory must be created:
83 for each language, e.g.:
111 for each language, e.g.:
126 The gadget will provide some functions, for each function its corresponding
148 At this moment a number of gadgets is created, each of which has a number of
366 all configurations, and in each configuration it iterates over all
Dmass-storage.txt5 multiple logical units (LUNs). Backing storage for each LUN is
35 backing storage for each logical unit. There may be at most
52 This parameter specifies whether each logical unit should be
83 This parameter specifies whether each logical unit should simulate
88 This parameter specifies whether each logical unit should be
107 Write(10,12) commands. This forces each write to wait until the
151 For each logical unit, the gadget creates a directory in the sysfs
213 values for each logical unit. If one uses only a single logical
215 needs to be repeated for each logical unit.
Dmisc_usbsevseg.txt20 raw controls each segment manually,
42 To set multiple decimals points sum up each power.
Dgadget_multi.txt46 tries to much drivers for each individual interface (sort of, don't
56 *** Installing drivers for each function
58 The other, trickier thing is making Windows install drivers for each
85 functions will obviously change interface numbers for each of the
/linux-4.1.27/Documentation/devicetree/bindings/reset/
Dreset.txt23 the DT node of each affected HW block, since if activated, an unrelated block
29 rather than to slavishly enumerate the reset signal that affects each HW
49 for each reset signal that affects the device, or that the
73 This represents a bus that controls the reset signal of each of four sub-
/linux-4.1.27/Documentation/sound/alsa/
DMIXART.txt26 One miXart8 board will be represented as 4 alsa cards, each with 1
42 can be muted for each stream to use 8 analog/digital outputs separately.
52 <PCM 0-3> and <PCM Capture> : digital volume control of each analog substream.
53 <AES 0-3> and <AES Capture> : digital volume control of each AES/EBU substream.
DChannel-Mapping-API.txt12 A channel map is an array of position for each PCM channel.
39 As a ground design, each PCM substream may contain a control element
60 position value for each channel.
139 containing the position of each channel.
DHD-Audio.txt23 bugs and issues specific to each controller type. The snd-hda-intel
111 codec slots via `probe_mask` option. It's a bitmask, and each bit
171 configuration of each pin, which indicates the location, the
193 and `model` options belonging to each codec. For example, for Realtek
246 - IDT codecs may have extra power-enable/disable controls on each
311 options. Note that each of them corresponds to the codec chip, not
318 (one per each codec), and you have a raw access to the device via
336 It shows most of useful information of each codec widget.
339 each codec slot. You can know the codec vendor, product id and
340 names, the type of each widget, capabilities and so on.
[all …]
/linux-4.1.27/Documentation/fb/
Dinternals.txt62 color (including red, green, and blue intensities) for each possible pixel
73 The pixel value is broken up into red, green, and blue fields, each of which
81 each other.
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-mux.txt5 multiplexer/switch will have one child node for each child
26 with two NXP pca8574 GPIO expanders attached, one each to
Dnvidia,tegra20-i2c.txt42 - clocks: Must contain an entry for each entry in clock-names.
50 - resets: Must contain an entry for each entry in reset-names.
54 - dmas: Must contain an entry for each entry in clock-names.
Di2c-mux-pinctrl.txt28 * Standard pinctrl properties that specify the pin mux state for each child
35 For each named state defined in the pinctrl-names property, an I2C child bus
Di2c-pxa-pci-ce4100.txt5 PCI device has three PCI-bars, each bar contains a complete I2C
18 each range (last cell). In this particular case,
/linux-4.1.27/drivers/staging/panel/
Dlcd-panel-cgram.txt5 (';'). Each couple of digits represents a line, with 1-bits for each
8 bits of the 7 first bytes are used for each character. If the string
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Dfsl-lpuart.txt11 - clocks : phandle + clock specifier pairs, one for each entry in clock-names
15 - dmas: A list of two dma specifiers, one for each entry in dma-names.
Dnvidia,tegra20-hsuart.txt9 - resets : Must contain an entry for each entry in reset-names.
13 - dmas : Must contain an entry for each entry in clock-names.
/linux-4.1.27/Documentation/input/
Damijoy.txt66 These addresses each read a 16 bit register. These in turn
70 loaded with the 4 quadrature inputs from each of two game
100 Bits 1 and 0 of each counter (Y1-Y0,X1-X0) may be
130 These addresses each read a pair of 8 bit pot counters.
133 from 2 controller connectors (left-right) with 2 pins each.
Dedt-ft5x06.txt48 values for each sensor field. Note that each read() call on this
/linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt12 - clocks: Must contain a phandle and clock specifier pair for each entry in
17 - resets: Must contain an entry for each entry in reset-names. See
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dtwd.txt17 - interrupts : One interrupt to each core
37 - interrupts : One interrupt to each core
Dvexpress-sysreg.txt22 by subnodes, each of them requiring the following properties:
82 - first cell of each group defines the function number
84 - second cell of each group defines device number (eg. osc 0,
/linux-4.1.27/fs/sysfs/
DKconfig11 kernel, such as the devices the kernel has discovered on each bus and
12 which driver each is bound to. sysfs can also be used to tune devices
/linux-4.1.27/Documentation/devicetree/bindings/
Dgraph.txt14 have multiple specifiable ports, each of which can be linked to one or more
31 Each port node contains an 'endpoint' subnode for each remote device port
33 remote device, an 'endpoint' child node must be provided for each link.
94 'remote-endpoint' phandles pointing at each other form a link between the
/linux-4.1.27/Documentation/filesystems/
Dqnx6.txt36 Each qnx6fs got two superblocks, each one having a 64bit serial number.
38 In write mode with reach new snapshot (after each synchronous write), the
51 If the level value is 0, up to 16 direct blocks can be addressed by each
53 Level 1 adds an additional indirect addressing level where each indirect
70 0x1000 is the size reserved for each superblock - regardless of the
97 It is a specially formatted file containing records which associate each
139 root node in the superblock and each bit in the bitmap represents one
Dsquashfs.txt120 To maximise compression there are different inodes for each file type
143 entries, each of which share the shared start block. A new directory header
148 file lookup. Directory indexes store one entry per metablock, each entry
150 in each metadata block. Directories are sorted in alphabetical order,
164 of each datablock is stored in a block list contained within the
214 The xattr table contains extended attributes for each inode. The xattrs
215 for each inode are stored in a list, each list entry containing a type,
228 location of the xattr list inside each inode, a 32-bit xattr id
Dgfs2-glocks.txt47 are defined for each type of glock. Not all types of glocks use
68 The minimum hold time for each lock is the time after a remote lock
129 the same information is gathered in each case. The super
217 The sbstats file contains a set of these stats for each glock type (so 8 lines
218 for each type) and for each cpu (one column per cpu). The glstats file contains
219 a set of these stats for each glock in a similar format to the glocks file, but
220 using the format mean/variance for each of the timing stats.
223 for the glock in question, along with some addition information on each dlm
Dlogfs.txt32 Segments are the primary write unit of LogFS. Within each segments,
54 objects, each consisting of the object header and the payload.
70 each level requires its own separate segment to be open for writing.
84 implementation would require that for each write or a block, all
178 tables of increasing size are used. For each table, the hash value
189 entries each.
235 logfs uses the top half of each inode's address space. The low 8TB
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dnvidia,tegra20-pcie.txt9 - reg: A list of physical base address and length for each set of controller
10 registers. Must contain an entry for each entry in the reg-names property.
16 entry for each entry in the interrupt-names property.
30 PCI regions. The entries must be 6 cells each, where the first three cells
49 - clocks: Must contain an entry for each entry in clock-names.
56 - resets: Must contain an entry for each entry in reset-names.
64 - phys: Must contain an entry for each entry in phy-names.
Dxgene-pci.txt6 - reg: A list of physical base address and length for each set of controller
7 registers. Must contain an entry for each entry in the reg-names
/linux-4.1.27/Documentation/spi/
Dspidev66 of devices at a time. Just provide one spi_board_info record for each such
67 SPI device, and you'll get a /dev device node for each device.
99 is right-justified in each word, so that unused (TX) or undefined (RX)
104 each SPI transfer word. The value zero signifies eight bits.
124 - There's a limit on the number of bytes each I/O request can transfer
145 each response. (Other protocol options include changing the word size
146 and bitrate for each transfer segment.)
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dfsl-edma.txt16 - interrupts : A list of interrupt-specifiers, one for each entry in
31 - clocks : A list of phandle and clock-specifier pairs, one for each entry in
60 in the dma.txt file, using a two-cell specifier for each channel: the 1st
Dqcom_adm.txt12 - resets: Must contain an entry for each entry in reset names.
39 cell specifier for each channel.
Ddma.txt41 - dmas: List of one or more DMA specifiers, each consisting of
49 - dma-names: Contains one identifier string for each DMA specifier in
Drenesas,rcar-dmac.txt21 - interrupts: interrupt specifiers for the DMAC, one for each entry in
27 - clocks: a list of phandle + clock-specifier pairs, one for each entry
/linux-4.1.27/Documentation/devicetree/
Ddynamic-resolution-notes.txt21 4. For each property in the __fixups__ node locate the node it references
24 6. For each fixup in the property locate the node:property:offset location
Dusage-model.txt145 Again on ARM, for each machine_desc, the kernel looks to see if
150 on which entry in the compatible property each machine_desc matches
173 hook from each machine_desc, and the first one returning TRUE is used.
241 instead of hard coding static devices for each platform, the list of
321 of device each node represents, or even if a node represents a device
327 together to create the audio subsystem. I know what each device is
329 know what to do with each node?
337 For each of these nodes, Linux allocates and registers a
343 example, each i2c_client is a child of an i2c_master. Each spi_device
367 i2c_client for each child node, an SPI bus driver will register
[all …]
/linux-4.1.27/Documentation/driver-model/
Dbus.txt55 iterated over, and the match callback is called for each device that
69 The LDM core provides helper functions for iterating over each list.
78 for each device or driver in the list. All list accesses are
80 count on each object in the list is incremented before the callback is
/linux-4.1.27/Documentation/devicetree/bindings/drm/imx/
Dldb.txt7 nodes describing each of the two LVDS encoder channels of the bridge.
15 interfaces as input for each LVDS channel.
32 The needed clock numbers for each are documented in
56 limitations, only one input port (port@[0,1]) can be used for each channel
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dpistachio-clock.txt28 - clocks: Must contain an entry for each clock in clock-names.
57 - clocks: Must contain an entry for each clock in clock-names.
85 - clocks: Must contain an entry for each clock in clock-names.
109 - clocks: Must contain an entry for each clock in clock-names.
Drockchip.txt15 the 10 individual gates containing 16 clocks each.
23 - clocks : should contain the parent clock for each individual gate,
/linux-4.1.27/arch/cris/
DKconfig350 If you do not enable DMA, an interrupt for each character will be
360 If you do not enable DMA, an interrupt for each character will be
385 If you do not enable DMA, an interrupt for each character will be
395 If you do not enable DMA, an interrupt for each character will be
420 If you do not enable DMA, an interrupt for each character will be
454 If you do not enable DMA, an interrupt for each character will be
477 If you do not enable DMA, an interrupt for each character will be
487 If you do not enable DMA, an interrupt for each character will be
512 If you do not enable DMA, an interrupt for each character will be
522 If you do not enable DMA, an interrupt for each character will be
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-dsp-keystone.txt4 the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
11 - each GPIO can be configured only as output pin;
Dgpio-vf610.txt5 each, and each PORT module has its own interrupt.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dpar_io.txt4 The node should reside in the "soc" node of the tree. For each
26 the new device trees. Instead, each Par I/O bank should be represented
/linux-4.1.27/Documentation/hwmon/
Dibmpowernv17 'hwmon' populates the 'sysfs' tree having attribute files, each for a given
20 All the nodes in the DT appear under "/ibm,opal/sensors" and each valid node in
Dlm9352 voltages. To set fan speed, the LM93 has two PWM outputs that are each
135 and pwm2_override are used to enable this mode; each is a boolean integer
137 and pwm2 are used to set the manual duty cycle; each is an integer (0-255)
157 points of configuration. To start, each PWM output can be bound to any
200 There is an independent base temperature for each temperature channel. Note,
201 however, there are only two tables of offsets: one each for temp[12] and
212 temp<n>_auto_pwm_min. Note, there are only two minimums: one each for temp[12]
235 steps. The duration of each step is configurable. There are two files, with
236 one value each in seconds: pwm_auto_prochot_ramp and pwm_auto_vrdhot_ramp.
244 For each temperature channel, there is a boost temperature: if the channel
Dw83792d95 The chips only update values each 3 seconds; reading them more often will
154 for each fan.
172 sf2_point[1-4]_fan[1-3] - four temperature points for each fan for Smart Fan II
173 sf2_level[1-3]_fan[1-3] - three PWM/DC levels for each fan for Smart Fan II
/linux-4.1.27/Documentation/virtual/kvm/devices/
Dxics.txt11 sources, each identified by a 20-bit source number, and a set of
13 each associated with a virtual CPU.
16 capability for each vcpu, specifying KVM_CAP_IRQ_XICS in args[0] and
Dmpic.txt9 MPIC will act as the system interrupt controller, connecting to each
29 IRQ input line for each standard openpic source. 0 is inactive and 1
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds242319 Result of each page is provided as an ASCII output where each counter
25 If the operation was successful, there is also in the end of each line
/linux-4.1.27/Documentation/video4linux/
Dvivid.txt9 Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs.
94 node_types: which devices should each driver instance create. An array of
95 hexadecimal values, one for each instance. The default is 0x1d3d.
112 num_inputs: the number of inputs, one for each instance. By default 4 inputs
113 are created for each video capture device. At most 16 inputs can be created,
116 input_types: the input types for each instance, the default is 0xe4. This defines
117 what the type of each input is when the inputs are created for each driver
118 instance. This is a hexadecimal value with up to 16 pairs of bits, each
133 num_outputs: the number of outputs, one for each instance. By default 2 outputs
134 are created for each video output device. At most 16 outputs can be
[all …]
/linux-4.1.27/drivers/staging/unisys/Documentation/
Dproc-entries.txt25 /proc/uislib/vbus: this is a directory containing entries for each
47 /proc/virtnic/ethX: This is a directory containing entries for each
65 directory for each device provided by that module. Each device has a
92 partition configuration data for each virtual bus, for use during
/linux-4.1.27/Documentation/
DIRQ-domain.txt4 space where each separate IRQ source is assigned a different number.
7 that each one gets assigned non-overlapping allocations of Linux
41 calling one of the irq_domain_add_*() functions (each mapping method
67 to Linux irq, and each mechanism uses a different allocation function.
167 hardware architecture, an irq_domain data structure is built for each
200 irq_domain structure is built for each interrupt controller, and an
201 irq_data structure is allocated for each irq_domain associated with an
203 irq_chip. That is, an irq_chip is associated with each irq_data along
DDMA-attributes.txt29 may be weakly ordered, that is that reads and writes may pass each other.
65 set on each call.
77 having a mapping created separately for each device and is usually
79 for the given buffer with device pointer to each device taking part in
Ddynamic-debug-howto.txt78 The third column shows the currently enabled flags for each debug
124 with implicit ANDs between each pair. Note that an empty list of
146 The meanings of each keyword are:
150 of each callsite. Example:
157 each callsite. Examples:
165 of each callsite. The module name is the string as
190 against the line number of each pr_debug() callsite. A single
281 "foo" is extracted from the param-name, and applied to each query in
282 "QUERY", and only 1 match-spec of each type is allowed.
Diostats.txt40 each snapshot of your disk statistics.
48 eleven fields of statistics, each meaning exactly the same things.
63 Reads and writes which are adjacent to each other may be merged for
87 This field is incremented at each I/O start, I/O completion, I/O
100 In 2.6, there are counters for each CPU, which make the lack of locking
/linux-4.1.27/Documentation/powerpc/
Dqe_firmware.txt60 The QE architecture allows for only one microcode present in I-RAM for each
72 allows each processor to run a different microcode, effectively creating an
127 | 0 | General | Indicates that prior to each host command |
158 | | | for each SNUM of Ethernet TX thread. |
206 must be one and only one 'microcode' structure for each RISC processor.
236 'vtraps' is an array of 8 words that contain virtual trap values for each
241 For each RISC processor there is one 'microcode' structure. The first
248 for each of the 16 traps. If trap[i] is 0, then this particular
Dcxl.txt46 translation services to allow each AFU direct access to userspace
77 with each of its requests. This tells the PSL which context is
78 associated with each operation. If the PSL can't translate an
147 opened once for each context that is available.
152 Note: IRQs need to be allocated for each context, which may limit
256 each event is of type struct cxl_event, of varying size.
375 identical for each:
Dpci_iov_resource_on_powernv.txt22 cleared independently) for each PE.
48 - For DMA we then provide an entire address space for each PE that can
87 maps each segment to a PE#. That allows portions of the MMIO space
171 This region is divided into eight contiguous 1MB regions, each of which
197 - Multiple segmented M64 windows: As usual, each window is split into 256
200 and different segment sizes. If we have VFs that each have a 1MB BAR
210 The goal is of course to be able to give a separate PE for each VF.
214 divided into 256 segments, with each segment corresponding to one PE.
292 Then each VF will be in its own PE. The VF BARs (and therefore the PE#s)
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dtegra-soctherm.txt16 - clocks : Must contain an entry for each entry in clock-names.
21 - resets : Must contain an entry for each entry in reset-names.
Drockchip-thermal.txt9 - clocks : Must contain an entry for each entry in clock-names.
12 - resets : Must contain an entry for each entry in reset-names.
/linux-4.1.27/Documentation/devicetree/bindings/fuse/
Dnvidia,tegra20-fuse.txt19 - clocks: Must contain an entry for each entry in clock-names.
23 - resets: Must contain an entry for each entry in reset-names.
/linux-4.1.27/Documentation/power/powercap/
Dpowercap.txt19 given zone belongs to. They each contain attributes for monitoring power, as
22 bigger part consists of multiple smaller parts that each have their own power
159 In addition to that, each power zone contains a name attribute, allowing the
167 with two different time windows to be applied to each power zone. Thus for
168 each zone there are 2 attributes representing the constraint names, 2 power
/linux-4.1.27/Documentation/scsi/
Dmegaraid.txt43 both mptraid and megaraid would register with lsiioctl for each
54 (currently only megaraid) register each controller with the common module.
67 Common module dedicates one uioc_t packet to each controller registered. This
/linux-4.1.27/Documentation/fmc/
Dfmc-fakedev.txt6 Unlike the SPEC driver, which creates an FMC device for each PCI cards
13 replicated for each fake mezzanine.
Dfmc-trivial.txt9 different gateware file in each card. The whole list of parameters it
/linux-4.1.27/Documentation/timers/
Dhpet.txt10 each of which can generate oneshot interrupts and at least one of which has
13 independent of each other ... these share a counter, complicating resets.
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dgr-udc.txt24 each OUT endpoint of the core. Fewer entries overrides the default sizes
30 each IN endpoint of the core. Fewer entries overrides the default sizes
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt19 - interrupts : each one of the interrupts here is one entry per 32 MSIs,
99 In the PAMU, each PCI controller is given only one primary window. The
104 PAMU primary windows can be divided into 256 subwindows, and each
106 physical"). However, each subwindow has to have the same alignment, which
Draideng.txt30 There must be a sub-node for each job queue present in RAID Engine
48 There must be a sub-node for each job ring present in RAID Engine
/linux-4.1.27/arch/blackfin/mach-bf609/
DKconfig38 The slave interface id of each slot should be set according following table.
221 The slave interface id of each slot should be set according following table.
404 The slave interface id of each slot should be set according following table.
587 The slave interface id of each slot should be set according following table.
770 The slave interface id of each slot should be set according following table.
953 The slave interface id of each slot should be set according following table.
1048 The slave interface id of each slot should be set according following table.
1169 The slave interface id of each slot should be set according following table.
1235 The slave interface id of each slot should be set according following table.
1334 The slave interface id of each slot should be set according following table.
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/panel/
Dsharp,lq101r1sx01.txt4 - left-right: each channel drives the left or right half of the screen
5 - even-odd: each channel drives the even or odd lines of the screen
/linux-4.1.27/Documentation/rapidio/
Dsysfs.txt8 For each RapidIO device, the RapidIO subsystem creates files in an individual
45 In addition to the files listed above, each device has a binary attribute file
76 each entry.
87 Device-specific switch attributes are listed for each RapidIO switch driver
138 the corresponding subdirectory will also contain subdirectories for each
/linux-4.1.27/Documentation/locking/
Dlockdep-design.txt15 struct is one class, while each inode has its own instantiation of that
54 The bit position indicates STATE, STATE-read, for each of the states listed
55 above, and the character displayed in each indicates:
138 locks in this fixed order on each of the objects.
217 sequence of locks taken after each other) only once. A simple stack of
239 will result in lock-class leakage. The issue here is that each
248 a hash table with 8192 buckets where each bucket has its own
249 spinlock_t will consume 8192 lock classes -unless- each spinlock
254 In contrast, a loop that called spin_lock_init() on each lock
/linux-4.1.27/tools/perf/tests/attr/
Dtest-record-graph-dwarf9 # TODO different for each arch, no support for that now
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm7038-l1-intc.txt4 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip
13 - A separate instance of the register set for each CPU, allowing individual
/linux-4.1.27/Documentation/networking/caif/
DLinux-CAIF.txt58 each layer described in the specification is implemented as a separate layer.
65 - Layered architecture (a la Streams), each layer in the CAIF
150 - In order to send data upwards, each layer should do
152 - In order to send data downwards, each layer should do
/linux-4.1.27/Documentation/devicetree/bindings/arm/samsung/
Dinterrupt-combiner.txt5 for the group. The interrupt request from each group are connected to a parent
17 can accommodate up to 4 interrupt combiners (with each combiner supporting
/linux-4.1.27/fs/jffs2/
DTODO3 let each outstanding write reserve the _maximum_ amount of physical
26 are likely to become dirty, and end up with blocks which are each far
/linux-4.1.27/Documentation/arm/
DCCN.txt5 (XPs), with each crosspoint supporting up to two device ports,
52 per each CPU.
DInterrupts11 There is more assembly code inside each of these functions, mainly to
31 exclusive of each other - if you're processing one interrupt from the
90 For each IRQ, we keep the following information:
151 acknowledge the SA1110 IRQ each time you re-read the SA1111 IRQ status.
/linux-4.1.27/sound/soc/dwc/
DKconfig8 maximum of 8 channels each for play and record.
/linux-4.1.27/Documentation/cgroups/
Dcgroups.txt58 hierarchy, and a set of subsystems; each subsystem has system-specific
59 state attached to each cgroup in the hierarchy. Each hierarchy has
77 tasks in each cgroup.
97 different subsystems - having parallel hierarchies allows each
103 At one extreme, each resource controller or subsystem could be in a
175 cgroup_subsys_state objects, one for each cgroup subsystem
177 the cgroup of which it's a member in each hierarchy, but this
184 field of each task_struct using the css_set, anchored at
227 for each active hierarchy, the subsystem names and the cgroup name
245 Other subsystems such as cpusets may add additional files in each
[all …]
/linux-4.1.27/drivers/auxdisplay/
DKconfig51 many parallel ports are present and which address each one has.
59 int "Delay between each control writing (microseconds)"
63 Amount of time the ks0108 should wait between each control write
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.txt15 - led-cur: Current setting at each led channel (mA x10, 0 if led is not connected)
16 - max-cur: Maximun current at each led channel.
27 Alternatively, each child can have a specific channel name and trigger:
/linux-4.1.27/tools/perf/Documentation/
Dperf-script-perl.txt26 That will generate a starter script containing a handler for each of
28 field for each event in the trace file.
40 'handler function' is called for each event in the trace. If there's
93 Here's a brief description of each of the invariant event args:
163 The remaining sections provide descriptions of each of the available
Dperf-evlist.txt25 Show just the sample frequency used for each event.
/linux-4.1.27/drivers/usb/usbip/
Dusbip_protocol.txt154 0x144 | | m_0 | From now on each interface is described, all
269 | | | each ISO packets is not transmitted.
315 | | | between each ISO packets is not transmitted.
336 | | | between each ISO packets is not transmitted.
358 | | | between each ISO packets is not transmitted.
/linux-4.1.27/arch/m68k/ifpsp060/
DTEST.DOC79 size. There are 32 fields, each 4 bytes in size. Each field corresponds
85 are individual tests, they each require their own "Call-out" sections.
148 3 different calls to the package if each of the three following tests
160 basically, it enables each of these exceptions and forces
161 each using an implemented FP instruction. this process
/linux-4.1.27/Documentation/gpio/
Ddriver.txt22 On top of this internal number, each GPIO also need to have a global number in
25 assigned), and for each GPIO the global number will be (base + hardware number).
40 In the gpiolib framework each GPIO controller is packaged as a "struct
42 common to each controller of that type:
53 controller, possibly using the driver model. That code will configure each
138 irq_chip are orthogonal, and offering their services independent of each
/linux-4.1.27/Documentation/sysctl/
Dvm.txt229 the fragmentation index for each order is in each zone in the system. Values
319 pages for each zones from them. These are shown as array of protection pages
428 watermark[WMARK_MIN] value for each lowmem zone in the system.
444 A percentage of the total pages in each zone. On Zone reclaim
462 This is a percentage of the total pages in each zone. Zone reclaim will
549 "Node order" orders the zonelists by node, then by zone within each node.
552 "Zone Order" orders the zonelists by zone type, then by node within each
578 the memory state information for each one. Such systems should not
705 This is the fraction of pages at most (high mark pcp->high) in each zone that
706 are allocated for each per cpu page list. The min value for this is 8. It
[all …]
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars16 creates a separate directory for each one found. Each
31 explanation of each of these variables.
Dsyscalls10 mapped to each syscall.
/linux-4.1.27/arch/powerpc/boot/dts/
Dmedia5200.dts118 device-width = <2>; // Two devices on each bank
125 device-width = <2>; // Two devices on each bank
/linux-4.1.27/Documentation/power/regulator/
Dmachine.txt16 each regulator.
41 for each regulator power domain. This structure also maps the consumers
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dm_can.txt20 RAM and each element(e.g Rx FIFO or Tx Buffer and etc)
32 elements are used for each FIFO/Buffer.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dqcom-rpm.txt4 various Qualcomm platforms. The RPM allows each component in the system to vote
140 The regulator node houses sub-nodes for each regulator within the device. Each
141 sub-node is identified using the node's name, with valid values listed for each
159 The content of each sub-node is defined by the standard binding for regulators -
/linux-4.1.27/Documentation/mtd/nand/
Dpxa3xx-nand.txt38 (2048 data + 32 spare) each.
51 In the BCH mode the ECC code will be calculated for each transferred chunk
64 If the ECC mode is 'Hamming' the ECC is 6 bytes long, for each 512B block.
/linux-4.1.27/Documentation/security/
DIMA-templates.txt15 However, the main problem to introduce this feature is that, each time
48 The functions ima[_ascii]_measurements_show() retrieve, for each entry,
50 method for each item of the array of template fields structures.
/linux-4.1.27/Documentation/tpm/
Dxen-tpmfront.txt14 system. Each guest gets its own unique, emulated, software TPM. However, each
16 which seals the secrets to the Physical TPM. If the process of creating each of
91 persistent state of each vTPM.
/linux-4.1.27/arch/arc/
DKconfig.debug9 kernel stack attached to each process/thread. The default is 8K.
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/
Dimgpdc-wdt.txt6 - clocks: Must contain an entry for each entry in clock-names.
/linux-4.1.27/fs/dlm/
DKconfig14 Under the debugfs mount point, the name of each lockspace will
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt37 The support for each CPU depends on the facilities provided by the
38 SoC and the driver as each device has different PLL and clock chains
DUSB-Host.txt84 This is struct describes each port, 0 or 1. The platform driver
85 should set the flags field of each port to S3C_HCDFLG_USED if
/linux-4.1.27/Documentation/video4linux/cx2341x/
DREADME.vbi16 header and a 42 bytes payload each. Anything beyond this limit is cut off by
34 For each line the least significant 4 bits of the first byte contain the data type.
/linux-4.1.27/Documentation/devicetree/bindings/power/
Dopp.txt8 - operating-points: An array of 2-tuples items, and each item consists
/linux-4.1.27/Documentation/accounting/
Dtaskstats.txt62 per-tgid data. It is versioned and can be extended by each accounting subsystem
125 accumulates each exiting task's statistics into a process-wide data structure.
146 interface to return them. Since userspace processes each netlink attribute
173 each listener. In the extreme case, there could be one listener for each cpu.
/linux-4.1.27/Documentation/trace/
Dkprobetrace.txt68 Per-probe event filtering feature allows you to set different filter on each
104 assigned to each function argument depends on arch-specific ABI. If you unsure
107 As this example shows, users can choose more familiar names for each arguments.
148 Right after definition, each event is disabled by default. For tracing these
/linux-4.1.27/Documentation/devicetree/bindings/iommu/
Dnvidia,tegra30-smmu.txt5 - reg : Should contain 3 register banks(address and length) for each
/linux-4.1.27/sound/soc/rockchip/
DKconfig16 8 channels each for play and record.
/linux-4.1.27/Documentation/ioctl/
Dioctl-decoding.txt16 unique to each driver

1234567