Searched refs:IOW (Results 1 – 16 of 16) sorted by relevance
| /linux/Documentation/arch/m68k/ |
| H A D | buddha-driver.rst | 140 All the timings have in common: Select and IOR/IOW rise at 141 the same time. IOR and IOW have a propagation delay of 147 497ns Select (7 clock cycles) , IOR/IOW after 172ns (2 clock cycles) 152 639ns Select (9 clock cycles), IOR/IOW after 243ns (3 clock cycles) 155 781ns Select (11 clock cycles), IOR/IOW after 314ns (4 clock cycles) 158 355ns Select (5 clock cycles), IOR/IOW after 101ns (1 clock cycle) 161 355ns Select (5 clock cycles), IOR/IOW after 172ns (2 clock cycles) 164 355ns Select (5 clock cycles), IOR/IOW after 243ns (3 clock cycles) 167 1065ns Select (15 clock cycles), IOR/IOW after 314ns (4 clock cycles) 170 355ns Select, (5 clock cycles), IOR/IOW after 101ns (1 clock cycle) [all …]
|
| /linux/include/uapi/drm/ |
| H A D | armada_drm.h | 50 ARMADA_IOCTL(IOW, GEM_PWRITE, gem_pwrite)
|
| /linux/rust/kernel/drm/ |
| H A D | ioctl.rs | 28 pub const fn IOW<T>(nr: u32) -> u32 { in IOW() function
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 20 Disparity in maximum attainable performance (IOW in maximum CPU capacity) stems 206 IOW, 359 tasks. IOW, CFS wakeup CPU selection searches for a CPU that satisfies:: 405 then it might become CPU-bound, IOW ``task_util(p) > capacity(task_cpu(p))``;
|
| H A D | schedutil.rst | 84 of DVFS and CPU type. IOW. we can transfer and compare them between CPUs.
|
| H A D | sched-util-clamp.rst | 463 rqs are restricted too. IOW, the whole system is capped to half its performance
|
| /linux/tools/crypto/ccp/ |
| H A D | test_dbc.py | 91 INVALID2 = ioctl.IOW(ord("D"), 0x02, invalid_param)
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zram.rst | 26 IOW, zram and zram_control sysfs attributes. 398 any writeback. IOW, if admin wants to apply writeback budget, they should
|
| /linux/Documentation/scsi/ |
| H A D | scsi_eh.rst | 431 SCSI midlayer. IOW, of the steps described in [2-1-2], all steps
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-regressions.rst | 403 In that mail, use one of the following commands in a stand-alone paragraph (IOW:
|
| H A D | kernel-parameters.txt | 1013 IOW, each message will have a facility and loglevel
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 525 IOW, whether there is a locker L3 that L1 blocks L3 and L2 gets blocked by L3. So
|
| /linux/Documentation/driver-api/ |
| H A D | libata.rst | 656 error can be acquired from STATUS or ERROR register. IOW, this error can
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 404 regression report. These commands need to be in their own paragraph (IOW: they
|
| /linux/Documentation/filesystems/ |
| H A D | porting.rst | 822 done by ->alloc_inode(). IOW, if it's cleaning up the stuff that
|
| /linux/lib/ |
| H A D | Kconfig.debug | 72 will be used as the loglevel. IOW passing "quiet" will be the
|