Home
last modified time | relevance | path

Searched full:possibilities (Results 1 – 25 of 135) sorted by relevance

123456

/linux-6.14.4/arch/parisc/math-emu/
Ddfcmp.c129 * resolve the two possibilities. */ in dbl_fcmp()
156 * resolve the two possibilities. */ in dbl_fcmp()
/linux-6.14.4/arch/arm/mach-omap1/
Dclock.h54 * struct clk.flags possibilities
74 * @flags: see "struct clk.flags possibilities" above
/linux-6.14.4/arch/arm/mach-omap2/
Dclock.h23 /* struct clksel_rate.flags possibilities */
/linux-6.14.4/include/linux/platform_data/
Dhsmmc-omap.h9 * struct omap_hsmmc_dev_attr.flags possibilities
/linux-6.14.4/Documentation/devicetree/bindings/mtd/
Dnand-chip.yaml28 basically three possibilities:
/linux-6.14.4/arch/x86/kernel/cpu/
Dcpu.h14 /* some have two possibilities for cpuid string */
Dhygon.c65 * Two possibilities here: in srat_detect_node()
/linux-6.14.4/include/linux/
Dpage-flags-layout.h40 * There are five possibilities for how page->flags get laid out. The first
/linux-6.14.4/arch/arm64/kernel/
Dperf_regs.c55 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
/linux-6.14.4/include/linux/clk/
Dti.h159 * @flags: see "struct clk.flags possibilities" above
184 * struct clk_hw_omap.flags possibilities
/linux-6.14.4/drivers/net/ethernet/mscc/
Docelot.h55 * possibilities of egress port masks for L2 multicast traffic.
/linux-6.14.4/tools/objtool/
Dorc_gen.c88 * possibilities (but they shouldn't conflict). in orc_create()
/linux-6.14.4/Documentation/driver-api/media/
Ddtv-demux.rst38 possibilities of lost update and race condition problems should be
/linux-6.14.4/Documentation/userspace-api/media/drivers/
Dcamera-sensor.rst43 There are two different methods for obtaining possibilities for different frame
/linux-6.14.4/arch/arm64/kvm/
Dhandle_exit.c231 * Two possibilities to handle a trapping ptrauth instruction:
268 * If we got here, two possibilities: in kvm_handle_eret()
/linux-6.14.4/drivers/usb/serial/
Daircable.c10 * The protocol is very simply, there are two possibilities reading or writing.
/linux-6.14.4/Documentation/filesystems/
Dfuse.rst45 non-privileged mounts. This opens up new possibilities for the use of
160 original request and its INTERRUPT request. There are two possibilities:
/linux-6.14.4/drivers/hwmon/
Dhs3001.c5 * the configuration possibilities, where it needs to be set to 'programming mode'
/linux-6.14.4/Documentation/driver-api/
Dmen-chameleon-bus.rst34 implementation and does by no means describe the complete possibilities of MCB
/linux-6.14.4/drivers/net/wireless/ralink/rt2x00/
Drt2x00crypto.c179 * Make room for new data. There are 2 possibilities in rt2x00crypto_rx_insert_iv()
/linux-6.14.4/sound/aoa/soundbus/
Dsoundbus.h66 /* supported transfer possibilities, array terminated by
/linux-6.14.4/Documentation/RCU/
Drcu_dereference.rst161 time ago"? Here are some possibilities:
176 There are many other possibilities involving the Linux
/linux-6.14.4/arch/s390/include/uapi/asm/
Dpkey.h254 * flags to widen the export possibilities. By default a cipher key is
288 * flags to widen the export possibilities. By default a cipher key is
/linux-6.14.4/Documentation/devicetree/bindings/media/i2c/
Dtda1997x.txt22 for a variety of connection possibilities including swapping pin order within
/linux-6.14.4/Documentation/gpu/amdgpu/display/
Dprogramming-model-dcn.rst41 arrangement possibilities. In some way, just displaying an image via DCN should

123456