linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Kelvin Lawson <klawson@lisden.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH] media: venus: Add support for H265 controls required by gstreamer V4L2 H265 module
Date: Fri, 7 Dec 2018 11:43:20 +0200	[thread overview]
Message-ID: <19f7304f-4a88-339f-faa2-2fac5a3b6b76@linaro.org> (raw)
In-Reply-To: <1543599060-3776-1-git-send-email-klawson@lisden.com>

Hi Kelvin,

Thanks for the patch!

On 11/30/18 7:31 PM, Kelvin Lawson wrote:
> Add support for V4L2_CID_MPEG_VIDEO_HEVC_PROFILE and
> V4L2_CID_MPEG_VIDEO_HEVC_LEVEL controls required by gstreamer V4L2 H265
> encoder module.
> 
> Signed-off-by: Kelvin Lawson <klawson@lisden.com>
> ---
>  drivers/media/platform/qcom/venus/venc_ctrls.c | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/drivers/media/platform/qcom/venus/venc_ctrls.c b/drivers/media/platform/qcom/venus/venc_ctrls.c
> index 45910172..ad1a4d8 100644
> --- a/drivers/media/platform/qcom/venus/venc_ctrls.c
> +++ b/drivers/media/platform/qcom/venus/venc_ctrls.c
> @@ -101,6 +101,9 @@ static int venc_op_s_ctrl(struct v4l2_ctrl *ctrl)
>  	case V4L2_CID_MPEG_VIDEO_H264_PROFILE:
>  		ctr->profile.h264 = ctrl->val;
>  		break;
> +	case V4L2_CID_MPEG_VIDEO_HEVC_PROFILE:
> +		ctr->profile.hevc = ctrl->val;
> +		break;
>  	case V4L2_CID_MPEG_VIDEO_VP8_PROFILE:
>  		ctr->profile.vpx = ctrl->val;
>  		break;
> @@ -110,6 +113,9 @@ static int venc_op_s_ctrl(struct v4l2_ctrl *ctrl)
>  	case V4L2_CID_MPEG_VIDEO_H264_LEVEL:
>  		ctr->level.h264 = ctrl->val;
>  		break;
> +	case V4L2_CID_MPEG_VIDEO_HEVC_LEVEL:
> +		ctr->level.hevc = ctrl->val;
> +		break;
>  	case V4L2_CID_MPEG_VIDEO_H264_I_FRAME_QP:
>  		ctr->h264_i_qp = ctrl->val;
>  		break;
> @@ -217,6 +223,19 @@ int venc_ctrl_init(struct venus_inst *inst)
>  		0, V4L2_MPEG_VIDEO_MPEG4_LEVEL_0);
>  
>  	v4l2_ctrl_new_std_menu(&inst->ctrl_handler, &venc_ctrl_ops,
> +		V4L2_CID_MPEG_VIDEO_HEVC_PROFILE,
> +		V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN_10,
> +		~((1 << V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN) |
> +		  (1 << V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN_STILL_PICTURE) |
> +		  (1 << V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN_10)),
> +		V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN);
> +
> +	v4l2_ctrl_new_std_menu(&inst->ctrl_handler, &venc_ctrl_ops,
> +		V4L2_CID_MPEG_VIDEO_HEVC_LEVEL,
> +		V4L2_MPEG_VIDEO_HEVC_LEVEL_6_2,
> +		0, V4L2_MPEG_VIDEO_HEVC_LEVEL_1);
> +
> +	v4l2_ctrl_new_std_menu(&inst->ctrl_handler, &venc_ctrl_ops,

you are adding two new menu controls but forgot to increment the count
of controls in v4l2_ctrl_handler_init(). Can you resend with that fixed?

>  		V4L2_CID_MPEG_VIDEO_H264_PROFILE,
>  		V4L2_MPEG_VIDEO_H264_PROFILE_MULTIVIEW_HIGH,
>  		~((1 << V4L2_MPEG_VIDEO_H264_PROFILE_BASELINE) |
> 

-- 
regards,
Stan

  reply	other threads:[~2018-12-07  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 17:31 [PATCH] media: venus: Add support for H265 controls required by gstreamer V4L2 H265 module Kelvin Lawson
2018-12-07  9:43 ` Stanimir Varbanov [this message]
2018-12-10 14:11   ` [PATCH v2] " Kelvin Lawson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19f7304f-4a88-339f-faa2-2fac5a3b6b76@linaro.org \
    --to=stanimir.varbanov@linaro.org \
    --cc=klawson@lisden.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).