Home
last modified time | relevance | path

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

12345

/Linux-v5.10/arch/parisc/math-emu/
Ddfcmp.c129 * resolve the two possibilities. */ in dbl_fcmp()
156 * resolve the two possibilities. */ in dbl_fcmp()
/Linux-v5.10/include/linux/platform_data/
Dhsmmc-omap.h9 * struct omap_hsmmc_dev_attr.flags possibilities
/Linux-v5.10/arch/x86/kernel/cpu/
Dcpu.h9 /* some have two possibilities for cpuid string */
/Linux-v5.10/arch/arm/mach-omap2/
Dclock.h23 /* struct clksel_rate.flags possibilities */
/Linux-v5.10/arch/arm64/kernel/
Dperf_regs.c37 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
/Linux-v5.10/arch/arm/mach-omap1/
Dclock.h79 * struct clk.flags possibilities
114 * @flags: see "struct clk.flags possibilities" above
/Linux-v5.10/include/linux/clk/
Dti.h142 * @flags: see "struct clk.flags possibilities" above
167 * struct clk_hw_omap.flags possibilities
/Linux-v5.10/include/linux/
Dpage-flags-layout.h39 * There are five possibilities for how page->flags get laid out. The first
/Linux-v5.10/Documentation/driver-api/media/
Ddtv-demux.rst38 possibilities of lost update and race condition problems should be
Dcamera-sensor.rst57 There are two different methods for obtaining possibilities for different frame
/Linux-v5.10/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:
Dromfs.rst168 Un*x like system, but romfs does not provide the full possibilities.
/Linux-v5.10/Documentation/block/
Dioprio.rst12 scheduling for ages. This document mainly details the current possibilities
/Linux-v5.10/drivers/usb/serial/
Daircable.c10 * The protocol is very simply, there are two possibilities reading or writing.
/Linux-v5.10/Documentation/devicetree/bindings/mtd/
Dnand-controller.yaml63 basically three possibilities:
/Linux-v5.10/Documentation/driver-api/
Dmen-chameleon-bus.rst33 implementation and does by no means describe the complete possibilities of MCB
/Linux-v5.10/sound/aoa/soundbus/
Dsoundbus.h66 /* supported transfer possibilities, array terminated by
/Linux-v5.10/Documentation/RCU/
Drcu_dereference.rst135 time ago"? Here are some possibilities:
150 There are many other possibilities involving the Linux
/Linux-v5.10/drivers/net/wireless/ralink/rt2x00/
Drt2x00crypto.c179 * Make room for new data. There are 2 possibilities in rt2x00crypto_rx_insert_iv()
/Linux-v5.10/fs/reiserfs/
DREADME74 aggressive in taking advantage of the commercial possibilities of
/Linux-v5.10/arch/s390/include/uapi/asm/
Dpkey.h235 * flags to widen the export possibilities. By default a cipher key is
268 * flags to widen the export possibilities. By default a cipher key is
/Linux-v5.10/Documentation/devicetree/bindings/media/i2c/
Dtda1997x.txt22 for a variety of connection possibilities including swapping pin order within
/Linux-v5.10/drivers/video/fbdev/omap2/omapfb/dss/
Dsdi.c77 * DSS fclk gives us very few possibilities, so finding a good pixel in sdi_calc_clock_div()
/Linux-v5.10/Documentation/sound/cards/
Dhdspm.rst87 Samples, which is a quarter of the interrupt possibilities.)
/Linux-v5.10/drivers/staging/comedi/drivers/
Dni_atmio.c42 * Some of the more esoteric triggering possibilities of these boards are

12345