On 07/31/2017 05:32 PM, Jacob Chen wrote:
> PorterDuff mode control are used to determine
> how two images are combined.
>
> Signed-off-by: Jacob Chen <jacob-chen@xxxxxxxxxx>
> ---
> Documentation/media/uapi/v4l/extended-controls.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/media/uapi/v4l/extended-controls.rst b/Documentation/media/uapi/v4l/extended-controls.rst
> index abb1057..f9c93bb 100644
> --- a/Documentation/media/uapi/v4l/extended-controls.rst
> +++ b/Documentation/media/uapi/v4l/extended-controls.rst
> @@ -3021,6 +3021,10 @@ Image Process Control IDs
> The video deinterlacing mode (such as Bob, Weave, ...). The menu items are
> driver specific and are documented in :ref:`v4l-drivers`.
>
> +``V4L2_CID_PORTER_DUFF_MODE (menu)``
> + The PorterDuff blend modes. PorterDuff is way to overlay, combine and
> + trim images as if they were pieces of cardboard, device could use to
> + determine how two images are combined.
A little rewrite:
The PorterDuff blend modes. PorterDuff is a method to overlay, combine and
trim images as if they were pieces of cardboard. The device uses this to
determine how two images are combined.
Also add a link to the same android article that you pointed to in the header.
Regards,
Hans
>
> .. _dv-controls:
>
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
