| /linux/Documentation/admin-guide/media/ |
| H A D | raspberrypi-pisp-be.rst | 11 image data from DRAM memory and performs image processing as specified by the
23 The full image processing pipeline, which involves capturing RAW Bayer data from
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
50 processing.
78 To realize HDR (high dynamic range) image processing the image stitching and
94 parameters that define the desired image processing to be performed by the ISP.
|
| /linux/Documentation/networking/ |
| H A D | napi.rst | 18 NAPI processing usually happens in the software interrupt context,
20 for NAPI processing.
23 of event (packet Rx and Tx) processing.
66 Rx packets. Rx processing is usually much more expensive.
68 In other words for Rx processing the ``budget`` argument limits how many
71 skb Tx processing should happen regardless of the ``budget``, but if
85 If event processing has been completed (all outstanding packets
156 mapped to queues and interrupts. NAPI is primarily a polling/processing
219 want to be interrupted until they finish processing a request or a batch
239 threads rather than software IRQ context for NAPI processing.
|
| H A D | scaling.rst | 29 queues to distribute processing among CPUs. The NIC distributes packets by
97 processing takes place in receive interrupt handling, it is advantageous
108 interrupt processing forms a bottleneck. Spreading load between CPUs
172 interrupt handler, RPS selects the CPU to perform protocol processing
174 on the desired CPU’s backlog queue and waking up the CPU for processing.
198 RPS may enqueue packets for processing. For each received packet,
200 of the list. The indexed CPU is the target for processing the packet,
204 processing on the remote CPU, and any queued packets are then processed
243 RPS scales kernel receive processing across CPUs without introducing
311 kernel processing of packets to the CPU where the application thread
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| H A D | v4l2-selection-flags.rst | 46 - The configuration must not be propagated to any further processing
48 inside the subdevice to all further processing steps.
|
| H A 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/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 23 internal resource leak thus stopping further packet processing.
28 stall further packet processing. The issue can occur with any
39 likelihood of stalled FMAN packet processing, especially under
|
| /linux/drivers/staging/media/ipu3/ |
| H A 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/drivers/staging/media/atomisp/ |
| H A D | notes.txt | 14 The actual processing pipeline is made by loading one or more programs,
27 Since getting a picture requires multiple processing steps,
29 on the ISP can do multiple processing steps in a single pipeline
|
| /linux/drivers/iio/common/hid-sensors/ |
| H A D | Kconfig | 13 HID sensor common processing for attributes and IIO triggers.
15 HID sensor drivers, this module contains processing for those
|
| /linux/Documentation/hid/ |
| H A 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/tools/perf/Documentation/ |
| H A D | perf-data.txt | 6 perf-data - Data file related processing
15 Data file related processing.
|
| H A 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
33 and skip SAMPLE processing.
|
| /linux/drivers/hid/intel-ish-hid/ |
| H A D | Kconfig | 12 sensor polling and algorithm processing to a dedicated low power
26 sensor polling and algorithm processing to a dedicated low power
|
| /linux/Documentation/usb/ |
| H A 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/Documentation/driver-api/ |
| H A 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/Documentation/driver-api/gpio/ |
| H A D | board.rst | 198 processing. If yes, a bitmap is passed over get/set array functions directly
201 In order to qualify for fast bitmap processing, the array must meet the
208 Otherwise fast bitmap processing path is not used in order to avoid consecutive
212 If the array applies for fast bitmap processing path, pins which belong to
216 output processing.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-xenbus | 30 trigger delayed EOI processing.
37 before delayed EOI processing is triggered for a Xen pv
|
| H A 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
|
| H A D | sysfs-driver-hid-ntrig | 34 start processing touch events.
37 start processing touch events.
|
| /linux/Documentation/devicetree/bindings/display/bridge/ |
| H A 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/Documentation/networking/devlink/ |
| H A 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
545 ACL processing
595 ACL processing
[all …]
|
| /linux/Documentation/driver-api/iio/ |
| H A 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/Documentation/bpf/ |
| H A D | map_cpumap.rst | 21 on the remote CPU. This allows an XDP program to split its processing across
23 the packets) needs to do minimal packet processing and the remote CPU (to which
24 the packet is directed) can afford to spend more cycles processing the frame. The
|
| /linux/Documentation/core-api/ |
| H A D | memory-hotplug.rst | 78 NOTIFY_DONE and NOTIFY_OK have no effect on the further processing.
82 further processing of the notification queue.
84 NOTIFY_STOP stops further processing of the notification queue.
|