Searched refs:grabbing (Results 1 – 19 of 19) sorted by relevance
| /linux-6.3-rc2/drivers/media/pci/ttpci/ |
| A D | budget-core.c | 67 memset(budget->grabbing, 0x00, budget->buffer_size); in start_ts_capture()
177 u8 *mem = (u8 *) (budget->grabbing); in vpeirq()
513 budget->grabbing = saa7146_vmalloc_build_pgtable(dev->pci, budget->buffer_size, &budget->pt); in ttpci_budget_init()
514 if (NULL == budget->grabbing) { in ttpci_budget_init()
533 saa7146_vfree_destroy_pgtable(dev->pci, budget->grabbing, &budget->pt); in ttpci_budget_init()
562 saa7146_vfree_destroy_pgtable(dev->pci, budget->grabbing, &budget->pt); in ttpci_budget_deinit()
|
| A D | budget.h | 49 unsigned char *grabbing; member
|
| /linux-6.3-rc2/drivers/media/pci/tw5864/ |
| A D | Kconfig | 8 multichannel video & audio grabbing and encoding (H.264, MJPEG,
|
| /linux-6.3-rc2/Documentation/locking/ |
| A D | rt-mutex.rst | 65 .. [1] It also can be a transitional state when grabbing the lock
71 waiters. This can happen when grabbing the lock in the slow path.
|
| A D | rt-mutex-design.rst | 317 is used (when applicable) to keep the fast path of grabbing and releasing
387 with what we believe is the best. It walks the PI chain by only grabbing
506 The second case is only applicable for tasks that are grabbing a mutex
536 the grabbing of the wait_lock, the mutex may not have any waiters, thus the
|
| A D | ww-mutex-design.rst | 105 better to avoid grabbing a deadlock avoidance ticket).
328 prevention is obviously overkill, since with grabbing just one lock you can't
|
| /linux-6.3-rc2/drivers/staging/media/av7110/ |
| A D | av7110.c | 1196 memset(budget->grabbing + y * TS_WIDTH, 0x00, TS_WIDTH); in start_ts_capture()
1236 u8 *mem = (u8 *) (budget->grabbing); in vpeirq()
2498 av7110->grabbing = saa7146_vmalloc_build_pgtable(pdev, length, in av7110_attach()
2500 if (!av7110->grabbing) in av7110_attach()
2526 av7110->grabbing = saa7146_vmalloc_build_pgtable(pdev, length, in av7110_attach()
2528 if (!av7110->grabbing) in av7110_attach()
2734 if (av7110->grabbing) in av7110_attach()
2735 saa7146_vfree_destroy_pgtable(pdev, av7110->grabbing, &av7110->pt); in av7110_attach()
2767 saa7146_vfree_destroy_pgtable(saa->pci, av7110->grabbing, &av7110->pt); in av7110_detach()
|
| A D | av7110.h | 185 unsigned char *grabbing; member
|
| /linux-6.3-rc2/Documentation/virt/kvm/x86/ |
| A D | msr.rst | 40 guest has to check version before and after grabbing
87 guest has to check version before and after grabbing
288 this field before and after grabbing time information and make
|
| /linux-6.3-rc2/Documentation/power/ |
| A D | freezing-of-tasks.rst | 218 First of all, grabbing the 'system_transition_mutex' lock to mutually exclude a
224 However, if that is not feasible, and grabbing 'system_transition_mutex' is
|
| /linux-6.3-rc2/Documentation/arm/ |
| A D | vlocks.rst | 196 grabbing most of this text out of the relevant mail thread and writing
|
| /linux-6.3-rc2/Documentation/admin-guide/media/ |
| A D | philips.rst | 76 grabbing with a tool that uses mmap(), you might want to increase if.
|
| /linux-6.3-rc2/Documentation/driver-api/nvdimm/ |
| A D | btt.rst | 185 read is complete. Every writer thread, after grabbing a free block, checks the
|
| /linux-6.3-rc2/scripts/ |
| A D | spelling.txt | 730 grabing||grabbing
|
| /linux-6.3-rc2/Documentation/powerpc/ |
| A D | hvcs.rst | 426 2. To provide network security when grabbing the console it is
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| A D | porting.rst | 157 watch for ->i_mutex-grabbing code that might be used by your ->setattr().
|
| /linux-6.3-rc2/Documentation/kernel-hacking/ |
| A D | locking.rst | 488 grabbing the lock. This is safe, as no-one else can access it until we
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | pin-control.rst | 1140 The result of grabbing this mapping from the device with something like
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | kernel-parameters.txt | 6287 infrastructure grabbing the clock more than
|
Completed in 52 milliseconds