Searched full:possibilities (Results 1 – 25 of 250) sorted by relevance
12345678910
129 * resolve the two possibilities. */ in dbl_fcmp()156 * resolve the two possibilities. */ in dbl_fcmp()
54 * struct clk.flags possibilities74 * @flags: see "struct clk.flags possibilities" above
9 * struct omap_hsmmc_dev_attr.flags possibilities
23 /* struct clksel_rate.flags possibilities */
28 basically three possibilities:
9 /* some have two possibilities for cpuid string */
37 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
142 * @flags: see "struct clk.flags possibilities" above167 * struct clk_hw_omap.flags possibilities
79 * struct clk.flags possibilities114 * @flags: see "struct clk.flags possibilities" above
55 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
40 * There are five possibilities for how page->flags get laid out. The first
39 * There are five possibilities for how page->flags get laid out. The first
156 * @flags: see "struct clk.flags possibilities" above181 * struct clk_hw_omap.flags possibilities
55 * possibilities of egress port masks for L2 multicast traffic.
38 possibilities of lost update and race condition problems should be
45 non-privileged mounts. This opens up new possibilities for the use of160 original request and its INTERRUPT request. There are two possibilities:
12 scheduling for ages. This document mainly details the current possibilities
10 * The protocol is very simply, there are two possibilities reading or writing.