Searched refs:processing (Results 1 – 25 of 365) sorted by relevance
12345678910>>...15
/Linux-v5.10/drivers/staging/media/ipu3/ |
D | Kconfig | 11 This is the Video4Linux2 driver for Intel IPU3 image processing unit, 12 found in Intel Skylake and Kaby Lake SoCs and used for processing
|
/Linux-v5.10/drivers/net/ethernet/freescale/fman/ |
D | Kconfig | 22 internal resource leak thus stopping further packet processing. 27 stall further packet processing. The issue can occur with any 38 likelihood of stalled FMAN packet processing, especially under
|
/Linux-v5.10/Documentation/userspace-api/media/v4l/ |
D | libv4l-introduction.rst | 56 processing functions to improve webcam video quality. The video 57 processing is split in to 2 parts: libv4lconvert/control and 58 libv4lconvert/processing. 61 control the video processing functions made available by 62 libv4lconvert/processing. These controls are stored application wide 65 libv4lconvert/processing offers the actual video processing
|
D | dev-subdev.rst | 50 sensors and image processing hardware implement identical functions, 102 the video sensor and the host image processing hardware. 356 sub-device for processing. 408 Inside subdevs, the order of image processing steps will always be from 424 pad for further processing. 450 .. _subdev-image-processing-crop: 452 .. kernel-figure:: subdev-image-processing-crop.svg 453 :alt: subdev-image-processing-crop.svg 456 **Figure 4.5. Image processing in subdevs: simple crop example** 467 .. _subdev-image-processing-scaling-multi-source: [all …]
|
D | v4l2-selection-flags.rst | 40 - The configuration must not be propagated to any further processing 42 inside the subdevice to all further processing steps.
|
D | ext-ctrls-image-process.rst | 10 image processing functions. Unlike ``V4L2_CID_IMAGE_SOURCE_CLASS``, the 11 controls in this class affect processing the image, and do not control
|
/Linux-v5.10/drivers/iio/common/hid-sensors/ |
D | Kconfig | 13 HID sensor common processing for attributes and IIO triggers. 15 HID sensor drivers, this module contains processing for those
|
/Linux-v5.10/tools/perf/Documentation/ |
D | perf-data.txt | 6 perf-data - Data file related processing 15 Data file related processing.
|
D | perf-inject.txt | 16 point the processing code can inject other events into the event stream - in 21 needs userspace processing to augment the events stream with additional
|
/Linux-v5.10/drivers/hid/intel-ish-hid/ |
D | Kconfig | 11 sensor polling and algorithm processing to a dedicated low power 25 sensor polling and algorithm processing to a dedicated low power
|
/Linux-v5.10/Documentation/devicetree/bindings/input/touchscreen/ |
D | cyttsp.txt | 28 scanning/processing cycles when the chip is in active mode. 31 scanning/processing cycles when the chip is in low-power mode. 40 scanning/processing cycle).
|
/Linux-v5.10/Documentation/hid/ |
D | hid-sensor.rst | 52 - Individual sensor processing part (sensor drivers) 65 function will be called. So an accelerometer processing driver can register 68 The core driver provides a set of APIs which can be used by the processing 72 Individual sensor processing part (sensor drivers) 75 The processing driver will use an interface provided by the core driver to parse 85 Each processing driver can use this structure to set some callbacks. 115 A processing driver can look for some field of interest and check if it exists
|
/Linux-v5.10/Documentation/usb/ |
D | ohci.rst | 30 to overhead in IRQ processing. When interrupt transfers are queued, those 32 work on while the OS is getting around to the relevant IRQ processing.
|
/Linux-v5.10/Documentation/ABI/testing/ |
D | sysfs-class-net-queues | 7 Receive Packet Steering packet processing flow for this 41 Transmit Packet Steering packet processing flow for this 51 into the Transmit Packet Steering packet processing flow for this
|
D | sysfs-driver-hid-ntrig | 34 start processing touch events. 37 start processing touch events.
|
/Linux-v5.10/Documentation/devicetree/bindings/display/bridge/ |
D | megachips-stdpxxxx-ge-b850v3-fw.txt | 5 The video processing pipeline on the second output on the GE B850v3: 15 The hardware do not provide control over the video processing pipeline, as the
|
/Linux-v5.10/Documentation/driver-api/ |
D | sync_file.rst | 19 driver that issued the fence is not using/processing the buffer anymore, so it 34 related to a buffer that the driver is processing or is going to process, so 36 dma_fence_signal(), when it has finished using (or processing) that buffer.
|
/Linux-v5.10/Documentation/driver-api/iio/ |
D | triggered-buffers.rst | 57 function. It should do as little processing as possible, because it runs in 63 processing takes place here. It usually reads data from the device and
|
/Linux-v5.10/drivers/dma/ |
D | sun4i-dma.c | 138 struct sun4i_dma_promise *processing; member 339 if (vchan->processing) { in __execute_vchan_pending() 369 vchan->processing = promise; in __execute_vchan_pending() 894 vchan->processing = NULL; in sun4i_dma_terminate_all() 1045 list_del(&vchan->processing->list); in sun4i_dma_interrupt() 1046 list_add_tail(&vchan->processing->list, in sun4i_dma_interrupt() 1064 vchan->processing = promise; in sun4i_dma_interrupt() 1068 vchan->processing = NULL; in sun4i_dma_interrupt()
|
/Linux-v5.10/Documentation/networking/devlink/ |
D | devlink-trap.rst | 12 kernel (i.e., the CPU) for processing. 15 IGMP membership reports to the kernel for processing by the bridge module. 16 Without processing such packets, the bridge module could never populate its 25 The fundamental ability of sending certain packets to the kernel for processing 251 - Traps packets dropped during processing of ingress flow action drop 254 - Traps packets dropped during processing of egress flow action drop 402 - Traps packets sampled during processing of flow action sample (e.g., via 406 - Traps packets logged during processing of flow action trap (e.g., via 525 ACL processing 575 ACL processing [all …]
|
/Linux-v5.10/Documentation/networking/ |
D | scaling.rst | 29 queues to distribute processing among CPUs. The NIC distributes packets by 82 processing takes place in receive interrupt handling, it is advantageous 93 interrupt processing forms a bottleneck. Spreading load between CPUs 115 interrupt handler, RPS selects the CPU to perform protocol processing 117 on the desired CPU’s backlog queue and waking up the CPU for processing. 141 RPS may enqueue packets for processing. For each received packet, 143 of the list. The indexed CPU is the target for processing the packet, 147 processing on the remote CPU, and any queued packets are then processed 186 RPS scales kernel receive processing across CPUs without introducing 254 kernel processing of packets to the CPU where the application thread [all …]
|
/Linux-v5.10/Documentation/driver-api/gpio/ |
D | board.rst | 207 processing. If yes, a bitmap is passed over get/set array functions directly 210 In order to qualify for fast bitmap processing, the array must meet the 217 Otherwise fast bitmap processing path is not used in order to avoid consecutive 221 If the array applies for fast bitmap processing path, pins which belong to 225 output processing.
|
/Linux-v5.10/drivers/media/rc/img-ir/ |
D | Kconfig | 18 processing power than using hardware decode, but can be useful for 26 signals in hardware. This is more reliable, consumes less processing
|
/Linux-v5.10/Documentation/admin-guide/media/ |
D | qcom_camss.rst | 38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing 40 interface feeds the input data to the image processing pipeline. The image 41 processing pipeline contains also a scale and crop module at the end. Three 42 RDI (Raw Dump Interface) input interfaces bypass the image processing
|
/Linux-v5.10/Documentation/arm/ |
D | interrupts.rst | 33 exclusive of each other - if you're processing one interrupt from the 35 finish processing before you can service the new interrupt. Eg, an 112 need to leave the hardware IRQ enabled while processing it, and queueing 113 further IRQ events should the IRQ happen again while processing. The
|
12345678910>>...15