Home
last modified time | relevance | path

Searched refs:leading (Results 1 – 25 of 97) sorted by relevance

1234

/Linux-v5.4/drivers/media/i2c/
Dir-kbd-i2c.c574 int leading = c - rep * 3; in zilog_ir_format() local
576 if (leading >= ARRAY_SIZE(code_block->codes) - 3 - rep) { in zilog_ir_format()
582 copy_codes(code_block->codes, codes, leading); in zilog_ir_format()
583 code_block->codes[leading] = 0x82; in zilog_ir_format()
584 copy_codes(code_block->codes + leading + 1, codes + leading, in zilog_ir_format()
586 c = leading + 1 + rep; in zilog_ir_format()
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Dusb-device.txt23 with leading zeroes suppressed. The other compatible strings from the above
39 case hexadecimal with leading zeroes suppressed. The other compatible
52 with leading zeroes suppressed. The other compatible strings from the above
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-rtc89 epoch by default, or if there's a leading +, seconds in the
90 future, or if there is a leading +=, seconds ahead of the
/Linux-v5.4/arch/alpha/lib/
Dstrncpy.S73 1: ldq_u $1, 0($16) # clear the leading bits in the final word
Dev67-strrchr.S103 subq t5, t2, t5 # E : Normalize leading zero count
Dev6-copy_user.S54 and $16,7,$3 # .. .. .. E : is leading dest misalignment
/Linux-v5.4/Documentation/pcmcia/
Ddriver.rst15 All fields are passed in as hexadecimal values (no leading 0x).
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dmdio-mux-meson-g12a.txt4 the internal mdio bus leading to the embedded 10/100 PHY or the external
/Linux-v5.4/Documentation/arm/nwfpe/
Dnwfpe.rst15 the problems is with leading underscores on kernel symbols. Elf
16 kernels have no leading underscores, a.out compiled kernels do. I
/Linux-v5.4/arch/arm/boot/dts/
Domap-gpmc-smsc9221.dtsi6 * or smsc 9218) has faster timings, leading to higher
/Linux-v5.4/Documentation/i2c/
Dten-bit-addresses.rst10 address space, namely 0xa000-0xa3ff. The leading 0xa (= 10) represents the
/Linux-v5.4/Documentation/devicetree/bindings/slimbus/
Dbus.txt32 Product Code, shall be in lower case hexadecimal with leading
/Linux-v5.4/kernel/
DKconfig.hz16 environment leading to NR_CPUS * HZ number of timer interrupts
/Linux-v5.4/Documentation/devicetree/
Dwriting-schema.rst23 with a leading '/' will have the hostname prepended. A $ref value a relative
73 binding. Note: YAML doesn't allow leading tabs, so spaces must be used instead.
/Linux-v5.4/arch/c6x/lib/
Ddivremu.S11 ;; out how many leading zero bits there are in the divisor. This
Ddivu.S28 ;; out how many leading zero bits there are in the divisor. This
/Linux-v5.4/Documentation/media/uapi/v4l/
Ddev-event.rst52 is lost, but only an intermediate step leading up to that
/Linux-v5.4/drivers/target/iscsi/
Discsi_target_parameters.c564 int leading) in iscsi_copy_param_list() argument
579 if (!leading && (param->scope & SCOPE_SESSION_WIDE)) { in iscsi_copy_param_list()
1605 int leading) in iscsi_set_session_parameters() argument
1618 if (leading) in iscsi_set_session_parameters()
1635 if (leading) in iscsi_set_session_parameters()
/Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Dsifive,plic-1.0.0.txt19 interrupt line leading to the context.
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Dqcom,wcd9335.txt16 shall be in lower case hexadecimal with leading zeroes
/Linux-v5.4/arch/m68k/fpsp040/
Ddecbin.S36 | A3. Count the number of leading/trailing zeros in the
37 | bcd string. If SE is positive, count the leading zeros;
/Linux-v5.4/tools/testing/selftests/kvm/lib/
Dsparsebit.c903 mask_t leading = (mask_t)1 << start; in node_first_set() local
904 int n1 = __builtin_ctz(nodep->mask & -leading); in node_first_set()
911 mask_t leading = (mask_t)1 << start; in node_first_clear() local
912 int n1 = __builtin_ctz(~nodep->mask & -leading); in node_first_clear()
/Linux-v5.4/arch/sh/
DKconfig.debug53 This prints out a code trace of the instructions leading up to
/Linux-v5.4/Documentation/kbuild/
Dkconfig-macro-language.rst153 whitespace. Then, leading whitespaces are trimmed from the first argument,
168 of leading spaces may matter depending on the function. The same applies to
/Linux-v5.4/tools/perf/Documentation/
Dperf-top.txt251 the pausing used in this technique is leading to loss of metadata events such
252 as PERF_RECORD_MMAP which makes 'perf top' unable to resolve samples, leading

1234