Searched full:interfere (Results 1 – 25 of 155) sorted by relevance
1234567
12 The torture tests may interfere with the PSCI checker by turning CPUs
21 performances. This can interfere with real-time tasks; even if they
29 not interfere in I2C communication. There is no need for a GPIO
30 * setitimer(2) while using this API - they may interfere with each
40 On some systems (Asus), the BIOS is known to interfere with the driver
36 This means that flooding of one event type will not interfere with
35 * The ARC write and read functions seem to interfere with the serial lines
127 is turned on, and also will interfere with JTAG-based trace
296 * interface that interfere with the test. Just drop them.
50 * to interfere with devices that were bug-free (has been tested). in speedlink_event()
43 * these are chomped so as to not interfere with normal IRQs. in store_intc_userimask()
46 * writes to neighbouring locations within a cacheline do not interfere
39 interfere with LSM-based sandboxing.)
24 # Use '-idirafter': Don't interfere with include mechanics except where the
19 chosen so it doesn't interfere with other PHYs on the bus.
78 * application knows it won't interfere with other nodes (or doesn't
30 rest of the modules won't interfere with the operation. The next
159 * if reading the Count register might interfere with the timer in time_init()
41 sloppy logic analyzer does not interfere with your other settings.
101 callback. You also may not do any other operation that may interfere
15 state to interfere with the rest of the system).
91 * don't interfere with hour overflow. This avoids in update_persistent_clock64()
42 * interfere with SW control. in nvkm_pmu_fan_controlled()
39 Any use of the NEON/VFP unit in kernel mode should not interfere with this, so
54 * mapped with strict permissions, as those might interfere in create_mapping_protection()