![]() mediatek,reserve-memory-dip_smem.txt | 45 +Īrch/arm64/boot/dts/mediatek/mt8183.dtsi | 36 +ĭrivers/media/platform/mtk-isp/Kconfig | 21 +ĭrivers/media/platform/mtk-isp/Makefile | 18 +ĭrivers/media/platform/mtk-isp/isp_50/Makefile | 17 +ĭrivers/media/platform/mtk-isp/isp_50/dip/Makefile | 35 + bindings/media/mediatek,mt8183-dip.txt | 35 + ![]() bindings/media/mediatek,dip_smem.txt | 29 + platform: mtk-isp: Add Mediatek DIP driver Media: platform: Add Mediatek DIP driver KConfig dt-bindings: mt8183: Added DIP dt-bindings dt-bindings: mt8183: Added DIP-SMEM dt-bindings dt-bindings: mt8183: Add binding for DIP shared memoryĭts: arm64: mt8183: Add DIP shared memory node * mtk_dip-v4l2-util.c: Implements V4L2 and vb2 ops. We reserved a memory region for the co-processor and DIP to exchange the * mtk_dip-smem-drv.c: Provides the shared memory management required operation. * mtk_dip-ctrl.c: Handles the HW ctrl request from userspace. * mtk_dip-dev.c: Implements context-independent flow. * mtk_dip-v4l2.c: Static DIP contexts configuration. Both the twoĬontexts share the same DIP hardware to process the images. ![]() For example, context 0 isĬreated for preview path and context 1 is for capture path. * mtk_dip-dev-ctx-core.c: Implements common software flow of DIP driver.ĭIP driver supports two or more software contexts. The overall file structure of the DIP driver is as following: Size and format can be different from the ones of MDP-0. MDP-1 (capture video device): return the processed image data, the image MDP-0 (capture video device): return the processed image data.ĥ. Needs two capture video devices to return the streaming data to the user.Ĥ. Hardware support multiple output image with different size and format so it DIP (sub device): connects to MDP-0 and MDP-1. RAW (output video device): connects to DIP sub device. The metadata interface used currently is onlyĪ temporary solution to kick off driver development and is not ready forĢ. Meta (output video device): connects to DIP sub device. We have theįollowing entities describing the DIP path.ġ. The driver is implemented with V4L2 and media controller framework. The DIP driver also support image format conversion, resizing and Furthermore, it performs demosaicingĪnd noise reduction on the image to support the advanced camera features of theĪpplication. The image content in Mediatek ISP system. The DIP driver as RFC to discuss first and would like some review comments onĭigital Image Processing (DIP) unit can accept the tuning parameters and adjust Series based on V4L2 and media controller framework. It belongs to the first Mediatek’s ISP driver Processing (DIP) driver on Mediatek mt8183 SoC, which will be used in cameraįeatures on CrOS application. This is the first version of the RFC patch series adding Digital Image Subject: media: platform: Add support for Digital Image Processing (DIP) on mt8183 SoCĭate: Fri, 19:21:24 +0800 Media: platform: Add support for Digital Image Processing (DIP) on mt8183 SoC - Frederic Chen archive mirror help / color / mirror / Atom feed From: Frederic Chen
0 Comments
Leave a Reply. |