Searched full:case (Results 1 – 25 of 1071) sorted by relevance
12345678910>>...43
| /Documentation/userspace-api/media/v4l/ |
| D | capture.c.rst | 90 case IO_METHOD_READ:
93 case EAGAIN:
96 case EIO:
109 case IO_METHOD_MMAP:
117 case EAGAIN:
120 case EIO:
138 case IO_METHOD_USERPTR:
146 case EAGAIN:
149 case EIO:
220 case IO_METHOD_READ:
[all …]
|
| D | pixfmt-nv12mt.rst | 43 the Z shape cannot be cut in half horizontally. In case the vertical
47 In case of chroma the layout is identical. Cb and Cr samples are
60 extreme case.
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 17 and it's also much more restricted in the latter case:
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
31 the no-MMU case doesn't support these, behaviour is identical to
36 In the MMU case: VM regions backed by pages read from file; changes to
39 In the no-MMU case:
61 In the MMU case: like the non-PROT_WRITE case, except that the pages in
66 In the no-MMU case: works much like the non-PROT_WRITE case, except
71 In the MMU case: VM regions backed by pages read from file; changes to
[all …]
|
| /Documentation/usb/ |
| D | mtouchusb.rst | 32 USB Capacitive - Pearl Case 14-205 (Discontinued)
33 USB Capacitive - Black Case 14-124 (Discontinued)
34 USB Capacitive - No Case 14-206 (Discontinued)
36 USB Capacitive - Pearl Case EXII-5010UC
37 USB Capacitive - Black Case EXII-5030UC
38 USB Capacitive - No Case EXII-5050UC
|
| D | usbdevfs-drop-permissions.c | 92 case 0: in main()
94 case 1: in main()
97 case 2: in main()
100 case 3: in main()
|
| /Documentation/x86/ |
| D | tsx_async_abort.rst | 13 case certain loads may speculatively pass invalid data to dependent operations
70 …0 0 1 Invalid case Invalid case Invalid case Invalid ca…
85 …0 0 1 Invalid case Invalid case Invalid case Invalid case
100 …0 0 1 Invalid case Invalid case Invalid case Invalid ca…
|
| /Documentation/devicetree/bindings/net/ |
| D | mediatek-dwmac.txt | 42 1. tx clock will be inversed in MII/RGMII case,
44 which is from external PHYs in RMII case, and it rarely happen.
45 3. the reference clock, which outputs to TXC pin will be inversed in RMII case
48 1. rx clock will be inversed in MII/RGMII case.
49 2. reference clock will be inversed when arrived at MAC in RMII case, when
51 3. the inside clock, which be sent to MAC, will be inversed in RMII case when
|
| /Documentation/admin-guide/ |
| D | java.rst | 56 following (this is because Java is broken in case of the filename
255 case CP_UTF8:
259 case CP_CLASS:
260 case CP_STRING:
261 case CP_METHODTYPE:
264 case CP_METHODHANDLE:
267 case CP_INTEGER:
268 case CP_FLOAT:
269 case CP_FIELDREF:
270 case CP_METHODREF:
[all …]
|
| /Documentation/block/ |
| D | ioprio.rst | 124 case 'n':
128 case 'c':
132 case 'p':
139 case IOPRIO_CLASS_NONE:
142 case IOPRIO_CLASS_RT:
143 case IOPRIO_CLASS_BE:
145 case IOPRIO_CLASS_IDLE:
|
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 7 Might return "<denied>" in case of special security settings
16 Might return "<denied>" in case of special security settings
25 Might return "<denied>" in case of special security settings
56 Might return "<denied>" in case of special security settings
73 Might return "0" in case of special security settings
105 Might return "<denied>" in case of special security settings
|
| /Documentation/core-api/ |
| D | pin_user_pages.rst | 48 FOLL_LONGTERM is a specific case, more restrictive case of FOLL_PIN.
126 CASE 1: Direct IO (DIO)
138 CASE 2: RDMA
151 CASE 3: MMU notifier registration, with or without page faulting hardware
168 CASE 4: Pinning for struct page manipulation only
174 CASE 5: Pinning in order to write to the data within the page
176 Even though neither DMA nor Direct IO is involved, just a simple case of "pin,
177 write to a page's data, unpin" can cause a problem. Case 5 may be considered a
178 superset of Case 1, plus Case 2, plus anything that invokes that pattern. In
179 other words, if the code is neither Case 1 nor Case 2, it may still require
[all …]
|
| D | refcount-vs-atomic.rst | 76 case 1) - non-"Read/Modify/Write" (RMW) ops
89 case 2) - increment-based ops that return no value
101 case 3) - decrement-based RMW ops that return no value
113 case 4) - increment-based RMW ops that return a value
129 case 5) - generic dec/sub decrement-based RMW ops that return a value
142 case 6) other decrement-based RMW ops that return a value
157 case 7) - lock-based RMW
|
| /Documentation/networking/ |
| D | 6lowpan.rst | 37 case ARPHRD_6LOWPAN:
41 case LOWPAN_LLTYPE_FOOBAR:
51 In case of generic 6lowpan branch ("net/6lowpan") you can remove the check
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mtd | 43 <major>:<minor> format). In this case <minor> will be odd.
117 In the case of NOR flash it is 1 (even though individual
120 In the case of NAND flash it is one NAND page (or a
123 In the case of ECC NOR, it is the ECC block size.
134 In the case of devices lacking any ECC capability, it is 0.
185 It will always be a non-negative integer. In the case of
196 It will always be a non-negative integer. In the case of
207 It will always be a non-negative integer. In the case of
|
| /Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 120 be used to specify the offset into the underlying file. In such a case,
168 modified to reflect the reservations. In the case of a shared mapping, a
193 specified address. The avoid_reserve argument is most often used in the case
206 However, in every case the avoid_reserve argument overrides the use of
278 accounting may need to be performed. This would be the case if the page was
292 Therefore, the global resv_huge_pages counter is incremented in this case.
338 biggest reservation concern for COW is private mappings. In this case,
355 In the case where the faulting task is not the owner, the fault will fail and
408 return value of region_chg(). However, in the case of shared mappings it is
410 region_chg() and region_add(). In this case, the return value of region_add()
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | renesas,rcar-usb2-clock-sel.txt | 12 Case 1: An external clock connects to R-Car SoC
17 In this case, we need this driver with "usb_extal" clock.
19 Case 2: An oscillator connects to R-Car SoC
24 In this case, we don't need this selector.
|
| /Documentation/core-api/irq/ |
| D | concepts.rst | 17 all of the interrupt controller in the system. In the case of ISA
22 are encouraged to in the case where there is any manual configuration
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 3 This node is intended to allow SoC reset in case of software reset
37 Setup keystone reset so that in case software reset or
58 Setup keystone reset so that in case of software reset or
|
| /Documentation/driver-api/phy/ |
| D | phy.rst | 32 For the simple case where the PHY provider implements only a single instance of
36 dt boot case.
49 arguments. For the dt boot case, all PHY providers should use one of the above
54 nodes within extra levels for context and extensibility, in which case the low
114 be used to get the PHY. In the case of dt boot, the string arguments
115 should contain the phy name as given in the dt data and in the case of
124 this case, devm_of_phy_get_by_index can be used to get a phy reference based on
|
| /Documentation/dev-tools/kunit/ |
| D | usage.rst | 53 The fundamental unit in KUnit is the test case. A test case is a function with
71 a special expectation that logs a message and causes the test case to fail.
78 one or more of the expectations fail, the test case fails and information about
92 the second parameter, in this case, is what the value is expected to be; the
94 expectations, the test case, ``add_test_basic`` will pass; if any one of these
95 expectations fails, the test case will fail.
97 It is important to understand that a test case *fails* when any expectation is
99 expectations until the test case ends or is otherwise terminated. This is as
105 A single test case should be pretty short, pretty easy to understand,
143 expectation except the assertion immediately terminates the test case if it is
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | knfsd-stats.rst | 44 Note that in the default case there will be a single thread pool
75 case configuring more nfsd threads will probably improve the
110 this case), or the transport can be enqueued for later attention
111 (sockets-enqueued counts this case), or the packet can be temporarily
113 thread. This last case is not very interesting and is not explicitly
|
| /Documentation/cdrom/ |
| D | ide-cd.rst | 203 before they'll function properly. (If this is the case, there
323 directly execute binaries off the CDROM in that case.)
453 case CDS_DISC_OK:
456 case CDS_TRAY_OPEN:
459 case CDS_DRIVE_NOT_READY:
473 case CDS_DISC_OK:
476 case CDS_NO_DISC:
479 case CDS_TRAY_OPEN:
482 case CDS_DRIVE_NOT_READY:
485 case CDS_NO_INFO:
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | coding-style.rst | 47 在 switch 语句中消除多级缩进的首选的方式是让 ``switch`` 和从属于它的 ``case``
48 标签对齐于同一列，而不要 ``两次缩进`` ``case`` 标签。比如：
53 case 'G':
54 case 'g':
57 case 'M':
58 case 'm':
61 case 'K':
62 case 'k':
116 case KOBJ_ADD:
118 case KOBJ_REMOVE:
[all …]
|
| /Documentation/mips/ |
| D | booting.rst | 11 Similar to the arch/arm case (b), a DT-aware bootloader is expected to
24 DT block. In this case, Linux will look for a builtin DTB, selected via
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 15 depending on the use case. Interconnect providers can also be interconnect
16 consumers, such as in the case where two network-on-chip fabrics interface
42 multiple paths from different providers depending on use case and the
|
12345678910>>...43