| /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.
|
| H A 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/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/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 | 47 - The configuration must not be propagated to any further processing
49 inside the subdevice to all further processing steps.
|
| H A D | ext-ctrls-image-process.rst | 11 image processing functions. Unlike ``V4L2_CID_IMAGE_SOURCE_CLASS``, the
12 controls in this class affect processing the image, and do not control
|
| /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/drivers/hid/intel-ish-hid/ |
| H A 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/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/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/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/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/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/arch/arm/ |
| H A 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
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-g-mode.rst | 63 processing them and the follower will have to implement those messages.
65 the passthrough mode. See :ref:`cec-core-processing` for details.
138 receive CEC messages for processing. If someone else is already
148 receive CEC messages for processing. In addition it will put the
198 Core message processing details:
202 .. _cec-core-processing:
|
| /linux/drivers/media/rc/img-ir/ |
| H A 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/Documentation/arch/s390/ |
| H A D | cds.rst | 21 processing, shared versus non-shared interrupt processing, DMA versus port
114 that may or may not allow for shared interrupts, DMA processing, etc.. Instead,
242 flag defines the action to be performed for I/O processing
293 -EBUSY The device is currently processing a previous I/O request, or there is
375 or similar needs to be scheduled. During I/O processing the Linux/390 generic
381 next it can reduce I/O processing overhead by chaining a NoOp I/O command
403 can handle lost data on the network to allow for enhanced I/O processing.
450 Sometimes a device driver might need a possibility to stop the processing of
493 In order to terminate all I/O processing at the subchannel, the clear subchannel
|
| /linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 62 takes this approach for much of its grace-period processing and also
64 single-threaded grace-period processing is use of batching, where all
66 next one. In other words, slowing down grace-period processing makes
110 Per-CPU processing
113 Partitioning processing and data over CPUs allows each CPU to take
119 view of this processing and data, in which case something like locking
126 data sets. For example, each CPU does private quiescent-state processing
|