Searched full:cases (Results 1 – 25 of 1611) sorted by relevance
12345678910>>...65
| /linux-3.3/tools/usb/ |
| D | hcd-tests.sh | 36 # NOTE: the 'in' and 'out' cases are usually bulk, but can be
105 echo '** Control test cases:'
123 echo '** Host Write (OUT) test cases:'
154 echo '** Host ISOCHRONOUS Write (OUT) test cases:'
181 echo '** Host Read (IN) test cases:'
207 echo '** Host ISOCHRONOUS Read (IN) test cases:'
|
| /linux-3.3/arch/arm/kernel/ |
| D | kprobes-test.h | 11 #define VERBOSE 0 /* Set to '1' for more logging of test cases */
35 * The arguments given to test cases can be one of three types.
87 * Building blocks for test cases.
97 * Some specific test cases may make use of other custom constructs.
190 * Macros to define test cases.
192 * Those of the form TEST_{R,P,M}* can be used to define test cases
415 /* Various values used in test cases... */
|
| /linux-3.3/arch/mips/ |
| D | Kconfig.debug | 31 For such cases, this option allows you to hardcode your own
49 pass arguments to the kernel. For these platforms, and for the cases
52 build time by entering them here. In other cases you can specify
|
| /linux-3.3/Documentation/development-process/ |
| D | 3.Early-stage | 13 clear description of the problem to be solved. In some cases, this step is
59 - Who are the users affected by this problem? Which use cases should the
116 In each of these cases, a great deal of pain and extra work could have been
195 mailing list may not be a viable option. In cases like this, it is worth
199 That said, there are also cases where a company legitimately cannot
|
| /linux-3.3/Documentation/power/regulator/ |
| D | design.txt | 21 Consumer use cases
31 => The consumer API should be structured so that these use cases are
|
| /linux-3.3/Documentation/DocBook/ |
| D | deviceiobook.tmpl | 161 device to ensure that writes have occurred in the specific cases the
163 writers in the API. In some cases, the read used to flush the device
258 driver that a DMA transaction is complete. In many cases, however,
262 <function>readb_relaxed</function> for these cases, although only
266 of how to use <function>readX_relaxed</function>. In many cases,
|
| /linux-3.3/Documentation/RCU/ |
| D | UP.txt | 60 In some cases, it would possible to restructure to code so that
62 there are cases where this can be quite ugly:
69 2. In some cases, the lock will be held across some kernel API,
|
| D | rcuref.txt | 64 update (write) stream. In such cases, atomic_inc_not_zero() might be
66 use atomic_inc() in such cases.
|
| /linux-3.3/Documentation/i2c/ |
| D | fault-codes | 10 some cases, such as re-initializing (and maybe resetting). After such
30 codes that may be returned, and other cases where these codes should
32 cases (unless the hardware doesn't provide unique fault reports).
|
| /linux-3.3/arch/sh/kernel/cpu/sh2a/ |
| D | opcode_helper.c | 40 /* Look for the common cases */ in instruction_size()
48 /* And the special cases.. */ in instruction_size()
|
| /linux-3.3/net/can/ |
| D | Kconfig | 26 most cases where no higher level protocol is being used. The raw
39 You probably want to use the bcm socket in most cases where cyclic
|
| /linux-3.3/Documentation/video4linux/ |
| D | cpia2_overview.txt | 14 mappings for the two chips. In these cases, the symbols defined in the
20 try to make note of all of these cases.
|
| /linux-3.3/Documentation/arm/OMAP/ |
| D | omap_pm | 115 specialized cases to convert that input information (OPPs/MPU
135 However, in special cases, the default OPP table may need to be
141 in these cases, the board file needs to do additional steps as follows:
|
| /linux-3.3/arch/x86/include/asm/ |
| D | local.h | 52 * other cases.
70 * cases.
88 * other cases.
|
| D | atomic64_64.h | 71 * other cases.
115 * cases.
133 * other cases.
|
| D | atomic64_32.h | 184 * other cases.
225 * cases.
238 * other cases.
|
| /linux-3.3/arch/m68k/fpsp040/ |
| D | sto_res.S | 35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
|
| /linux-3.3/arch/mips/include/asm/mach-au1x00/ |
| D | gpio.h | 31 * 4 use cases of Alchemy GPIOS:
45 * Cases 1 and 3 are intended for boards which want to provide their own
|
| /linux-3.3/Documentation/ |
| D | workqueue.txt | 20 There are many cases where an asynchronous process execution context
22 mechanism for such cases.
184 cases.
261 limiting factor while providing protection in runaway cases.
369 recommended. In most use cases, concurrency level usually stays
|
| D | kmemleak.txt | 180 the false negative cases described above.
182 The tool can report false positives. These are cases where an allocated
183 block doesn't need to be freed (some cases in the init_call functions),
|
| /linux-3.3/arch/mips/include/asm/ |
| D | local.h | 151 * other cases.
161 * other cases.
171 * cases.
|
| /linux-3.3/Documentation/power/ |
| D | states.txt | 38 suspended and put into D3. In many cases, all peripheral buses lose
67 requirements, but should work in most cases. Some, albeit outdated,
|
| /linux-3.3/Documentation/networking/ |
| D | udplite.txt | 131 cases the default of 8 is assumed.
184 length in such cases.
220 While it is important that such cases are dealt with correctly, they
239 These cases are counted separately (not as InErrors).
|
| /linux-3.3/Documentation/ia64/ |
| D | aliasing.txt | 83 POTENTIAL ATTRIBUTE ALIASING CASES
133 There may be corner cases of things that are not in kern_memmap,
158 PAST PROBLEM CASES
|
| /linux-3.3/Documentation/crypto/ |
| D | async-tx-api.txt | 48 API automatically handles cases where the transition from one operation
178 Primarily this requirement arises from cases where a DMA engine driver
181 be shared. For these cases the dma_request_channel() interface is
|
12345678910>>...65