Home
last modified time | relevance | path

Searched full:processing (Results 1 – 25 of 4155) sorted by relevance

12345678910>>...167

/OK3568_Linux_fs/external/camera_engine_rkaiq/rkaiq/include/algos/
H A Drk_aiq_algo_des.h36 * after |pre_process| or |processing|. That means the configs can't be
40 * We separate the whole process to 3 steps: pre-process, processing and
42 * call processing, then post-process at last.
44 * to solve the dependancy. It collects all the dependancy before processing.
45 * 4) processing
163 } proc; //for pre/processing/post function
165 void* reserverd; //transfer whatever used by prepare/pre/processing/post
177 XCamReturn (*processing)(const RkAiqAlgoCom* inparams, RkAiqAlgoResCom* outparams); member
/OK3568_Linux_fs/kernel/Documentation/gpu/
H A Dmeson.rst2 drm/meson AmLogic Meson Video Processing Unit
6 :doc: Video Processing Unit
8 Video Processing Unit
16 DMC|---------------VPU (Video Processing Unit)----------------|------HHI------|
20 R |-------| |----| Processing | | | | |
33 Video Post Processing
37 :doc: Video Post Processing
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Ddev-subdev.rst50 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 …]
H A Dlibv4l-introduction.rst56 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
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/firmware/
H A Dintel,ixp4xx-network-processing-engine.yaml5 $id: "http://devicetree.org/schemas/firmware/intel,ixp4xx-network-processing-engine.yaml#"
8 title: Intel IXP4xx Network Processing Engine
14 On the IXP4xx SoCs, the Network Processing Engine (NPE) is a small
25 - const: intel,ixp4xx-network-processing-engine
42 compatible = "intel,ixp4xx-network-processing-engine";
/OK3568_Linux_fs/kernel/drivers/net/wireless/rockchip_wlan/cywdhd/bcmdhd/
H A Ddhd_linux_priv.h232 /* Number of times NAPI processing got scheduled */
234 /* Number of times NAPI processing ran on each available core */
250 /* Number of times TX processing run on each core */
257 /* TODO: Need to see if batch processing is really required in case of TX
258 * processing. In case of RX the Dongle can send a bunch of rx completions,
263 * napi processing - copies the pend_queue into a local queue and works
278 * can be lockless. The concept is borrowed as is from RX processing
290 * For now, the processing tasklet will also direcly operate on this
302 /* Tasklet context from which the DHD's TX processing happens */
306 * Consumer Histogram - NAPI RX Packet processing
[all …]
/OK3568_Linux_fs/kernel/drivers/net/wireless/rockchip_wlan/infineon/bcmdhd/
H A Ddhd_linux_priv.h232 /* Number of times NAPI processing got scheduled */
234 /* Number of times NAPI processing ran on each available core */
250 /* Number of times TX processing run on each core */
257 /* TODO: Need to see if batch processing is really required in case of TX
258 * processing. In case of RX the Dongle can send a bunch of rx completions,
263 * napi processing - copies the pend_queue into a local queue and works
278 * can be lockless. The concept is borrowed as is from RX processing
290 * For now, the processing tasklet will also direcly operate on this
302 /* Tasklet context from which the DHD's TX processing happens */
306 * Consumer Histogram - NAPI RX Packet processing
[all …]
/OK3568_Linux_fs/external/rkwifibt/drivers/infineon/
H A Ddhd_linux_priv.h232 /* Number of times NAPI processing got scheduled */
234 /* Number of times NAPI processing ran on each available core */
250 /* Number of times TX processing run on each core */
257 /* TODO: Need to see if batch processing is really required in case of TX
258 * processing. In case of RX the Dongle can send a bunch of rx completions,
263 * napi processing - copies the pend_queue into a local queue and works
278 * can be lockless. The concept is borrowed as is from RX processing
290 * For now, the processing tasklet will also direcly operate on this
302 /* Tasklet context from which the DHD's TX processing happens */
306 * Consumer Histogram - NAPI RX Packet processing
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/orm/management/commands/
H A Dlsupdates.py112 # We know we're only processing one entry, so we reference it here
119 logger.info("Processing releases")
131 logger.info("Processing layers")
159 logger.info("Processing layer versions")
193 logger.info("Processing layer version dependencies")
226 logger.info("Processing distro information")
241 logger.info("Processing machine information")
256 logger.info("Processing recipe information")
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dscaling.rst29 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 …]
/OK3568_Linux_fs/kernel/drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd/
H A Ddhd_linux_priv.h259 /* Number of times NAPI processing got scheduled */
264 /* Number of times NAPI processing ran on each available core */
280 /* Number of times TX processing run on each core */
287 /* TODO: Need to see if batch processing is really required in case of TX
288 * processing. In case of RX the Dongle can send a bunch of rx completions,
293 * napi processing - copies the pend_queue into a local queue and works
308 * can be lockless. The concept is borrowed as is from RX processing
320 * For now, the processing tasklet will also direcly operate on this
331 /* Tasklet context from which the DHD's TX processing happens */
335 * Consumer Histogram - NAPI RX Packet processing
[all …]
/OK3568_Linux_fs/external/rkwifibt/drivers/bcmdhd/
H A Ddhd_linux_priv.h257 /* Number of times NAPI processing got scheduled */
262 /* Number of times NAPI processing ran on each available core */
278 /* Number of times TX processing run on each core */
285 /* TODO: Need to see if batch processing is really required in case of TX
286 * processing. In case of RX the Dongle can send a bunch of rx completions,
291 * napi processing - copies the pend_queue into a local queue and works
306 * can be lockless. The concept is borrowed as is from RX processing
318 * For now, the processing tasklet will also direcly operate on this
329 /* Tasklet context from which the DHD's TX processing happens */
333 * Consumer Histogram - NAPI RX Packet processing
[all …]
/OK3568_Linux_fs/external/camera_engine_rkaiq/rkaiq/aiq_core/algo_handlers/
H A DRkAiqAorbHandle.cpp66 XCamReturn RkAiqAorbHandleInt::processing() { in processing() function in RkCam::RkAiqAorbHandleInt
78 ret = RkAiqHandle::processing(); in processing()
80 RKAIQCORE_CHECK_RET(ret, "aorb handle processing failed"); in processing()
89 ret = des->processing(mProcInParam, mProcOutParam); in processing()
90 RKAIQCORE_CHECK_RET(ret, "aorb algo processing failed"); in processing()
H A DRkAiqAwdrHandle.cpp80 XCamReturn RkAiqAwdrHandleInt::processing() { in processing() function in RkCam::RkAiqAwdrHandleInt
91 ret = RkAiqHandle::processing(); in processing()
93 RKAIQCORE_CHECK_RET(ret, "awdr handle processing failed"); in processing()
97 ret = des->processing(mProcInParam, mProcOutParam); in processing()
98 RKAIQCORE_CHECK_RET(ret, "awdr algo processing failed"); in processing()
H A DRkAiqAmdHandle.cpp90 XCamReturn RkAiqAmdHandleInt::processing() { in processing() function in RkCam::RkAiqAmdHandleInt
108 ret = RkAiqHandle::processing(); in processing()
110 RKAIQCORE_CHECK_RET(ret, "amd handle processing failed"); in processing()
118 ret = des->processing(mProcInParam, (RkAiqAlgoResCom*)amd_proc_res_int); in processing()
119 RKAIQCORE_CHECK_RET(ret, "amd algo processing failed"); in processing()
/OK3568_Linux_fs/external/security/rk_tee_user/v2/client_export/public/
H A Dpkcs11_ta.h283 * PKCS11_CMD_ENCRYPT_INIT - Initialize encryption processing
284 * PKCS11_CMD_DECRYPT_INIT - Initialize decryption processing
300 * PKCS11_CMD_ENCRYPT_UPDATE - Update encryption processing
301 * PKCS11_CMD_DECRYPT_UPDATE - Update decryption processing
315 * PKCS11_CMD_ENCRYPT_FINAL - Finalize encryption processing
316 * PKCS11_CMD_DECRYPT_FINAL - Finalize decryption processing
330 * processing
332 * processing
347 * processing
349 * processing
[all …]
/OK3568_Linux_fs/buildroot/package/gnuradio/
H A DConfig.in33 toolkit that provides signal processing blocks to implement
74 FEC signal processing blocks
127 FFT signal processing blocks
133 Filter signal processing blocks
/OK3568_Linux_fs/buildroot/package/webrtc-audio-processing/
H A DConfig.in6 bool "webrtc-audio-processing"
16 http://freedesktop.org/software/pulseaudio/webrtc-audio-processing/
18 comment "webrtc-audio-processing needs a toolchain w/ C++, NPTL, gcc >= 4.8"
/OK3568_Linux_fs/kernel/Documentation/networking/devlink/
H A Ddevlink-trap.rst12 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 …]
/OK3568_Linux_fs/kernel/Documentation/hid/
H A Dhid-sensor.rst52 - 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
/OK3568_Linux_fs/u-boot/board/Barix/ipam390/
H A DREADME.ipam39097 (AIS Parse): Processing command 0: 0x5853590D.
100 (AIS Parse): Processing command 1: 0x5853590D.
103 (AIS Parse): Processing command 2: 0x5853590D.
106 (AIS Parse): Processing command 3: 0x5853590D.
109 (AIS Parse): Processing command 4: 0x5853590D.
112 (AIS Parse): Processing command 5: 0x58535901.
116 (AIS Parse): Processing command 6: 0x58535906.
/OK3568_Linux_fs/kernel/Documentation/admin-guide/media/
H A Dipu3.rst6 Intel Image Processing Unit 3 (IPU3) Imaging Unit (ImgU) driver
14 This file documents the Intel IPU3 (3rd generation Image Processing Unit)
27 The Imaging Unit (ImgU) is responsible for processing images captured
77 Image processing using IPU3 ImgU requires tools such as raw2pnm [#f1]_, and
162 - Processing parameters
184 format), ImgU starts processing the buffer and produces the video output in YUV
190 video nodes should be enabled for IPU3 to start image processing.
216 Details on processing parameters specific to the IPU3 can be found in
243 larger bayer frame for further YUV processing than "VIDEO" mode to get high
261 Processing the image in raw Bayer format
[all …]
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/opencv/
H A Dade_0.1.1f.bb1 SUMMARY = "A graph construction, manipulation, and processing framework"
3 and processing framework. ADE Framework is suitable for \
4 organizing data flow processing and execution."
/OK3568_Linux_fs/kernel/drivers/gpu/drm/msm/disp/dpu1/
H A Ddpu_crtc.h51 * @PRE_COMMIT: state transitions should be done before processing the commit
52 * @POST_COMMIT: state transitions to be done after processing the commit.
89 * struct dpu_crtc_frame_event: stores crtc frame event for crtc processing
127 * @feature_list : list of color processing features supported on a crtc
128 * @active_list : list of color processing features are active
129 * @dirty_list : list of color processing features are dirty
/OK3568_Linux_fs/kernel/tools/perf/util/
H A Ds390-cpumsf.c37 * auxiliary trace data processing. See s390_cpumsf_process_auxtrace_info()
44 * the offset and size of a CPU's auxtrace data. During auxtrace processing
57 * 2. PERF_RECORD_XXX processing triggers access to the auxtrace_queues.
83 * Perf event processing.
84 * Event processing of PERF_RECORD_XXX entries relies on time stamp entries.
106 * | list, sort order is the timestamp. The event processing is deferred until
130 * Deferred processing determined by perf_session__process_user_event() is
193 * Return 0 on success and greater zero on error so processing continues.
577 * - of the event that triggered this processing.
580 * position on where to continue processing on the next invocation
[all …]

12345678910>>...167