| /linux-6.12.1/drivers/vdpa/vdpa_sim/ |
| D | vdpa_sim_blk.c | 113 size_t pushed = 0, to_pull, to_push; in vdpasim_blk_handle_req() local
190 pushed += bytes; in vdpasim_blk_handle_req()
225 pushed += bytes; in vdpasim_blk_handle_req()
303 if (to_push - pushed > 0) in vdpasim_blk_handle_req()
304 vringh_kiov_advance(&vq->in_iov, to_push - pushed); in vdpasim_blk_handle_req()
311 pushed += bytes; in vdpasim_blk_handle_req()
319 vringh_complete_iotlb(&vq->vring, vq->head, pushed); in vdpasim_blk_handle_req()
|
| /linux-6.12.1/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_mbx.c | 219 if (!mbx->pushed) in fm10k_mbx_pushed_tail_len()
302 len += mbx->pushed; in fm10k_mbx_validate_msg_size()
438 end = fm10k_fifo_tail_offset(fifo, mbx->pushed); in fm10k_mbx_read_copy()
479 len = fm10k_fifo_unused(fifo) - mbx->pushed; in fm10k_mbx_push_tail()
499 mbx->pushed += len; in fm10k_mbx_push_tail()
503 len && (mbx->pushed >= len); in fm10k_mbx_push_tail()
506 mbx->pushed -= len; in fm10k_mbx_push_tail()
642 u16 offset = fm10k_fifo_tail_offset(fifo, mbx->pushed) - len; in fm10k_mbx_verify_remote_crc()
720 memmove(fifo->buffer, fifo->buffer + fifo->tail, mbx->pushed << 2); in fm10k_mbx_dequeue_rx()
1081 mbx->pushed = 0; in fm10k_mbx_reset_work()
[all …]
|
| D | fm10k_mbx.h | 267 u16 head, head_len, pushed; member
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-adc-hi8435 | 17 this value then the threshold falling event is pushed.
36 this value then the threshold rising event is pushed.
|
| D | sysfs-bus-iio-accel-bmc150 | 6 which sets driver in a mode, where data is pushed to the buffer
|
| D | sysfs-bus-iio-gyro-bmg160 | 6 which sets driver in a mode, where data is pushed to the buffer
|
| D | sysfs-driver-intc_sar | 42 by a single space. This information can then be pushed to a
|
| /linux-6.12.1/net/mpls/ |
| D | Kconfig | 23 that have had MPLS stack entries pushed onto them and thus
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | shstk.rst | 134 When a signal happens, the old pre-signal state is pushed on the stack. When
135 shadow stack is enabled, the shadow stack specific state is pushed onto the
136 shadow stack. Today this is only the old SSP (shadow stack pointer), pushed
|
| /linux-6.12.1/drivers/iio/buffer/ |
| D | Kconfig | 11 usage. That is, those where the data is pushed to the consumer.
|
| /linux-6.12.1/drivers/platform/surface/ |
| D | surfacepro3_button.c | 70 unsigned long pushed; member
|
| /linux-6.12.1/drivers/acpi/ |
| D | button.c | 174 unsigned long pushed; member
468 event, ++button->pushed); in acpi_button_notify()
|
| /linux-6.12.1/arch/m68k/fpsp040/ |
| D | x_fline.S | 35 | the equate is valid only after a 'link a6' has pushed one more
|
| D | fpsp.h | 66 | a second fsave frame can be pushed onto the stack and the
|
| /linux-6.12.1/tools/include/uapi/ |
| D | README | 47 was pushed back on from the kernel side, when tooling modified the
|
| /linux-6.12.1/Documentation/misc-devices/ |
| D | bh1770glc.rst | 37 interrupts the delayed work is pushed forward. So, when proximity level goes
|
| /linux-6.12.1/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 67 queues looking for descriptors that have been pushed
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | generic-counter.rst | 513 pushed to userspace.
538 Extension 0, and Count 7 -- the data returned for each is pushed to a
|
| /linux-6.12.1/Documentation/hid/ |
| D | hid-sensor.rst | 234 These reports are pushed using misc device interface in a FIFO order::
|
| /linux-6.12.1/drivers/atm/ |
| D | eni.c | 148 backlogged = 0,rx_enqueued = 0,rx_dequeued = 0,pushed = 0,submitted = 0, variable
767 pushed++; in dequeue_rx()
1465 rx_enqueued,rx_dequeued,putting,pushed);
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | journalling.rst | 62 buffer you now know is now longer required to be pushed back on the
|
| /linux-6.12.1/Documentation/trace/ |
| D | ring-buffer-design.rst | 373 the head page will be pushed ahead one. If the buffer is in producer/consumer
715 page. If this fails, a nested write pushed it forward, the current write
|
| /linux-6.12.1/Documentation/sound/designs/ |
| D | timestamping.rst | 62 are pushed on a link. The link time can be directly measured if
|
| /linux-6.12.1/Documentation/networking/ |
| D | gtp.rst | 153 extended it with new features and finally pushed all of us to get it
|
| /linux-6.12.1/tools/testing/selftests/bpf/ |
| D | README.rst | 195 has been pushed to llvm 10.x release branch and will be
|