Searched full:same (Results 1 – 25 of 1277) sorted by relevance
12345678910>>...52
| /Documentation/driver-api/usb/ |
| D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same
35 system woke up, who cares? It'll still work the same when you type on
39 devices. The effect is exactly the same as if the device really had
47 interrupts a power session will have the same effect. For example,
83 same thing that happens whenever a USB device is reset.) If the
85 same descriptors as before, including the Vendor and Product IDs, then
86 the kernel continues to use the same device structure. In effect, the
90 The same thing happens if the host controller is in the expected state
125 have the same persistent volume associated with the device. As such
142 to make sure the USB device hasn't been changed; that is, the same
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | socionext-netsec.txt | 11 - phy-mode: See ethernet.txt file in the same directory
12 - phy-handle: See ethernet.txt in the same directory.
26 Optional properties: (See ethernet.txt file in the same directory)
29 - max-speed: See ethernet.txt in the same directory.
30 - max-frame-size: See ethernet.txt in the same directory.
|
| D | fsl-fec.txt | 7 - phy-mode : See ethernet.txt file in the same directory
12 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
26 the same order. The defaults if not specified are
40 according to phy.txt in the same directory
43 To avoid these, create a phy node according to phy.txt in the same
|
| D | qca,ar71xx.txt | 16 - phy-mode : See ethernet.txt file in the same directory
26 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
31 according to phy.txt in the same directory
|
| D | nixge.txt | 8 information of registers in the same order as described by reg-names.
14 - phy-mode: See ethernet.txt file in the same directory.
20 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
22 - phy-handle: See ethernet.txt file in the same directory.
|
| /Documentation/admin-guide/ |
| D | cputopology.rst | 41 internal kernel map of CPUs within the same core.
46 human-readable list of CPUs within the same core.
51 internal kernel map of the CPUs sharing the same physical_package_id.
56 human-readable list of CPUs sharing the same physical_package_id.
61 internal kernel map of CPUs within the same die.
65 human-readable list of CPUs within the same die.
69 internal kernel map of cpuX's hardware threads within the same
74 human-readable list of cpuX's hardware threads within the same
79 internal kernel map of cpuX's hardware threads within the same
84 human-readable list of cpuX's hardware threads within the same
|
| /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 …]
|
| /Documentation/vm/ |
| D | zswap.rst | 113 Some of the pages in zswap are same-value filled pages (i.e. contents of the
114 page have same value or repetitive pattern). These pages include zero-filled
116 checked if it is a same-value filled page before compressing it. If true, the
117 compressed length of the page is set to zero and the pattern or same-filled
120 Same-value filled pages identification feature is enabled by default and can be
128 When zswap same-filled page identification is disabled at runtime, it will stop
129 checking for the same-value filled pages during store operation. However, the
130 existing pages which are marked as same-value filled pages remain stored
134 of pages stored, same-value filled pages and various counters for the reasons
|
| D | numa.rst | 35 attached to the same cell will experience faster access times and higher
43 [cache misses] to be to "local" memory--memory on the same cell, if any--or
61 a given node will see the same local memory access times and bandwidth.
83 fall back to the same zone type on a different node, or to a different zone
84 type on the same node. This is an important consideration because some zones,
87 from the same node before using remote nodes which are ordered by NUMA distance.
125 closest available memory. This is a consequence of the same mechanism that
149 specified CPU. Again, this is the same node from which default, local page
|
| /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 | name-prefix.txt | 4 audio components as list of string pair. Component using the same
12 Example: Two instances of the same component.
|
| D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
22 - reg: CPU DAI IP Base address and size entries, listed in same
26 the same order.
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
31 - dma: CPU_DAI DMA controller phandle and DMA request line, listed in the same
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| /Documentation/virt/kvm/devices/ |
| D | vcpu.txt | 5 KVM_GET_DEVICE_ATTR, and KVM_HAS_DEVICE_ATTR. The interface uses the same struct
25 type must be same for each vcpu. As a PPI, the interrupt number is the same for
57 Setting the same PPI for different timers will prevent the VCPUs from running.
|
| /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
|
| /Documentation/powerpc/ |
| D | vcpudispatch_stats.txt | 26 2. number of times this vcpu was dispatched on the same processor as last
29 as last time, but within the same chip
61 statistics were enabled. 4126 of those dispatches were on the same
63 the same chip, while 30 dispatches were on a different chip compared to
|
| /Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 35 program order (po) relation (on the same CPU). It guarantees that
42 stores (all po-earlier instructions) on the same CPU are completed
43 before any po-later instruction is executed on the same CPU.
44 It also guarantees that all po-earlier stores on the same CPU
50 stores (all po-earlier instructions) on the same CPU are completed
52 stores on the same CPU and all propagated stores from other CPUs
58 stores (all po-later instructions) on the same CPU are
60 po-later stores on the same CPU must propagate to all other CPUs
|
| /Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 35 words, user 10 in one user namespace shouldn't have the same
39 The same is true for the IPC namespaces being shared - two users
40 from different user namespaces should not access the same IPC objects
|
| /Documentation/x86/ |
| D | tsx_async_abort.rst | 17 the same uarch data structures as in MDS, with same scope of exposure i.e.
18 same-thread and cross-thread. This issue affects all current processors that
69 …0 0 0 HW default Yes Same as MDS Same as MDS
84 … 0 0 0 HW default Yes Same as MDS Same as MDS
87 … 0 1 1 Enabled Yes None Same as MDS
99 …0 0 0 HW default Yes Same as MDS Same as MDS
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 7 The Linux kernel handles swap files almost in the same way as it handles swap
45 by the same application that determines the swap file's header offset using the
56 Now, swsusp will use the swap file in the same way in which it would use a swap
61 the location of its header need not be the same as before. Thus every time
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | dpu.txt | 18 - clock-names: device clock names, must be in same order as clocks property.
30 - ranges: parent bus address space is the same as the child bus address space.
39 - assigned-clock-rates: list of clock frequencies sorted in the same order as
50 - clock-names: device clock names, must be in same order as clocks property.
71 - assigned-clock-rates: list of clock frequencies sorted in the same order as
|
| /Documentation/networking/ |
| D | devlink-params.txt | 28 enabled and creates same number of partitions when
34 a device can create. Value is same across all
40 for the device initialization. Value is same across all
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 11 since you would *usually* use the same key for the same project, you can
|
| /Documentation/devicetree/bindings/media/ |
| D | st,st-hva.txt | 7 - reg-names: names of the registers listed in registers property in the same
13 - clock-names: names of the clocks listed in clocks property in the same order.
|
| /Documentation/ABI/testing/ |
| 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
|
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 19 world value is the same as specified for the Normal world by the
42 same value as "status"; if "status" is not specified either then
65 its console output. The syntax is the same as for /chosen/stdout-path.
69 /chosen/stdout-path instead (that is, use the same device as the
|
12345678910>>...52