Searched full:case (Results 1 – 25 of 998) sorted by relevance
12345678910>>...40
| /Documentation/media/uapi/v4l/ |
| D | capture.c.rst | 97 case IO_METHOD_READ:
100 case EAGAIN:
103 case EIO:
116 case IO_METHOD_MMAP:
124 case EAGAIN:
127 case EIO:
145 case IO_METHOD_USERPTR:
153 case EAGAIN:
156 case EIO:
227 case IO_METHOD_READ:
[all …]
|
| /Documentation/ |
| D | nommu-mmap.txt | 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 …]
|
| D | IRQ.txt | 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/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…
|
| D | exception-tables.rst | 21 normal case (correctly working program), this test was successful.
46 we are interested in the other case: the address is not valid, there
47 is no vma that contains this address. In this case, the kernel jumps
81 case 1:
95 case 2:
109 case 4:
251 in our case the address of the label 1 is c017e7a5:
256 the fault, in our case the actual value is c0199ff5:
333 This is legacy case that just jumps to the fixup code
336 This case provides the fault number of the trap that occurred at
[all …]
|
| /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/networking/ |
| D | 6lowpan.txt | 34 case ARPHRD_6LOWPAN:
38 case LOWPAN_LLTYPE_FOOBAR:
48 In case of generic 6lowpan branch ("net/6lowpan") you can remove the check
|
| /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:
|
| D | inline-encryption.rst | 91 not. So in the case that a particular device does not support IE, since it is
117 **Case 1:** blk-crypto is given a bio with only an encryption context that hasn't
119 In this case, blk-crypto will program the encryption context into the KSM of the
125 **Case 2:** blk-crypto is given a bio whose encryption context has already been
127 In this case, blk-crypto does nothing; it treats the bio as not having
129 in Case 3 because we would have already encrypted the bio via the crypto API
132 **Case 3:** blk-crypto is given a bio whose encryption context has already been
135 In this case, blk-crypto first releases that keyslot from that KSM and then
136 treats the bio as in Case 1.
159 blk-crypto, which will work as described in Case 3. If a layered device wants
[all …]
|
| /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
53 Might return "<denied>" in case of special security settings
70 Might return "0" in case of special security settings
102 Might return "<denied>" in case of special security settings
|
| /Documentation/virt/kvm/devices/ |
| D | vm.txt | 41 the number of page table levels. In the case that there is no limit we will set
63 0 in case of success
84 Returns: -EBUSY in case 1 or more vcpus are already activated (only in write case)
87 0 in case of success
101 0 in case of success.
114 0 in case of success.
150 0 in case of success.
164 to determine available subfunctions in this case, this will guarantee backward
173 0 in case of success.
260 0 in case of success.
[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/devicetree/bindings/iio/adc/ |
| D | nuvoton,npcm-adc.txt | 11 - clocks: phandle of ADC reference clock, in case the clock is not
13 - vref-supply: The regulator supply ADC reference voltage, in case the
|
| /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
41 multiple paths from different providers depending on use case and the
|
| /Documentation/devicetree/bindings/net/ |
| D | mediatek-dwmac.txt | 38 1. tx clock will be inversed in MII/RGMII case,
40 which is from external PHYs in RMII case, and it rarely happen.
42 1. rx clock will be inversed in MII/RGMII case.
43 2. reference clock will be inversed when arrived at MAC in RMII case.
|
| /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/filesystems/nfs/ |
| D | knfsd-stats.txt | 42 Note that in the default case there will be a single thread pool
73 case configuring more nfsd threads will probably improve the
108 this case), or the transport can be enqueued for later attention
109 (sockets-enqueued counts this case), or the packet can be temporarily
111 thread. This last case is not very interesting and is not explicitly
|
| /Documentation/devicetree/bindings/power/ |
| D | domain-idle-state.txt | 16 Definition: u32 value representing worst case latency in
24 Definition: u32 value representing worst case latency
|
| /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/filesystems/ |
| D | isofs.txt | 21 check=strict Matches only filenames with the exact same case
23 map=off Do not map non-Rock Ridge filenames to lower case
24 map=normal Map non-Rock Ridge filenames to lower case
|
| /Documentation/devicetree/bindings/usb/ |
| D | generic.txt | 6 "full-speed" and "low-speed". In case this isn't passed
11 "peripheral" and "otg". In case this attribute isn't
17 In case this isn't passed via DT, USB controllers should
|
| /Documentation/core-api/ |
| 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
|
12345678910>>...40