Searched full:couple (Results 1 – 25 of 330) sorted by relevance
12345678910>>...14
/linux-6.12.1/Documentation/scsi/ |
D | ChangeLog.sym53c8xx_2 | 7 - Change a couple of defines containing ncr or NCR by their 12 - Fix a couple of printfs: 80 - A couple of comments fixes. 100 - A couple of tiny fixes ... 134 - Fix a couple of gcc/gcc3 warnings.
|
/linux-6.12.1/sound/soc/qcom/qdsp6/ |
D | q6afe.h | 149 /* Clock attribute for no couple case */ 151 /* Clock attribute for dividend couple case */ 153 /* Clock attribute for divisor couple case */ 155 /* Clock attribute for invert and no couple case */
|
/linux-6.12.1/tools/testing/selftests/ftrace/test.d/preemptirq/ |
D | irqsoff_tracer.tc | 33 # Simulate preemptoff section for half a second couple of times 56 # Simulate irqsoff section for half a second couple of times
|
/linux-6.12.1/Documentation/core-api/irq/ |
D | irqflags-tracing.rst | 24 Architectures that want to support this need to do a couple of 29 and then a couple of functional changes are needed as well to implement
|
/linux-6.12.1/arch/mips/include/asm/ |
D | pm.h | 33 /* A couple of CP0 registers with space in pt_regs */ 42 /* A couple of CP0 registers with space in pt_regs */
|
/linux-6.12.1/Documentation/arch/arm/nwfpe/ |
D | todo.rst | 25 There are a couple of ways to approach the implementation of these. One 27 a couple of papers by S. Gal from IBM's research labs in Haifa, Israel that
|
/linux-6.12.1/drivers/gpu/drm/lib/ |
D | drm_random.h | 5 /* This is a temporary home for a couple of utility functions that should
|
/linux-6.12.1/Documentation/devicetree/bindings/sound/ |
D | qcom,q6dsp-lpass-clocks.yaml | 28 4 = for inverted and no couple clock
|
/linux-6.12.1/Documentation/doc-guide/ |
D | contributing.rst | 65 A quick look at the source file named above turned up a couple of kerneldoc 96 Add a couple of missing asterisks and make kerneldoc a little happier. 253 to continue. There are a couple of challenges associated with this work,
|
/linux-6.12.1/drivers/gpu/drm/xe/ |
D | xe_guc_log.h | 24 * "elaborate"? We have a couple of bits for verbosity, separate bit for actual
|
/linux-6.12.1/Documentation/devicetree/bindings/arm/ |
D | google.yaml | 25 Likewise there are a couple of names for the actual device
|
/linux-6.12.1/arch/m68k/coldfire/ |
D | reset.c | 20 * the CPU. But there are couple of exceptions, the 5272 and the 547x
|
/linux-6.12.1/Documentation/admin-guide/ |
D | lcd-panel-cgram.rst | 9 (';'). Each couple of digits represents a line, with 1-bits for each
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | dev-radio.rst | 43 Radio devices may have a couple audio controls (as discussed in
|
/linux-6.12.1/Documentation/devicetree/bindings/fpga/ |
D | xlnx,pr-decoupler.yaml | 19 can also couple / enable the bridges which allows traffic to pass through the
|
/linux-6.12.1/include/linux/ |
D | nfs.h | 6 * but also has a couple of NFSv3 bits in (notably the error codes).
|
/linux-6.12.1/Documentation/mhi/ |
D | topology.rst | 36 couple of channels.
|
/linux-6.12.1/tools/testing/selftests/net/ |
D | route_localnet.sh | 4 # Run a couple of tests when route_localnet = 1.
|
D | ip_defrag.sh | 4 # Run a couple of IP defragmentation tests.
|
/linux-6.12.1/Documentation/hwmon/ |
D | acpi_power_meter.rst | 22 interval, an optional capping mechanism, and a couple of trip points. The
|
/linux-6.12.1/tools/testing/selftests/arm64/signal/ |
D | README | 46 - a couple of ASSERT_BAD/GOOD_CONTEXT() macros to easily parse a ucontext_t
|
/linux-6.12.1/drivers/gpu/drm/i915/gt/uc/ |
D | intel_guc_log.h | 20 * "elaborate"? We have a couple of bits for verbosity, separate bit for actual
|
/linux-6.12.1/drivers/net/wireless/ralink/rt2x00/ |
D | rt2x00mmio.h | 57 * register is busy. If it is, it will sleep for a couple of
|
/linux-6.12.1/tools/perf/Documentation/ |
D | perf-script-python.txt | 76 that script. Theoretically, there are a couple of ways we could do 163 Following that are a couple generated functions, trace_begin() and 175 The final couple of functions are, like the begin and end functions, 330 writing a couple of very simple shell scripts and putting them in the
|
/linux-6.12.1/Documentation/driver-api/usb/ |
D | writing_musb_glue_layer.rst | 35 hardware level. A couple of wiki pages by Texas Instruments and Analog 98 resources and initialising a couple of circuits. To do so, it needs to 274 data. The next couple of instructions (line 12 and 14) are used as a 680 These are only a couple of the quirks found in the JZ4740 USB device
|
12345678910>>...14