libcamera/vivid.git - libcamera pipeline handler for VIVID

summary refs log tree commit diff

path: root/src/v4l2/v4l2_compat_manager.h

diff options

author	Florian Sylvestre <fsylvestre@baylibre.com>	2022-07-27 10:38:18 +0200
committer	Laurent Pinchart <laurent.pinchart@ideasonboard.com>	2022-07-28 14:55:00 +0300
commit	7a80e01b4ab3f8982fbbbd1746025da2dc5e1390 (patch)
tree	2594ae005c8383e151ae0e05fdfb7b947d83bb7b /src/v4l2/v4l2_compat_manager.h
parent	564537a9066141f01871b06bae090e6ea5b7a37f (diff)

ipa: rkisp1: Add support of Filter control

Denoise and Sharpness filters will be applied by RkISP1 during the demosaicing step. The denoise filter is responsible for removing noise from the image, while the sharpness filter will enhance its acutance. Add filter algorithm with denoise and sharpness values based on user controls. Signed-off-by: Florian Sylvestre <fsylvestre@baylibre.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Diffstat (limited to 'src/v4l2/v4l2_compat_manager.h')

0 files changed, 0 insertions, 0 deletions

clude "md_parser.hpp" #include "libcamera/internal/v4l2_videodevice.h" namespace RPi { // The CamHelper class provides a number of facilities that anyone trying // trying to drive a camera will need to know, but which are not provided by // by the standard driver framework. Specifically, it provides: // // A "CameraMode" structure to describe extra information about the chosen // mode of the driver. For example, how it is cropped from the full sensor // area, how it is scaled, whether pixels are averaged compared to the full // resolution. // // The ability to convert between number of lines of exposure and actual // exposure time, and to convert between the sensor's gain codes and actual // gains. // // A method to return the number of frames of delay between updating exposure // and analogue gain and the changes taking effect. For many sensors these // take the values 2 and 1 respectively, but sensors that are different will // need to over-ride the default method provided. // // A method to query if the sensor outputs embedded data that can be parsed. // // A parser to parse the metadata buffers provided by some sensors (for // example, the imx219 does; the ov5647 doesn't). This allows us to know for // sure the exposure and gain of the frame we're looking at. CamHelper // provides methods for converting analogue gains to and from the sensor's // native gain codes. // // Finally, a set of methods that determine how to handle the vagaries of // different camera modules on start-up or when switching modes. Some // modules may produce one or more frames that are not yet correctly exposed, // or where the metadata may be suspect. We have the following methods: // HideFramesStartup(): Tell the pipeline handler not to return this many // frames at start-up. This can also be used to hide initial frames // while the AGC and other algorithms are sorting themselves out. // HideFramesModeSwitch(): Tell the pipeline handler not to return this // many frames after a mode switch (other than start-up). Some sensors // may produce innvalid frames after a mode switch; others may not. // MistrustFramesStartup(): At start-up a sensor may return frames for // which we should not run any control algorithms (for example, metadata