Searched refs:moving (Results 1 – 11 of 11) sorted by relevance
56 unsigned int moving; member95 adata->moving = 1; in avecintc_sync()108 if (adata->moving) in avecintc_set_affinity()200 adata->moving = 0; in complete_irq_moving()305 if (!adata->moving) in avecintc_free_vector()
18 This MUST be done before moving the driver out of staging so that we can22 ready before moving the driver out of staging.
29 interface. It will provide a means of moving a data connection,
33 unsigned moving:1; member
793 stat->moving = r->operand[11] >> 6 & 1; in avc_tuner_status()
1436 struct dma_fence *moving = NULL; in i915_vma_pin_ww() local1481 err = i915_gem_object_get_moving_fence(vma->obj, &moving); in i915_vma_pin_ww()1485 dma_fence_work_chain(&work->base, moving); in i915_vma_pin_ww()1603 if (moving) in i915_vma_pin_ww()1604 dma_fence_put(moving); in i915_vma_pin_ww()
22 wear leveling by means of moving data from eraseblock with low erase
14 The numberspace issue is the same as to why irq is moving away from irq
81 moving towards separating connector handling from display controllers
310 moving frequently used data to a smaller, higher performance
430 * list. This is achieved by simply moving our "next" pointer into
Completed in 23 milliseconds