Home
last modified time | relevance | path

Searched full:exactly (Results 1 – 25 of 1163) sorted by relevance

12345678910>>...47

/kernel/linux/linux-5.10/drivers/media/test-drivers/vidtv/
Dvidtv_ts.c77 /* we should have written exactly _one_ 188byte packet */ in vidtv_ts_null_write_into()
79 pr_warn_ratelimited("Expected exactly %d bytes, got %d\n", in vidtv_ts_null_write_into()
129 /* we should have written exactly _one_ 188byte packet */ in vidtv_ts_pcr_write_into()
131 pr_warn_ratelimited("Expected exactly %d bytes, got %d\n", in vidtv_ts_pcr_write_into()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ti/
Dcomposite.txt9 of which can be selected as output, this behaves exactly as [2]
11 an adjustable clock rate divider, this behaves exactly as [3]
14 clock, this behaves exactly as [4]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/serial/
Darm_sbsa_uart.txt8 - reg: exactly one register range
9 - interrupts: exactly one interrupt specifier
/kernel/linux/linux-5.10/Documentation/staging/
Dlzo.rst142 Always followed by exactly one byte : H H H H H H H H
152 Always followed by exactly one byte : H H H H H H H H
158 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
175 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
183 Always followed by exactly one byte : H H H H H H H H
190 Always followed by exactly one byte : H H H H H H H H
/kernel/linux/linux-5.10/tools/lib/perf/
Dlib.c34 * Read exactly 'n' bytes or return an error.
42 * Write exactly 'n' bytes or return an error.
/kernel/linux/linux-5.10/tools/perf/util/
Devents_stats.h14 * total_lost tells exactly how many events the kernel in fact lost, i.e. it is
20 * exactly how many samples the kernel in fact dropped, i.e. it is the sum of
/kernel/linux/linux-5.10/arch/hexagon/kernel/
Dptrace.c43 * exactly the same order in which the userspace expects these in genregs_get()
49 /* Must be exactly same sequence as struct user_regs_struct */ in genregs_get()
94 /* Must be exactly same sequence as struct user_regs_struct */ in genregs_set()
/kernel/linux/linux-5.10/Documentation/driver-api/
Dmen-chameleon-bus.rst97 The current implementation assigns exactly one memory and one IRQ resource
103 Each MCB device has exactly one memory resource, which can be requested from
111 Each MCB device has exactly one IRQ resource, which can be requested from the
Dswitchtec.rst43 * Each write must be followed by exactly one read. Any double write will
88 exactly 2 NT partitions and zero or more non-NT partitions. It also requires
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/amdgpu_dm/
Damdgpu_dm_irq.h36 * This function should be called exactly once - during DM initialization.
47 * This function should be called exactly once - during DM destruction.
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dtuner.rst21 Radio input devices have exactly one tuner with index zero, no video
54 Radio output devices have exactly one modulator with index zero, no
Dpixfmt-compressed.rst70 :ref:`associated Codec Control IDs <v4l2-mpeg-h264>`. Exactly
120 Exactly one output and one capture buffer must be provided for use with
161 Exactly one output and one capture buffer must be provided for use with
/kernel/linux/linux-5.10/Documentation/scsi/
Dsmartpqi.rst63 The above three ioctls all do exactly the same thing, which is to cause the driver
64 to rescan for new devices. This does exactly the same thing as writing to the
/kernel/linux/linux-5.10/drivers/tty/ipwireless/
Dtty.c237 /* FIXME: Exactly how is the tty object locked here .. */ in ipw_write_room()
357 /* FIXME: Exactly how is the tty object locked here .. */ in ipw_tiocmget()
373 /* FIXME: Exactly how is the tty object locked here .. */ in ipw_tiocmset()
395 /* FIXME: Exactly how is the tty object locked here .. */ in ipw_ioctl()
533 /* FIXME: Exactly how is the tty object locked here in ipwireless_tty_free()
/kernel/linux/linux-5.10/include/drm/
Ddrm_managed.h74 * memory is automatically freed on the final drm_dev_put() and works exactly
96 * automatically freed on the final drm_dev_put() and works exactly like a
/kernel/linux/linux-5.10/fs/efs/
Defs.h35 * layout of an extent, in memory and on disk. 8 bytes exactly.
54 * is exactly 128 bytes long.
/kernel/linux/linux-5.10/Documentation/driver-api/usb/
Dpersist.rst39 devices. The effect is exactly the same as if the device really had
82 port reset and then re-enumerates the device. (This is exactly the
153 Furthermore it's quite possible to leave a USB device exactly the same
/kernel/linux/linux-5.10/scripts/kconfig/tests/
Dconftest.py248 """Check if resulted configuration exactly matches expected data.
264 """Check if resulted stdout exactly matches expected data.
280 """Check if resulted stderr exactly matches expected data.
/kernel/linux/linux-5.10/arch/x86/math-emu/
Dreg_round.S56 | exactly 0x80000000 <=> the significand is exactly 1/2 an ls bit |
225 /* Exactly half, increment only if 24th bit is 1 (round to even) */
301 /* Exactly half, increment only if 53rd bit is 1 (round to even) */
533 /* Exactly 64 bit shift */
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-driver-tegra-fuse9 exactly matches the HW registers, including any unused bits.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dspe-pmu.txt11 - interrupts : Exactly 1 PPI must be listed. For heterogeneous systems where
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/
Dsprd-wdt.txt6 - interrupts : Exactly one interrupt specifier.
/kernel/linux/linux-5.10/fs/quota/
Dquota_tree.h14 * there will be space for exactly 21 quota-entries in a block
/kernel/linux/linux-5.10/arch/mips/math-emu/
Dsp_fmin.c58 * The cases of exactly one input quiet NaN (numbers in ieee754sp_fmin()
184 * The cases of exactly one input quiet NaN (numbers in ieee754sp_fmina()
Ddp_fmax.c58 * The cases of exactly one input quiet NaN (numbers in ieee754dp_fmax()
184 * The cases of exactly one input quiet NaN (numbers in ieee754dp_fmaxa()

12345678910>>...47