/linux/arch/parisc/math-emu/ |
H A D | dfcmp.c | 129 * resolve the two possibilities. */ in dbl_fcmp() 156 * resolve the two possibilities. */ in dbl_fcmp()
|
/linux/arch/arm/mach-omap1/ |
H A D | clock.h | 54 * struct clk.flags possibilities 74 * @flags: see "struct clk.flags possibilities" above
|
/linux/arch/arm/mach-omap2/ |
H A D | clock.h | 23 /* struct clksel_rate.flags possibilities */
|
/linux/include/linux/platform_data/ |
H A D | hsmmc-omap.h | 9 * struct omap_hsmmc_dev_attr.flags possibilities
|
/linux/Documentation/devicetree/bindings/mtd/ |
H A D | nand-chip.yaml | 28 basically three possibilities:
|
/linux/arch/x86/kernel/cpu/ |
H A D | cpu.h | 14 /* some have two possibilities for cpuid string */
|
H A D | hygon.c | 65 * Two possibilities here: in srat_detect_node()
|
/linux/include/linux/clk/ |
H A D | ti.h | 159 * @flags: see "struct clk.flags possibilities" above 184 * struct clk_hw_omap.flags possibilities
|
/linux/arch/arm64/kernel/ |
H A D | perf_regs.c | 55 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
|
/linux/drivers/net/ethernet/mscc/ |
H A D | ocelot.h | 55 * possibilities of egress port masks for L2 multicast traffic.
|
/linux/tools/objtool/ |
H A D | orc_gen.c | 88 * possibilities (but they shouldn't conflict). in orc_create()
|
/linux/arch/arm64/kvm/ |
H A D | handle_exit.c | 231 * Two possibilities to handle a trapping ptrauth instruction: 268 * If we got here, two possibilities: in kvm_handle_eret()
|
/linux/Documentation/driver-api/media/ |
H A D | dtv-demux.rst | 38 possibilities of lost update and race condition problems should be
|
/linux/Documentation/userspace-api/media/drivers/ |
H A D | camera-sensor.rst | 43 There are two different methods for obtaining possibilities for different frame
|
/linux/Documentation/filesystems/ |
H A D | fuse.rst | 45 non-privileged mounts. This opens up new possibilities for the use of 160 original request and its INTERRUPT request. There are two possibilities:
|
H A D | romfs.rst | 168 Un*x like system, but romfs does not provide the full possibilities.
|
/linux/drivers/usb/serial/ |
H A D | aircable.c | 10 * The protocol is very simply, there are two possibilities reading or writing.
|
/linux/drivers/hwmon/ |
H A D | hs3001.c | 5 * the configuration possibilities, where it needs to be set to 'programming mode'
|
/linux/sound/aoa/soundbus/ |
H A D | soundbus.h | 66 /* supported transfer possibilities, array terminated by
|
/linux/Documentation/driver-api/ |
H A D | men-chameleon-bus.rst | 34 implementation and does by no means describe the complete possibilities of MCB
|
/linux/drivers/net/wireless/ralink/rt2x00/ |
H A D | rt2x00crypto.c | 179 * Make room for new data. There are 2 possibilities in rt2x00crypto_rx_insert_iv()
|
/linux/Documentation/RCU/ |
H A D | rcu_dereference.rst | 161 time ago"? Here are some possibilities: 176 There are many other possibilities involving the Linux
|
/linux/arch/s390/include/uapi/asm/ |
H A D | pkey.h | 254 * 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/Documentation/devicetree/bindings/media/i2c/ |
H A D | tda1997x.txt | 22 for a variety of connection possibilities including swapping pin order within
|
/linux/drivers/video/fbdev/omap2/omapfb/dss/ |
H A D | sdi.c | 78 * DSS fclk gives us very few possibilities, so finding a good pixel in sdi_calc_clock_div()
|