| /linux-4.4.14/kernel/ |
| D | latencytop.c | 105 int q, same = 1; in account_global_scheduler_latency() local
117 same = 0; in account_global_scheduler_latency()
125 if (same) { in account_global_scheduler_latency()
200 int same = 1; in __account_scheduler_latency() local
207 same = 0; in __account_scheduler_latency()
215 if (same) { in __account_scheduler_latency()
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-buildid-cache.txt | 32 same directory and are also copied. All 3 files are created with read
34 kcore in the cache (with the same build-id) that has the same modules at
35 the same addresses. Use the -v option to see if a copy of kcore is
39 Remove a cached binary which has same build-id of specified file
53 exactly same build-id, that is replaced by new one. It can be used
|
| D | intel-bts.txt | 39 The snapshot option is the same as Intel PT (refer Intel PT documentation).
45 The mmap size option is the same as Intel PT (refer Intel PT documentation).
53 the same as Intel PT (refer Intel PT documentation) except that neither
76 This can be further controlled by new option --itrace exactly the same as
|
| D | perf-mem.txt | 47 Restrict dump of raw samples to those provided via this option. Note that the same
48 option can be passed in record mode. It will be interpreted the same way as perf
|
| D | itrace.txt | 11 The default is all events i.e. the same as --itrace=ibxe
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | st,stih4xx.txt | 18 - clock-names: names of the clocks listed in clocks property in the same
36 - clock-names: names of the clocks listed in clocks property in the same
40 - reset-names: names of the resets listed in resets property in the same
50 the same order.
53 - reset-names: names of the resets listed in resets property in the same
62 the same order.
65 the same order
68 - clock-names: names of the clocks listed in clocks property in the same
78 the same order.
82 - clock-names: names of the clocks listed in clocks property in the same
[all …]
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | Kconfig | 76 set this to same as CONFIG_ETRAX_LED1G (normally 2).
86 set this to same as CONFIG_ETRAX_LED1G (normally 2).
96 set this to same as CONFIG_ETRAX_LED1G (normally 2).
105 set this to same as CONFIG_ETRAX_LED1G (normally 2).
114 set this to same as CONFIG_ETRAX_LED1G (normally 2).
123 set this to same as CONFIG_ETRAX_LED1G (normally 2).
132 set this to same as CONFIG_ETRAX_LED1G (normally 2).
141 set this to same as CONFIG_ETRAX_LED1G (normally 2).
150 set this to same as CONFIG_ETRAX_LED1G (normally 2).
159 set this to same as CONFIG_ETRAX_LED1G (normally 2).
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | renesas,fsi.txt | 17 - fsib,spdif-connection : same as fsia
18 - fsib,stream-mode-support : same as fsia
19 - fsib,use-internal-clock : same as fsia
|
| D | st,sti-asoc-card.txt | 18 - clock-names: name of the clocks listed in clocks property in the same order
20 - reg: CPU DAI IP Base address and size entries, listed in same
24 the same order.
26 - interrupts: CPU_DAI interrupt line, listed in the same order than the
29 - dma: CPU_DAI DMA controller phandle and DMA request line, listed in the same
41 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| D | renesas,rsnd.txt | 18 The number of SSI subnode should be same as HW.
21 The number of SRC subnode should be same as HW.
24 The number of CTU subnode should be same as HW.
27 The number of MIX subnode should be same as HW.
30 The number of DVC subnode should be same as HW.
33 The number of DAI subnode should be same as HW.
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 19 has no way to know what has actually happened. Perhaps the same
32 system woke up, who cares? It'll still work the same when you type on
36 devices. The effect is exactly the same as if the device really had
44 interrupts a power session will have the same effect. For example,
79 same thing that happens whenever a USB device is reset.) If the
81 same descriptors as before, including the Vendor and Product IDs, then
82 the kernel continues to use the same device structure. In effect, the
86 The same thing happens if the host controller is in the expected state
120 have the same persistent volume associated with the device. As such
136 to make sure the USB device hasn't been changed; that is, the same
[all …]
|
| D | bulk-streams.txt | 35 IDs. This is to ensure that a UASP driver will be able to use the same stream
50 Drivers will only be allowed to call this API once for the same endpoint
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | snps,dwc-qos-ethernet.txt | 13 - phy-mode: See ethernet.txt file in the same directory
17 - mac-address: See ethernet.txt in the same directory
18 - local-mac-address: See ethernet.txt in the same directory
30 - phy-handle: See ethernet.txt file in the same directory
43 - fixed-mode device tree subnode: see fixed-link.txt in the same directory
|
| D | altera_tse.txt | 9 the information of registers in the same order as described by reg-names
24 - phy-mode: See ethernet.txt in the same directory.
25 - phy-handle: See ethernet.txt in the same directory.
26 - phy-addr: See ethernet.txt in the same directory. A configuration should
50 - local-mac-address: See ethernet.txt in the same directory.
51 - max-frame-size: See ethernet.txt in the same directory.
|
| D | ethernet.txt | 16 - phy-connection-type: the same as "phy-mode" property but described in ePAPR;
19 - phy: the same as "phy-handle" property, not recommended for new bindings.
20 - phy-device: the same as "phy-handle" property, not recommended for new
34 They are described in the phy.txt file in this same directory.
|
| D | marvell-armada-370-neta.txt | 7 - phy: See ethernet.txt file in the same directory.
8 - phy-mode: See ethernet.txt file in the same directory
|
| D | fsl-fec.txt | 7 - phy-mode : See ethernet.txt file in the same directory
17 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
30 according to phy.txt in the same directory
|
| D | cpsw.txt | 43 - phy-mode : See ethernet.txt file in the same directory
47 - mac-address : See ethernet.txt file in the same directory
49 - phy-handle : See ethernet.txt file in the same directory
52 - fixed-link : See fixed-link.txt file in the same directory
|
| D | stmmac.txt | 13 - phy-mode: See ethernet.txt file in the same directory.
37 - max-frame-size: See ethernet.txt file in the same directory
48 - tx-fifo-depth: See ethernet.txt file in the same directory
49 - rx-fifo-depth: See ethernet.txt file in the same directory
|
| D | marvell-pxa168.txt | 13 - phy-handle: see ethernet.txt file in the same directory.
14 - local-mac-address: see ethernet.txt file in the same directory.
|
| D | arc_emac.txt | 7 - max-speed: see ethernet.txt file in the same directory.
8 - phy: see ethernet.txt file in the same directory.
|
| D | emac_rockchip.txt | 10 - phy: see ethernet.txt file in the same directory.
11 - phy-mode: see ethernet.txt file in the same directory.
|
| D | fsl-tsec-phy.txt | 53 - phy-handle : See ethernet.txt file in the same directory.
54 - fixed-link : See fixed-link.txt in the same directory.
55 - phy-connection-type : See ethernet.txt file in the same directory.
118 The calculation for tmr_fiper2 is the same as for tmr_fiper1. The
|
| D | sh_eth.txt | 18 - phy-mode: see ethernet.txt file in the same directory.
19 - phy-handle: see ethernet.txt file in the same directory.
|
| D | allwinner,sun4i-emac.txt | 8 - phy: see ethernet.txt file in the same directory.
|
| D | cdns-emac.txt | 10 - phy-mode: see ethernet.txt file in the same directory.
|
| D | lpc-eth.txt | 9 - phy-mode: See ethernet.txt file in the same directory. If the property is
|
| D | smsc-lan91c111.txt | 9 - phy-device : see ethernet.txt file in the same directory
|
| D | marvell-orion-net.txt | 39 - local-mac-address: See ethernet.txt file in the same directory.
51 - phy-handle: See ethernet.txt file in the same directory.
|
| D | renesas,ravb.txt | 15 - phy-mode: see ethernet.txt file in the same directory.
16 - phy-handle: see ethernet.txt file in the same directory.
|
| D | cavium-mix.txt | 21 - phy-handle: Optional, see ethernet.txt file in the same directory.
|
| D | brcm,bcmgenet.txt | 10 - phy-mode: see ethernet.txt file in the same directory
21 - phy-handle: See ethernet.txt file in the same directory; used to describe
|
| /linux-4.4.14/Documentation/ |
| D | cputopology.txt | 25 internal kernel map of cpuX's hardware threads within the same
30 human-readable list of cpuX's hardware threads within the same
35 internal kernel map of cpuX's hardware threads within the same
40 human-readable list of cpuX's hardware threads within the same
45 internal kernel map of cpuX's hardware threads within the same
50 human-readable list of cpuX's hardware threads within the same
|
| D | sgi-ioc4.txt | 9 they can't all register to own the same PCI device ID. To make
29 IOC4 function probe and remove operations isn't precisely the same
31 same operation.
|
| D | bus-virt-phys-mapping.txt | 33 external hardware sees the memory the same way.
35 Now, on normal PCs the bus address is exactly the same as the physical
37 because the memory and the devices share the same address space, and that is
47 Now, that looks simple enough. However, when you look at the same thing from
61 where all the addresses actually point to the same thing. It's just seen
71 are the same).
139 conceptually in the same memory space as "real memory" at all, so you cannot
140 just dereference a pointer. (Sadly, on x86 it _is_ in the same memory space,
|
| D | devices.txt | 60 Second, please include a description of the device *in the same format
288 Partitions are handled in the same way as for IDE
597 Partitions are handled the same way as for IDE disks
608 Partitions are handled the same way as for the first
716 Partitions are handled in the same way as for IDE
804 Partitions are handled the same way as for the first
822 Partitions are handled the same way as for the first
949 Partitions are handled in the same way as for IDE
951 limit is 15 rather than 63 per disk (same as SCSI.)
973 Partitions are handled in the same way as for IDE
[all …]
|
| D | preempt-locking.txt | 10 A preemptible kernel creates new locking issues. The issues are the same as
54 RULE #3: Lock acquire and release must be performed by same task
57 A lock acquired in one task must be released by the same task. This
60 like this, acquire and release the task in the same code path and
|
| D | assoc_array.txt | 42 (4) Index keys must be unique. Inserting an object with the same key as one
67 on each level by nibbles from the index key in the same manner as in a radix
170 differs from the given index key or -1 if they are the same.
263 the array under the RCU read lock at the same time as this function is
313 This may be used on an array at the same time as the array is being
334 This may be used on an array at the same time as the array is being
350 other - and those with the same length keys to cluster together.
455 pointers - even if some of those leaves would like to be in the same slot.
556 unchanged - and will still be rooted on the same slot, so we shouldn't
|
| D | IRQ.txt | 5 Several devices may be connected to the same pin thus
|
| D | rtc.txt | 27 RTCs use the same API to make requests in both RTC frameworks (using
29 same functionality. For example, not every RTC is hooked up to an
117 * /dev/rtcN ... much the same as the older /dev/rtc interface
166 some PC/AT functionality might not be provided. And in the same way, some
181 request (using the same model as EFI firmware).
|
| D | workqueue.txt | 39 thread system-wide. A single MT wq needed to keep around the same
56 limitation that no two polling PIOs can progress at the same time. As
213 work items will not prevent other work items in the same
235 executing at the same time per CPU.
245 may queue at the same time. Unless there is a specific need for
253 achieving the same ordering property as ST wq.
261 Work items w0, w1, w2 are queued to a bound wq q0 on the same CPU.
|
| /linux-4.4.14/Documentation/namespaces/ |
| D | compatibility-list.txt | 30 words, user 10 in one user namespace shouldn't have the same
34 The same is true for the IPC namespaces being shared - two users
35 from different user namespaces should not access the same IPC objects
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos5433-decon.txt | 14 in the same order as they were listed in the interrupts
18 - clock-names: list of clock names sorted in the same order as the clocks
30 it is not needed, but make it remain to use same kind of node
|
| D | exynos7-decon.txt | 20 "lcd_sys", in the same order as they were listed in the interrupts
30 - clock-names: list of clock names sorted in the same order as the clocks
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 8 namespace active multiple devices with the same name can show up in
9 the same directory, ouch!
12 namespaces to see the same interface that is currently presented in
|
| D | isofs.txt | 1 Mount options that are the same as for msdos and vfat partitions.
7 Mount options that are the same as vfat partitions. These are only useful
21 check=strict Matches only filenames with the exact same case
|
| D | sharedsubtree.txt | 40 replicas continue to be exactly same.
72 And the same is true even when /dev/sd0 is mounted on /mnt/a. The
162 mount at /cdrom which is a replica of the same mount in the
233 to mean the same thing, throughout this document.
260 to the same peer group. Anything mounted or unmounted under
379 'C', 'C1', .., 'Cn' with exactly the same configuration as the
417 rbind is same as bind. Bind replicates the specified mount. Rbind
481 exact same configuration as that of 'B'. This new propagation tree
498 in the exact same configuration as that of 'B'. This new propagation
534 The above operation is the same as bind operation with the exception
[all …]
|
| D | overlayfs.txt | 41 directory trees to be in the same filesystem and there is no
71 The "workdir" needs to be an empty directory on the same filesystem
100 directory in the lower filesystem with the same name is ignored.
110 directory is opened and read by two processes at the same time, they
151 necessary. It then creates the object with the same metadata (owner,
195 referring to the same inode.
|
| D | locks.txt | 33 file with fcntl() at the same time as the GDBM routines tried to lock this
47 practical one. It puts us in the same position as, for example, SunOS
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | shdma.txt | 5 the same configuration. To describe this topology we require all compatible
7 DMAC instances have the same number of channels and use the same DMA
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp-and-swap-files.txt | 4 The Linux kernel handles swap files almost in the same way as it handles swap
42 by the same application that determines the swap file's header offset using the
53 Now, swsusp will use the swap file in the same way in which it would use a swap
58 the location of its header need not be the same as before. Thus every time
|
| D | power_supply_class.txt | 100 VOLTAGE_MAX, VOLTAGE_MIN - same as _DESIGN voltage values except that
111 ENERGY_FULL_DESIGN, ENERGY_EMPTY_DESIGN - same as above but for energy.
139 ENERGY_FULL, ENERGY_EMPTY - same as above but for energy.
164 Often power supplies are acting as supplies and supplicants at the same
202 attribute? The same question about time_to_empty/time_to_full.
|
| D | charger-manager.txt | 22 they may be activated at the same time. Each charger may have its
65 multiple instances of Charger Manager share the same charger_global_desc
84 same struct. If there is any other wakeup source triggered the
91 assumes that the suspend-duration is same as the alarm length.
188 is the same as irq's type (enum cm_event_types). The event message "msg" is
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README.quirks | 6 The vsfx insmod option does the same for EN_VSFX bit. If you have
43 (1) Deassert REQ at the same time as asserting FRAME.
61 responsibility to remove its request at the same time. It is the
73 during the same cycle that GNT is de-asserted. This is non PCI 2.1
78 transaction from starting the same cycle as GNT is de-asserted. This
|
| D | README.freeze | 55 doing DMA at the same time. bttv + ide seems to cause this sometimes,
57 access at the same time. Updating the IDE driver to get the latest and
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | mediatek,sysirq.txt | 18 - #interrupt-cells : Use the same format as specified by GIC in
21 use the same interrupt-cells format as GIC.
|
| D | cdns,xtensa-mx.txt | 6 Remaining properties have exact same meaning as in Xtensa PIC
|
| D | brcm,bcm2835-armctrl-ic.txt | 8 The BCM2836 contains the same interrupt controller with the same
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | m_can.txt | 10 line 0 and line 1, could be same if sharing
11 the same interrupt.
19 Multiple M_CAN instances can share the same Message
|
| /linux-4.4.14/scripts/coccinelle/tests/ |
| D | doublebitand.cocci | 1 /// Find bit operations that include the same argument more than once
5 //# same structure as other similar expressions
|
| D | doubletest.cocci | 1 /// Find &&/|| operations that include the same argument more than once
|
| /linux-4.4.14/drivers/gpu/vga/ |
| D | Kconfig | 6 Some "legacy" VGA devices implemented on PCI typically have the same
8 are accessed at same time they need some kind of coordination. Please
|
| /linux-4.4.14/net/batman-adv/ |
| D | Kconfig | 25 to both the same LAN and the same mesh. If you will never use
26 more than one mesh node in the same LAN, you can safely remove
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 79 to other cores and threads in the same physical package.
91 within the same physical_package_id.
94 numbers within the same physical_package_id as cpu#.
101 threads within the same core as cpu#
104 threads within the same core as cpu#
150 Description: Discover CPUs in the same CPU frequency coordination domain
153 the same clock/freq domain (possibly at the hardware level).
241 attributes: LEGACY used only on IA64 and is same as write_policy
249 collection of cache lines with the same cache index
|
| D | sysfs-firmware-dmi-entries | 27 Multiple entries of the same type are allowed. In order
31 to say, if there are 'N' multiple entries with the same type
69 type : The type of the entry. This value is the same
73 given type. This value is the same as found
|
| D | sysfs-profiling | 8 You can get the same effect running:
|
| D | sysfs-devices-power_resources_D0 | 12 of the links are the same as the names of the directories they
|
| D | sysfs-devices-power_resources_wakeup | 12 the links are the same as the names of the directories they
|
| D | sysfs-bus-hsi | 18 Description: Stores the same MODALIAS value emitted by uevent
|
| D | sysfs-devices-power_resources_D1 | 13 of the links are the same as the names of the directories they
|
| D | sysfs-devices-power_resources_D2 | 13 of the links are the same as the names of the directories they
|
| D | sysfs-devices-sun | 10 the same type. It is also recommended that this number match
|
| D | sysfs-devices-power_resources_D3hot | 13 names of the links are the same as the names of the directories
|
| D | sysfs-bus-rbd | 27 Usage is the same as for /sys/bus/rbd/add. If present,
38 Usage is the same as for /sys/bus/rbd/remove. If present,
|
| D | sysfs-class-regulator | 102 output voltage level as this value is the same regardless of
117 output current level as this value is the same regardless of
141 output operating mode as this value is the same regardless of
324 This will be one of the same strings reported by
337 This will be one of the same strings reported by
350 This will be one of the same strings reported by
|
| D | sysfs-bus-iio-mpu6050 | 13 aligned with each other. All axes are exactly the same.
|
| D | sysfs-block | 27 same as the above-written /sys/block/<disk>/stat
113 write atomically. It is usually the same as the logical
229 Some devices support a write same operation in which a
234 bytes can be written in a single write same command. If
235 write_same_max_bytes is 0, write same is not supported
|
| D | sysfs-bus-mei | 6 Description: Stores the same MODALIAS value emitted by uevent
|
| D | sysfs-bus-bcma | 22 BCMA cores of the same type can still slightly differ depending
|
| D | sysfs-devices-real_power_state | 19 the same device object. If that happens, some shared power
|
| D | sysfs-class-net-mesh | 24 same time (if available).
93 to send fewer wifi packets but still the same
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | sacos.S | 5 | an input argument; sAcosd does the same except for denormalized
42 | file, README, in this same directory.
|
| D | satanh.S | 6 | an input argument; satanhd does the same except for denormalized
49 | file, README, in this same directory.
|
| D | sasin.S | 5 | an input argument; sAsind does the same except for denormalized
42 | file, README, in this same directory.
|
| D | scosh.S | 5 | an input argument; sCoshd does the same except for denormalized
53 | file, README, in this same directory.
|
| D | slog2.S | 6 | slog10d does the same except the input value is a
26 | function is reinvoked at the same input argument.
100 | file, README, in this same directory.
|
| D | ssinh.S | 5 | an input argument; sSinhd does the same except for denormalized
53 | file, README, in this same directory.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | README | 10 - IA-64 kernel installation is the same as the other platforms, see
23 Configuration is the same, see original README for details.
|
| D | aliasing.txt | 24 The Itanium architecture requires that we avoid accessing the same
92 by a kernel identity mapping, the user mapping must use the same
124 Otherwise, the user mapping must use the same attribute as the
188 same attributes, we can allow the mmap (and we will prefer WB if
206 fail for the same reason as above.
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-iov-howto.txt | 39 which applies to all PFs of the same device. Additionally, the
41 valid to reduce duplication in multiple drivers for the same
49 should be able to work in the same way as real PCI devices. The VF
50 requires device driver that is same as a normal PCI device's.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.icn | 22 all cards are mapped to the same window and activated as needed.
88 maps all cards into the same address-space.
105 where p, m, idstring1 and idstring2 have the same meanings as the
113 Using the "icnctrl"-utility, the same features apply to the modularized
139 To load a 4B-card, the same command is used, except a second firmware
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-parport | 11 * video/i2c-parport (NOT the same as this one, dedicated to home brew
84 all connected lines MUST BE driven at the same state, else you'll short
130 If possible, you should use the same pinout configuration as existing
137 This driver is NOT the same as the i2c-pport driver found in the i2c
142 This driver is also NOT the same as the i2c-pcf-epp driver found in the
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | timer.txt | 18 must appear in the same order as the clock names.
21 the same order as the clocks.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | g_NCR5380.txt | 11 modes at a time but it does support both of these chips at the same time.
13 the same time. It should be able to handle multiple different cards in the
14 same machine.
|
| D | cxgb3i.txt | 67 same as the ethX's ip address or an address on the same subnet. Make
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm77 | 25 the limit and its hysteresis is always the same for all 3 limits.
36 temp1_crit_hyst and temp1_crit into the chip, and the same relative
|
| D | smsc47m192 | 49 Reading them more often repeats the same values.
83 Note that temp1 and temp2 offsets share the same register,
84 they cannot both be different from zero at the same time.
|
| D | emc1403 | 45 difference between the limit and its hysteresis is always the same for
57 temp1_crit_hyst and temp1_crit into the chip, and the same relative
|
| D | hih6130 | 21 The devices communicate with the I2C protocol. All sensors are set to the same
|
| /linux-4.4.14/Documentation/vm/ |
| D | numa | 31 attached to the same cell will experience faster access times and higher
39 [cache misses] to be to "local" memory--memory on the same cell, if any--or
57 a given node will see the same local memory access times and bandwidth.
79 fall back to the same zone type on a different node, or to a different zone
80 type on the same node. This is an important consideration because some zones,
124 closest available memory. This is a consequence of the same mechanism that
148 specified CPU. Again, this is the same node from which default, local page
|
| /linux-4.4.14/Documentation/thermal/ |
| D | exynos_thermal_emulation | 24 changing temperature. However, this node only uses same delay of real sensing time, 938us.)
28 mode at the same time. (Or you have to keep the mode enabling.) If you don't, it fails to
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | integrator.dtsi | 67 * These PrimeCells are in the same locations and using the
68 * same interrupts in all Integrators, however the silicon
|
| D | integratorcp.dts | 153 * These PrimeCells are at the same location and using
154 * the same interrupts in all Integrators, but in the CP
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-crypt.txt | 67 Perform encryption using the same cpu that IO was submitted on.
75 significantly. The default is to offload write bios to the same
77 same context.
|
| D | dm-service-time.txt | 49 1. If the paths have the same 'relative_throughput', skip
52 2. If the paths have the same 'in-flight-size', skip the division
|
| D | verity.txt | 34 specified similarly to the device path and may be the same device. If the
35 same device is used, the hash_start should be outside the configured
47 inaccessible. You can place hashes to the same partition as data, in this
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 33 be different or the same. Usually for
36 If they are the same, the additional
|
| /linux-4.4.14/drivers/staging/panel/ |
| D | Kconfig | 115 however, use the same line width internally as what is visible. The KS0074
175 -1..-17 : connected to the same pin through an inverter (eg: transistor).
190 -1..-17 : connected to the same pin through an inverter (eg: transistor).
205 -1..-17 : connected to the same pin through an inverter (eg: transistor).
220 -1..-17 : connected to the same pin through an inverter (eg: transistor).
235 -1..-17 : connected to the same pin through an inverter (eg: transistor).
250 -1..-17 : connected to the same pin through an inverter (eg: transistor).
|
| /linux-4.4.14/fs/cramfs/ |
| D | README | 28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
29 lines); put another way, the same order as `find -type d -exec
48 same as the start of the (i+1)'th <block> if there is one). The first
53 tree, i.e. the same order as `find -size +0 \( -type f -o -type l \)
107 kernels, not even necessarily kernels of the same architecture if
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | S3C2412.txt | 83 The watchdog hardware is the same as the S3C2410, and is supported by
95 The IIC hardware is the same as the S3C2410, and is supported by the
|
| D | GPIO.txt | 55 as they have the same arguments, and can either take the pin specific
80 The s3c2410_gpio and gpio_ calls have always operated on the same gpio
131 The return value will be from the same set of values which can be
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-mcp23s08.txt | 24 multiple chips on the same chipselect. Have a look at
30 chips - as the name suggests. Multiple SPI chips can share the same
35 possible to mix mcp23s08 and mcp23s17 on the same chipselect. Set at
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | core_locking.txt | 54 if multiple function calls using the same object are run
69 same callchain as an ib_device method call. For example, it is not
76 completion event handlers for the same CQ are not called
|
| /linux-4.4.14/arch/x86/realmode/rm/ |
| D | trampoline_32.S | 36 mov %cs, %ax # Code and data in the same place
|
| D | trampoline_64.S | 45 mov %cs, %ax # Code and data in the same place
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/panel/ |
| D | edt,et070080dh6.txt | 6 This panel is the same as ETM0700G0DH6 except for the touchscreen.
|
| D | edt,etm0700g0dh6.txt | 6 This panel is the same as ET070080DH6 except for the touchscreen.
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | Introduction | 71 for the same or a similar feature (dma1= versus dma16=). As a last
88 multiple sounds at the same time via a single card, eliminating
247 multiple PCI sound cards of the same type.
258 If you have two cards of the same type that are jumpered
259 cards or different PnP revisions, you may load the same
276 same type to load at the same time. I have tried this several times
298 A) If you have Win95 or NT on the same computer,
300 those were using for the same hardware. You probably
319 2) If you get motor-boating (the same sound or part of a
|
| D | ultrasound | 22 DSP to use DMA for playback and downloading samples. This is the same
|
| /linux-4.4.14/Documentation/RCU/ |
| D | checklist.txt | 6 result in the same sorts of problems that leaving out a locking primitive
175 any sort of irq context. The same rule applies for
180 The expedited forms of these primitives have the same semantics
211 srcu_read_unlock(), and with the same srcu_struct. The rules for
212 the expedited primitives are the same as for their non-expedited
281 The same cautions apply to call_rcu_bh(), call_rcu_sched(),
330 This same limitation also applies to synchronize_rcu_bh()
351 RCU callbacks are -usually- executed on the same CPU that executed
377 calls that have been passed the same srcu_struct. This property
386 srcu_read_unlock() calls must be passed the same srcu_struct.
[all …]
|
| D | UP.txt | 18 this same list in softirq context. Suppose that the process-context scan
28 This same problem can occur if call_rcu() is invoked from a hardware
56 callback function must acquire this same lock. In this case, if
65 the same critical section, then the code would need to create
|
| /linux-4.4.14/Documentation/networking/ |
| D | scaling.txt | 123 the receive descriptor for the packet; this would usually be the same
155 the rps_cpus to the CPUs in the same memory domain of the interrupting
164 share the same memory domain as the interrupting CPU for that queue.
169 reordering. The trade-off to sending all packets from the same flow
170 to the same CPU is CPU load imbalance if flows vary in packet rate.
195 in sysctl net.core.flow_limit_cpu_bitmap. It exposes the same CPU
202 the same that selects a CPU in RPS, but as the number of buckets can
233 consuming the packet is running. RFS relies on the same RPS mechanisms
244 same CPU. Indeed, with many flows and few CPUs, it is very likely that
260 and userspace processing occur on the same CPU, and hence the CPU index
[all …]
|
| D | z8530drv.txt | 103 IRQs or the same. If they share an interrupt, it needs to be
222 Its parameters are exactly the same as the ones you use with
232 does the same for the BAYCOM USCC card. In my opinion it is much easier
415 same way in the SCC driver. You can change parameters by using
537 has same result as the fullduplex mode 1. This parameter
559 one frequency on the same band, e.g. using several receivers and
561 Also, you can connect several radios that are active on the same
576 Interfaces are in the same group, when the logical AND
581 keyed at the same time.
583 when both channels are clear at the same time. When group 301,
[all …]
|
| D | x25-iface.txt | 54 LAPB link has been established. The same message is used for both a LAPB
59 LAPB link has been terminated. This same message is used for both a LAPB
92 always executed on the same CPU. Thus,
|
| D | ipvs-sysctl.txt | 32 connection will be delivered to the same real server that was
119 The value definition is the same as that of the drop_entry. In
185 The value definition is the same as that of drop_entry and
212 always be the same as the original route so it is an optimisation
|
| D | switchdev.txt | 118 for SWITCHDEV_ATTR_ID_PORT_PARENT_ID for each port netdev, returning the same
120 on the same system. The ID does not need to be unique between switches on
124 ports belong to the same switch.
283 bridge should not reflood the packet to the same ports the device flooded,
287 forwarded using skb->offload_fwd_mark. The same mark is set on the device
291 understanding that the device already forwarded the packet on same egress port.
340 referenced in the route's nexthop list don't all have the same switch ID, the
|
| D | ip_dynaddr.txt | 16 going up. So, the *same* (local AND masqueraded) connections requests that
|
| /linux-4.4.14/fs/efivarfs/ |
| D | Kconfig | 8 same 1024-byte variable size limit.
|
| /linux-4.4.14/Documentation/arm64/ |
| D | memory.txt | 14 virtual address, are used but the memory layout is the same.
17 the same bits set to 1. TTBRx selection is given by bit 63 of the
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 10 By default the "clocks" property lists the parents in the same order
33 supplied. If the shift value is missing it is the same as supplying
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | mflash.txt | 11 MCP(Multi Chip Package) device. These two device operate exactly same way.
30 must be same.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 3 interrupt lines from the subsystems are not needed at the same
17 register is assumed to be of same size. Valid sizes are 1, 2, 4.
|
| /linux-4.4.14/fs/configfs/ |
| D | Kconfig | 11 same system. One is not a replacement for the other.
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | i18n.c | 487 int same = 0; in compare_specifiers() local
494 same = 1; in compare_specifiers()
498 return same; in compare_specifiers()
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | arm-vgic.txt | 52 GICv2 specs. Getting or setting such a register has the same effect as
55 fields are not banked, but return the same value regardless of the
75 same effect as reading or writing the register on the actual hardware.
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | btt.txt | 34 Each arena follows the same layout for its metadata, and all references in an
165 writer started writing to the same external LBA, and finished the write updating
168 into the list of free blocks. If another write comes in for the same LBA, it can
182 Consider a case where two writer threads are writing to the same LBA. There can
188 Both threads can update their respective free[lane] with the same old, freed
190 at the same time, duplicating another free entry for two lanes.
280 btt_fini using the same struct btt* handle that was provided to it by btt_init.
|
| /linux-4.4.14/drivers/lguest/ |
| D | Kconfig | 7 multiple instances of the same Linux kernel, using the
|
| /linux-4.4.14/Documentation/devicetree/bindings/ufs/ |
| D | ufshcd-pltfrm.txt | 34 - clock-names : List of clock input name strings sorted in the same
36 - freq-table-hz : Array of <min max> operating frequencies stored in the same
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | s2mpa01.txt | 34 NOTE: Some BUCKs share the ramp rate setting i.e. same ramp value will be set
35 for a particular group of BUCKs. So provide same regulator-ramp-delay=<value>.
|
| D | s2mps11.txt | 50 The s2msp15 uses the same compatible as s2mps13, as both provides similar clocks.
67 NOTE: Some BUCKs share the ramp rate setting i.e. same ramp value will be set
68 for a particular group of BUCKs. So provide same regulator-ramp-delay<value>.
|
| D | max77686.txt | 5 are addressed using same i2c slave address whereas RTC submodule uses
|
| /linux-4.4.14/arch/arm/kvm/ |
| D | init.S | 77 @ Set the HTCR and VTCR to the same shareability and cacheability
95 @ Use the same memory attributes for hyp. accesses as the kernel
|
| /linux-4.4.14/Documentation/fmc/ |
| D | API.txt | 32 registered at the same time because if the FPGA is reprogrammed, all
38 should register as a group only mezzanines that are driven by the same
|
| /linux-4.4.14/Documentation/devicetree/bindings/watchdog/ |
| D | fsl-imx-wdt.txt | 10 in big endian mode, otherwise in native mode(same with CPU), for more
|
| /linux-4.4.14/drivers/media/rc/keymaps/ |
| D | Kconfig | 13 provide the tool and the same RC maps for load from
|
| /linux-4.4.14/drivers/staging/fwserial/ |
| D | TODO | 12 1. This driver uses the same unregistered vendor id that the firewire core does
|
| /linux-4.4.14/Documentation/devicetree/bindings/timer/ |
| D | samsung,exynos4210-mct.txt | 36 interrupt might be specified, meaning that all local timers use the same
75 timer interrupts can be specified, with the same interrupt specifier
|
| D | arm,sp804.txt | 13 apb_pclk. A single clock can also be specified if the same clock is
|
| /linux-4.4.14/Documentation/arm/ |
| D | mem_alignment | 19 floating point emulation that works about the same way). Fix your code
53 You can also read the content of the same file to get statistical
|
| /linux-4.4.14/arch/mips/cavium-octeon/ |
| D | Kconfig | 29 bool "Build the kernel to be used as a 2nd kernel on the same chip"
34 with this option to be run at the same time as one built without this
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 3 LED and flash LED devices provide the same basic functionality as current
19 a device, i.e. no other LED class device can be assigned the same
|
| /linux-4.4.14/fs/hfsplus/ |
| D | unicode.c | 154 goto same; in hfsplus_uni2asc()
177 goto same; in hfsplus_uni2asc()
223 same: in hfsplus_uni2asc()
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | serial-u16550.txt | 35 module parameter is automatically set to 1. The driver sends the same data to
47 the same data to all four MIDI Out connectors at full MIDI speed.
72 but does not allow sending the same byte simultaneously to multiple MIDI Outs.
|
| D | Audiophile-Usb.txt | 39 * Two interfaces can't use different sample depths at the same time.
44 activated at the same time depending on the audio mode selected:
152 the same behaviour as when the parameter is omitted (see paragraph "Default
163 - Ai,Ao,Do can be used at the same time
169 - Ai,Ao,Di,Do can be used at the same time
191 - Ai,Ao,Do can be used at the same time
197 - 3 ports from {Ai,Ao,Di,Do} can be used at the same time
206 - Only 1 port from {Ai,Ao,Di,Do} can be used at the same time
310 only be able to use one at the same time
|
| D | Channel-Mapping-API.txt | 26 positions even with the same number of total channels. However, there
44 device = the same device number for the assigned PCM substream
45 index = the same index number for the assigned PCM substream
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | nxp,pca9685-pwm.txt | 8 The index 16 is the ALLCALL channel, that sets all PWM channels at the same
|
| /linux-4.4.14/Documentation/auxdisplay/ |
| D | ks0108 | 53 your LCD specific wiring information in the same folder.
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | network_protocol.txt | 65 @size - the same.
97 @size - the same.
106 @size - the same.
163 @size - the same plus size of the netfs_inode_info structure.
|
| /linux-4.4.14/Documentation/connector/ |
| D | connector.txt | 92 created for user with the same ID as in msg.
115 received message MUST be the same as in the original message, and the
116 acknowledge number MUST be the same + 1.
120 its sequence number is the same as one we are expecting, but its
|
| /linux-4.4.14/Documentation/trace/ |
| D | ring-buffer-design.txt | 21 producer - the task that writes into the ring buffer (same as writer)
23 writer - same as producer
25 consumer - the task that reads from the buffer (same as reader)
27 reader - same as consumer.
63 No two writers can write at the same time (on the same per-cpu buffer),
81 same time, nor can a reader preempt/interrupt another reader. A reader
83 buffer at the same time as a writer is writing, but the reader must be
88 But a reader can read the buffer at the same time (on another processor)
97 to the same page.
463 Note, the flags UPDATE and HEADER are never set at the same time.
|
| D | tracepoints.txt | 84 - TP_ARGS(firstarg, p) are the parameters names, same as found in the
101 same tracepoint, but a single definition must be made of a given
111 kernel: they are considered as being the same whether they are in the
|
| /linux-4.4.14/drivers/idle/ |
| D | Kconfig | 9 can be configured at the same time, in order to handle
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | ev6-copy_user.S | 127 EXI ( ldbu $2,0($7) ) # .. .. .. L : No loads in the same quad
214 EXI ( ldbu $2,0($7) ) # .. .. .. L : No loads in the same quad
|
| /linux-4.4.14/arch/arm/boot/compressed/ |
| D | head-xscale.S | 20 @ memory to be sure we hit the same cache.
|
| /linux-4.4.14/fs/hpfs/ |
| D | Kconfig | 5 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | st,stih4xx.txt | 12 - clock-names: names of the clocks listed in clocks property in the same order.
|
| /linux-4.4.14/Documentation/spi/ |
| D | spidev | 137 transfer.) The model is the same as that used in the kernel spi_sync()
138 request; the individual transfers offer the same capabilities as are
149 same transfer. It's even OK if those are the same buffer.
|
| /linux-4.4.14/Documentation/locking/ |
| D | spinlocks.txt | 50 readers to be in the same critical region at once, but if somebody wants
57 The routines look the same as above:
108 guarantee the same kind of exclusive access, and it will be much faster.
122 interrupt happens on the same CPU that already holds the lock, because the
|
| D | locktorture.txt | 33 ownership (readers). The default is the same amount of writer
95 same period of time. Defaults to "stutter=5", so as
129 Of course, the same applies for (C), above. A dummy example of this is
|
| /linux-4.4.14/Documentation/input/ |
| D | iforce-protocol.txt | 59 00 Channel (when playing several effects at the same time, each must be assigned a channel)
154 responses are of the same form:
160 The device should reply with the same packet plus two additional bytes
167 at the same time (one byte)
|
| D | walkera0701.txt | 94 directly controlled from TX). Binary representations are the same as in first
105 Summary of octal values in nibbles must be same as octal value in checksum
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpu/ |
| D | samsung-g2d.txt | 14 - clock-names : names of clocks listed in clocks property, in the same
|
| /linux-4.4.14/Documentation/networking/mac80211_hwsim/ |
| D | README | 23 and always reproduce the same setup for future tests. In addition,
35 currently enabled and on the same channel as the transmitting
|
| /linux-4.4.14/Documentation/timers/ |
| D | timekeeping.txt | 91 Clock events are orthogonal to clock sources. The same hardware
99 You will notice that the clock event device code is based on the same basic
101 arithmetic, and you find the same family of helper functions again for
125 for speed in sched_clock(). It however requires some of the same basic
149 same counter that is also used as clock source is used for this purpose.
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | network.txt | 26 fsl,pq1-fec-mdio (reg is same as first resource of FEC device)
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-nice-design.txt | 95 the new scheduler makes nice(1) have the same CPU utilization effect on
97 scheduler, running a nice +10 and a nice 11 task has the same CPU
102 result' will always be the same.
|
| /linux-4.4.14/drivers/accessibility/ |
| D | Kconfig | 29 to the kernel. Options are the same as for serial console.
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | fixed-regulator.txt | 19 to be the same.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | mmc-pwrseq-simple.txt | 5 same provider for several SOC designs.
|
| /linux-4.4.14/Documentation/cpuidle/ |
| D | governor.txt | 20 More than one governor can be registered at the same time and
|
| D | driver.txt | 18 If all the idle states are the same, the wrapper function cpuidle_register
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 23 ntlmv2. Fix 2nd mount to same server but with different port to
35 hard link detection to use same inode for both. Do not set
49 session setup to distinguish multiple mounts to same server from different
57 Improve support for multiple security contexts to the same server. We
58 used to use the same "vcnumber" for all connections which could cause
62 same server with different userids without risking invalidating earlier
199 Fix hang (in i_size_read) when simultaneous size update of same remote file
273 Fix slow oplock break when mounted to different servers at the same time and
386 different users from the same client to the same server. Fix oops in
395 processes accessing the same server at the same time).
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 15 meaning that the CPU and the Device are in the same endianness mode,
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | marvell,berlin.txt | 9 (BG2, BG2CD, BG2Q) SoCs share the same IP for PLLs and clocks, with some
|
| /linux-4.4.14/Documentation/m68k/ |
| D | README.buddha | 24 same card, no space preference, supports "Shutup_forever".
110 polls two words out of the same address of IDE port since
135 the same time. IOR and IOW have a propagation delay of
143 (same timing as the Amiga 1200 does on it's IDE port without
|
| /linux-4.4.14/Documentation/blackfin/ |
| D | bfin-spi-notes.txt | 15 You can even use the same pin whose peripheral role is a SSEL,
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 9 from the same input device.
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 9 all per-CPU defaults at the same time.
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pca954x.txt | 21 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | trigger.txt | 5 such triggers are registered with the core in the same way as
|
| /linux-4.4.14/arch/arm/mach-s3c64xx/ |
| D | Kconfig | 167 # for the MMC/SD slots connected to the same input. This means that
182 channels 0 and 1 are the same.
191 channels 0 and 1 are the same.
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide.txt | 46 - If you mix devices on the same cable, please consider using similar devices
49 - Even better try to stick to the same vendor and device type on the same
77 or may not be harmful to your hardware.. two or more cards driving the same IRQ
244 similar to SCSI protocols, created at the same time as the ATA2 standard.
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 45 stays the same, though.
123 get the same sysfs value by default.
162 are made at the same interval regardless of current clock speed. But
200 The governor is tweaked in the same manner as the "ondemand" governor
210 down_threshold: same as the 'up_threshold' found for the "ondemand"
|
| /linux-4.4.14/Documentation/sh/ |
| D | new-machine.txt | 53 ... and so on. Headers for the companion chips are treated the same way as
90 share the same board-specific code with minor differences.
102 seamlessly with the build system, it's best to have this directory the same
136 * Presume all FooTech boards have the same broken timer,
231 be named the same. If this is not the case (as is the case with multiple
|
| /linux-4.4.14/Documentation/block/ |
| D | cfq-iosched.txt | 79 multiple queues in the group at the same time and achieve higher throughput
112 This parameter is same as of slice_sync but for asynchronous queue. The
214 single queue and also allow dispatch from multiple cfq queue at the same time.
226 on same queue after completion of a request. In this process CFQ will not
285 provides isolation from multiple sequential readers and at the same
290 more writes to be dispatched from same context soon, should be able
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | 83xx-512x-pci.txt | 3 Freescale 83xx and 512x SOCs include the same pci bridge core.
|
| /linux-4.4.14/scripts/coccinelle/free/ |
| D | clk_put.cocci | 4 //# in the same function.
|
| /linux-4.4.14/arch/h8300/lib/ |
| D | modsi3.S | 54 ;; Basically the same, except that the sign of the divisor determines
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | mpc52xx.txt | 35 nothing to do with the MPC5200. I also included the 'MPC' for the same
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | dynamic-resolution-notes.txt | 20 by the same amount.
|