| /linux/drivers/media/pci/ttpci/ |
| H A D | budget-core.c | 68 memset(budget->grabbing, 0x00, budget->buffer_size); in start_ts_capture()
178 u8 *mem = (u8 *) (budget->grabbing); in vpeirq()
518 budget->grabbing = saa7146_vmalloc_build_pgtable(dev->pci, budget->buffer_size, &budget->pt); in ttpci_budget_init()
519 if (budget->grabbing == NULL) { in ttpci_budget_init()
539 saa7146_vfree_destroy_pgtable(dev->pci, budget->grabbing, &budget->pt); in ttpci_budget_init()
570 saa7146_vfree_destroy_pgtable(dev->pci, budget->grabbing, &budget->pt); in ttpci_budget_deinit()
|
| H A D | budget.h | 55 unsigned char *grabbing; member
|
| /linux/drivers/media/pci/tw5864/ |
| H A D | Kconfig | 8 multichannel video & audio grabbing and encoding (H.264, MJPEG,
|
| /linux/Documentation/locking/ |
| H 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.
|
| H 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
|
| H 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/drivers/staging/media/av7110/ |
| H A D | av7110.c | 1184 memset(budget->grabbing + y * TS_WIDTH, 0x00, TS_WIDTH); in start_ts_capture()
1224 u8 *mem = (u8 *)(budget->grabbing); in vpeirq()
2479 av7110->grabbing = saa7146_vmalloc_build_pgtable(pdev, length, in av7110_attach()
2481 if (!av7110->grabbing) in av7110_attach()
2507 av7110->grabbing = saa7146_vmalloc_build_pgtable(pdev, length, in av7110_attach()
2509 if (!av7110->grabbing) in av7110_attach()
2714 if (av7110->grabbing) in av7110_attach()
2715 saa7146_vfree_destroy_pgtable(pdev, av7110->grabbing, &av7110->pt); in av7110_attach()
2748 saa7146_vfree_destroy_pgtable(saa->pci, av7110->grabbing, &av7110->pt); in av7110_detach()
|
| H A D | av7110.h | 182 unsigned char *grabbing; member
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | msr.rst | 40 guest has to check version before and after grabbing
87 guest has to check version before and after grabbing
287 this field before and after grabbing time information and make
|
| /linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 229 First of all, grabbing the 'system_transition_mutex' lock to mutually exclude a
235 However, if that is not feasible, and grabbing 'system_transition_mutex' is
|
| /linux/Documentation/arch/arm/ |
| H A D | vlocks.rst | 196 grabbing most of this text out of the relevant mail thread and writing
|
| /linux/Documentation/admin-guide/media/ |
| H A D | philips.rst | 76 grabbing with a tool that uses mmap(), you might want to increase if.
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | btt.rst | 185 read is complete. Every writer thread, after grabbing a free block, checks the
|
| /linux/scripts/ |
| H A D | spelling.txt | 748 grabing||grabbing
|
| /linux/Documentation/arch/powerpc/ |
| H A D | hvcs.rst | 426 2. To provide network security when grabbing the console it is
|
| /linux/Documentation/kernel-hacking/ |
| H A D | locking.rst | 488 grabbing the lock. This is safe, as no-one else can access it until we
|
| /linux/Documentation/driver-api/ |
| H A D | pin-control.rst | 1140 The result of grabbing this mapping from the device with something like
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.txt | 6791 infrastructure grabbing the clock more than
|