Home
last modified time | relevance | path

Searched +full:pre +full:- +full:processing (Results 1 – 25 of 46) sorted by relevance

12

/Documentation/infiniband/
Dtag_matching.rst5 The MPI standard defines a set of rules, known as tag-matching, for matching
10 * User tag - wild card may be specified by the receiver
15 message envelopes may match, the pair that includes the earliest posted-send
16 and the earliest posted-receive is the pair that must be used to satisfy the
31 1. The Eager protocol- the complete message is sent when the send is
35 2. The Rendezvous Protocol - the sender sends the tag-matching header,
51 pre-posted receive for this arriving message, it is passed to the software and
53 including rendezvous processing, if appropriate, delivering the data to the
54 specified receive buffer. This allows overlapping receive-side MPI tag
57 When a receive-message is posted, the communication library will first check
[all …]
/Documentation/admin-guide/media/
Dimx.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
9 The Freescale i.MX5/6 contains an Image Processing Unit (IPU), which
15 - Image DMA Controller (IDMAC)
16 - Camera Serial Interface (CSI)
17 - Image Converter (IC)
18 - Sensor Multi-FIFO Controller (SMFC)
19 - Image Rotator (IRT)
20 - Video De-Interlacing or Combining Block (VDIC)
26 re-ordering (for example UYVY to YUYV) within the same colorspace, and
[all …]
Dipu3.rst1 .. SPDX-License-Identifier: GPL-2.0
6 Intel Image Processing Unit 3 (IPU3) Imaging Unit (ImgU) driver
14 This file documents the Intel IPU3 (3rd generation Image Processing Unit)
24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2*
27 The Imaging Unit (ImgU) is responsible for processing images captured
36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device
38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers.
44 interface to the user space. There is a video node for each CSI-2 receiver,
47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2
48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed
[all …]
/Documentation/devicetree/bindings/input/
Dmicrochip,qt1050.txt1 Microchip AT42QT1050 Five-channel Touch Sensor IC
4 one to five keys, dependent on mode. The QT1050 includes all signal processing
11 - compatible: Must be "microchip,qt1050"
12 - reg: The I2C address of the device
13 - interrupts: The sink for the touchpad's IRQ output,
14 see ../interrupt-controller/interrupts.txt
17 - wakeup-source: touch keys can be used as a wakeup source
19 Each button (key) is represented as a sub-node:
25 - linux,code: Keycode to emit.
26 - reg: The key number. Valid values: 0, 1, 2, 3, 4.
[all …]
/Documentation/devicetree/bindings/display/
Damlogic,meson-vpu.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/display/amlogic,meson-vpu.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Neil Armstrong <narmstrong@baylibre.com>
17 DMC|---------------VPU (Video Processing Unit)----------------|------HHI------|
19 D |-------| |----| | | | | HDMI PLL |
20 D | vd2 | VIU | | Video Post | | Video Encoders |<---|-----VCLK |
21 R |-------| |----| Processing | | | | |
22 | osd2 | | | |---| Enci ----------|----|-----VDAC------|
[all …]
/Documentation/devicetree/bindings/sound/
Dnvidia,tegra210-ahub.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/nvidia,tegra210-ahub.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 for audio pre-processing, post-processing and a programmable full
17 - Jon Hunter <jonathanh@nvidia.com>
18 - Sameer Pujar <spujar@nvidia.com>
22 pattern: "^ahub@[0-9a-f]*$"
26 - enum:
27 - nvidia,tegra210-ahub
[all …]
/Documentation/devicetree/bindings/media/
Dti,cal.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benoit Parrot <bparrot@ti.com>
12 description: |-
15 processing capability to connect CSI2 image-sensor modules to the
21 Documentation/devicetree/bindings/media/video-interfaces.txt.
27 - ti,dra72-cal
28 # for DRA72 controllers pre ES2.0
29 - ti,dra72-pre-es2-cal
[all …]
/Documentation/devicetree/bindings/dsp/
Dfsl,dsp.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Daniel Baluta <daniel.baluta@nxp.com>
14 advanced pre- and post- audio processing.
19 - fsl,imx8qxp-dsp
20 - fsl,imx8qm-dsp
21 - fsl,imx8mp-dsp
28 - description: ipg clock
29 - description: ocram clock
[all …]
/Documentation/driver-api/media/
Dcamera-sensor.rst1 .. SPDX-License-Identifier: GPL-2.0
6 CSI-2
7 -----
12 ---------------
23 elsewhere. Therefore only the pre-determined frequencies are configurable by the
27 ----------
36 processing pipeline as one or more sub-devices with different cropping and
55 ----------------------------
80 pixel rate is specified by ``V4L2_CID_PIXEL_RATE`` in the same sub-device. The
83 Register list based drivers need to implement read-only sub-device nodes for the
[all …]
/Documentation/sphinx/
Dmaintainers_include.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
65 line = unicode(line, 'utf-8')
69 # Ensure a blank line following the last "|"-prefixed line.
[all …]
/Documentation/driver-api/mmc/
Dmmc-async-req.rst11 pre-fetch makes the cache overhead relatively significant. If the DMA
15 The intention of non-blocking (asynchronous) MMC requests is to minimize the
19 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
26 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
40 https://wiki.linaro.org/WorkingGroups/Kernel/Specs/StoragePerfMMC-async-req
48 truly non-blocking. If there is an ongoing async request it waits
56 There are two optional members in the mmc_host_ops -- pre_req() and
57 post_req() -- that the host driver may implement in order to move work
77 if (is_first_req && req->size > threshold)
90 dma_issue_pending(req->dma_desc);
[all …]
/Documentation/sound/soc/
Ddapm.rst11 such, can easily co-exist with the other PM systems.
60 Audio DAPM widgets fall into a number of types:-
104 Pre
105 Special PRE widget (exec before all others)
111 DSP internal scheduler that schedules component/pipeline processing
114 Widget that performs an audio processing effect.
127 (Widgets are defined in include/sound/soc-dapm.h)
130 There are convenience macros defined in soc-dapm.h that can be used to quickly
138 ---------------------
144 Stream widgets have the following format:-
[all …]
/Documentation/driver-api/nfc/
Dnfc-hci.rst5 - Author: Eric Lapuyade, Samuel Ortiz
6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
9 -------
12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
17 ---
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
35 --------------------------
41 In case the chip supports pre-opened gates and pseudo-static pipes, the driver
45 -------------------
[all …]
/Documentation/RCU/
Drcubarrier.rst8 RCU (read-copy update) is a synchronization mechanism that can be thought
9 of as a replacement for read-writer locking (among other things), but with
10 very low-overhead readers that are immune to deadlock, priority inversion,
11 and unbounded latency. RCU read-side critical sections are delimited
12 by rcu_read_lock() and rcu_read_unlock(), which, in non-CONFIG_PREEMPT
18 pre-existing readers have finished. These old versions are needed because
20 rather expensive, and RCU is thus best suited for read-mostly situations.
25 pre-existing readers have completed. An updater wishing to delete an
33 But the above code cannot be used in IRQ context -- the call_rcu()
35 rcu_head struct placed within the RCU-protected data structure and
[all …]
/Documentation/vm/
Dslub.rst20 slabs that have data in them. See "slabinfo -h" for more options when
24 gcc -o slabinfo tools/vm/slabinfo.c
32 -------------------------------------------
37 slub_debug=<Debug-Options>
40 slub_debug=<Debug-Options>,<slab name1>,<slab name2>,...
60 - Switch all debugging off (useful if the kernel is
76 slub_debug=P,kmalloc-*,dentry
95 slub_debug=Z,dentry;U,kmalloc-*
100 with "-" as options::
102 slub_debug=FZ;-,zs_handle,zspage
[all …]
/Documentation/block/
Dbiodoc.rst13 - Jens Axboe <jens.axboe@oracle.com>
14 - Suparna Bhattacharya <suparna@in.ibm.com>
19 - Nick Piggin <npiggin@kernel.dk>
34 - Jens Axboe <jens.axboe@oracle.com>
43 - Christoph Hellwig <hch@infradead.org>
44 - Arjan van de Ven <arjanv@redhat.com>
45 - Randy Dunlap <rdunlap@xenotime.net>
46 - Andre Hedrick <andre@linux-ide.org>
49 while it was still work-in-progress:
51 - David S. Miller <davem@redhat.com>
[all …]
/Documentation/sparc/oradax/
Ddax-hv-api.txt3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
13 …The following APIs provide access via the Hypervisor to hardware assisted data processing function…
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
[all …]
/Documentation/filesystems/
Dcoda.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
35 level filesystem code needed for the operation of the Coda file sys-
124 leads to an almost natural environment for implementing a kernel-level
149 manager in Windows 95. The VFS is responsible for partial processing
153 pre-processing, the VFS starts invoking exported routines in the FS
154 driver. This is the point where the FS specific processing of the
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
220 memory for the request. Since the data buffer is re-used to hold the
[all …]
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst13 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier
14 third RCU-bh flavor having been implemented in terms of the other two.
38 RCU-preempt Expedited Grace Periods
41 ``CONFIG_PREEMPT=y`` kernels implement RCU-preempt.
42 The overall flow of the handling of a given CPU by an RCU-preempt
45 .. kernel-figure:: ExpRCUFlow.svg
59 can check to see if the CPU is currently running in an RCU read-side
63 invocation will provide the needed quiescent-state report.
64 This flag-setting avoids the previous forced preemption of all
65 CPUs that might have RCU read-side critical sections.
[all …]
/Documentation/target/
Dtcmu-design.rst19 2) Writing a user pass-through handler
29 TCM is another name for LIO, an in-kernel iSCSI target (server).
38 built-in modules are implemented entirely as kernel code.
41 ----------
52 use case that other non-kernel target solutions, such as tgt, are able
55 in these non-traditional networked storage systems, while still only
65 kernel, another approach is to create a userspace pass-through
70 --------
83 ------------------
85 - Good performance: high throughput, low latency
[all …]
/Documentation/userspace-api/media/v4l/
Dcontrol.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 Devices typically have a number of user-settable controls such as
21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
22 :ref:`control-id`. The ID is used when querying the attributes of a
27 the user is supposed to understand. When the purpose is non-intuitive
28 the driver writer should provide a user manual, a user interface plug-in
57 .. _control-id:
127 Whiteness for grey-scale devices. This is a synonym for
152 .. _v4l2-power-line-frequency:
193 .. _v4l2-colorfx:
[all …]
/Documentation/power/
Dpci.rst13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
53 to put the device that sent it into the full-power state. However, the PCI Bus
68 Thus in many situations both the native and the platform-based power management
72 --------------------------------
[all …]
/Documentation/core-api/
Dcachetlb.rst25 virtual-->physical address translations obtained from the software
59 modifications for the address space 'vma->vm_mm' in the range
60 'start' to 'end-1' will be visible to the cpu. That is, after
62 virtual addresses in the range 'start' to 'end-1'.
78 address space is available via vma->vm_mm. Also, one may
79 test (vma->vm_flags & VM_EXEC) to see if this region is
81 split-tlb type setups).
84 page table modification for address space 'vma->vm_mm' for
87 'vma->vm_mm' for virtual address 'addr'.
89 This is used primarily during fault processing.
[all …]
/Documentation/scsi/
Dscsi_eh.rst1 .. SPDX-License-Identifier: GPL-2.0
14 [1-1] struct scsi_cmnd
15 [1-2] How do scmd's get completed?
16 [1-2-1] Completing a scmd w/ scsi_done
17 [1-2-2] Completing a scmd w/ timeout
18 [1-3] How EH takes over
20 [2-1] EH through fine-grained callbacks
21 [2-1-1] Overview
22 [2-1-2] Flow of scmds through EH
23 [2-1-3] Flow of control
[all …]
/Documentation/kbuild/
Dmakefiles.rst12 --- 3.1 Goal definitions
13 --- 3.2 Built-in object goals - obj-y
14 --- 3.3 Loadable module goals - obj-m
15 --- 3.4 Objects which export symbols
16 --- 3.5 Library file goals - lib-y
17 --- 3.6 Descending down in directories
18 --- 3.7 Compilation flags
19 --- 3.8 <deleted>
20 --- 3.9 Dependency tracking
21 --- 3.10 Special Rules
[all …]

12