Home
last modified time | relevance | path

Searched refs:same (Results 1 – 25 of 1485) sorted by relevance

12345678910>>...60

/Linux-v4.19/Documentation/devicetree/bindings/net/
Dsocionext-netsec.txt11 - 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 - local-mac-address: See ethernet.txt in the same directory.
30 - mac-address: See ethernet.txt in the same directory.
31 - max-speed: See ethernet.txt in the same directory.
32 - max-frame-size: See ethernet.txt in the same directory.
Daltera_tse.txt9 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.
Dsocionext,uniphier-ave4.txt15 - phy-mode: See ethernet.txt in the same directory. Allow to choose
19 See ethernet.txt file in the same directory.
35 - local-mac-address: See ethernet.txt in the same directory.
39 See phy.txt in the same directory.
Dnixge.txt8 - phy-mode: See ethernet.txt file in the same directory.
9 - phy-handle: See ethernet.txt file in the same directory.
Dbrcm,amac.txt9 contains the information of registers in the same order as
20 - mac-address: See ethernet.txt file in the same directory
/Linux-v4.19/kernel/
Dlatencytop.c107 int q, same = 1; in account_global_scheduler_latency() local
119 same = 0; in account_global_scheduler_latency()
127 if (same) { in account_global_scheduler_latency()
202 int same = 1; in __account_scheduler_latency() local
209 same = 0; in __account_scheduler_latency()
217 if (same) { in __account_scheduler_latency()
/Linux-v4.19/Documentation/devicetree/bindings/display/
Dst,stih4xx.txt18 - 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-v4.19/tools/perf/Documentation/
Dperf-buildid-cache.txt38 same directory and are also copied. All 3 files are created with read
40 kcore in the cache (with the same build-id) that has the same modules at
41 the same addresses. Use the -v option to see if a copy of kcore is
45 Remove a cached binary which has same build-id of specified file
62 exactly same build-id, that is replaced by new one. It can be used
Dintel-bts.txt39 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
/Linux-v4.19/Documentation/devicetree/bindings/sound/
Drenesas,fsi.txt17 - fsib,spdif-connection : same as fsia
18 - fsib,stream-mode-support : same as fsia
19 - fsib,use-internal-clock : same as fsia
Dst,sti-asoc-card.txt20 - 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
Daudio-graph-scu-card.txt8 Basically, Audio-Graph-SCU-Card property is same as
14 Below are same as Simple-Card / Audio-Graph-Card.
26 Below are same as Simple-SCU-Card.
Dname-prefix.txt4 audio components as list of string pair. Component using the same
12 Example: Two instances of the same component.
/Linux-v4.19/Documentation/driver-api/usb/
Dpersist.rst22 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 …]
/Linux-v4.19/Documentation/
Dcputopology.txt34 internal kernel map of cpuX's hardware threads within the same
39 human-readable list of cpuX's hardware threads within the same
44 internal kernel map of cpuX's hardware threads within the same
49 human-readable list of cpuX's hardware threads within the same
54 internal kernel map of cpuX's hardware threads within the same
59 human-readable list of cpuX's hardware threads within the same
64 internal kernel map of cpuX's hardware threads within the same
69 human-readable list of cpuX's hardware threads within the same
/Linux-v4.19/fs/
Dioctl.c582 struct file_dedupe_range *same = NULL; in ioctl_file_dedupe_range() local
598 same = memdup_user(argp, size); in ioctl_file_dedupe_range()
599 if (IS_ERR(same)) { in ioctl_file_dedupe_range()
600 ret = PTR_ERR(same); in ioctl_file_dedupe_range()
601 same = NULL; in ioctl_file_dedupe_range()
605 same->dest_count = count; in ioctl_file_dedupe_range()
606 ret = vfs_dedupe_file_range(file, same); in ioctl_file_dedupe_range()
610 ret = copy_to_user(argp, same, size); in ioctl_file_dedupe_range()
615 kfree(same); in ioctl_file_dedupe_range()
/Linux-v4.19/Documentation/devicetree/bindings/display/msm/
Ddpu.txt18 - 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.
34 - assigned-clock-rates: list of clock frequencies sorted in the same order as
45 - clock-names: device clock names, must be in same order as clocks property.
66 - assigned-clock-rates: list of clock frequencies sorted in the same order as
/Linux-v4.19/Documentation/namespaces/
Dcompatibility-list.txt30 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-v4.19/Documentation/core-api/
Drefcount-vs-atomic.rst35 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
/Linux-v4.19/Documentation/virtual/kvm/devices/
Dvcpu.txt5 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.
/Linux-v4.19/Documentation/vm/
Dzswap.rst113 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
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
/Linux-v4.19/Documentation/devicetree/bindings/media/
Dst,st-hva.txt7 - 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.
/Linux-v4.19/Documentation/power/
Dswsusp-and-swap-files.txt4 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
/Linux-v4.19/Documentation/filesystems/
Dsysfs-tagging.txt8 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
/Linux-v4.19/Documentation/devicetree/bindings/dma/
Dshdma.txt5 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

12345678910>>...60