Searched refs:processing (Results 1 – 25 of 425) sorted by relevance
12345678910>>...17
| /linux-6.1.9/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-6.1.9/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-6.1.9/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.
358 sub-device for processing.
410 Inside subdevs, the order of image processing steps will always be from
426 pad for further processing.
452 .. _subdev-image-processing-crop:
454 .. kernel-figure:: subdev-image-processing-crop.svg
455 :alt: subdev-image-processing-crop.svg
458 **Figure 4.5. Image processing in subdevs: simple crop example**
469 .. _subdev-image-processing-scaling-multi-source:
[all …]
|
| 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.
|
| 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-6.1.9/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-6.1.9/Documentation/devicetree/bindings/firmware/ |
| D | intel,ixp4xx-network-processing-engine.yaml | 5 $id: "http://devicetree.org/schemas/firmware/intel,ixp4xx-network-processing-engine.yaml#"
25 - const: intel,ixp4xx-network-processing-engine
65 compatible = "intel,ixp4xx-network-processing-engine";
|
| /linux-6.1.9/tools/perf/Documentation/ |
| D | perf-data.txt | 6 perf-data - Data file related processing
15 Data file related processing.
|
| /linux-6.1.9/drivers/hid/intel-ish-hid/ |
| 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-6.1.9/drivers/staging/media/atomisp/ |
| 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-6.1.9/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-6.1.9/Documentation/devicetree/bindings/media/ |
| D | nxp,dw100.yaml | 13 The Dewarp Engine provides high-performance dewarp processing for the
17 processing, it successfully generates a corrected output image.
|
| D | renesas,vsp1.yaml | 13 The VSP is a video processing engine that supports up-/down-scaling, alpha
14 blending, color space conversion and various other image processing features.
|
| /linux-6.1.9/Documentation/devicetree/bindings/sound/ |
| D | nvidia,tegra210-ope.yaml | 12 sub blocks for data processing.
81 processing-engine@702d8000 {
|
| D | nvidia,tegra210-ahub.yaml | 11 for audio pre-processing, post-processing and a programmable full
113 '^processing-engine@[0-9a-f]+$':
|
| /linux-6.1.9/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-6.1.9/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-devices-xenbus | 30 trigger delayed EOI processing.
37 before delayed EOI processing is triggered for a Xen pv
|
| D | sysfs-driver-hid-ntrig | 34 start processing touch events.
37 start processing touch events.
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/ |
| D | microchip,sparx5.yaml | 17 features such as advanced TCAM-based VLAN and QoS processing
19 TCAM-based frame processing using versatile content aware processor
|
| /linux-6.1.9/Documentation/devicetree/bindings/input/touchscreen/ |
| D | cypress,cy8ctma340.yaml | 88 scanning/processing cycles when the chip is in active mode
94 scanning/processing cycles when the chip is in low-power mode
108 every scanning/processing cycle)
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/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
|
12345678910>>...17