mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>,
	mchehab@kernel.org, hverkuil-cisco@xs4all.nl
Cc: shawnguo@kernel.org, robh+dt@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	xiahong.bao@nxp.com, eagle.zhou@nxp.com, tao.jiang_2@nxp.com,
	imx@lists.linux.dev, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] media: amphion: Support display delay for Hevc format
Date: Tue, 7 Jan 2025 13:18:15 +0800	[thread overview]
Message-ID: <fc536f83-912a-4b9f-9523-e6cdb4463eb9@oss.nxp.com> (raw)
In-Reply-To: <6fcdd612-0f1e-42bd-b171-6f1d70790ffd@oss.nxp.com>

Hi Nicolas,

On 2025/1/7 9:29, Ming Qian(OSS) wrote:
> Hi Nicolas,
> 
> 
> On 2025/1/7 6:16, Nicolas Dufresne wrote:
>> Hi,
>>
>> nit: use capital HEVC in the subject
>>
> 
> I'll fix it in the v2 patch
> 
>> Le jeudi 19 décembre 2024 à 10:51 +0900, Ming Qian a écrit :
>>> The amphion decoder firmware v1.9.0 supports display delay 0 for
>>> hevc format, then driver can enable this feature.
>>
>> nit: HEVC
>>
>> I think this added "feature" hides a bug you haven't fixed in this patch.
>>
>>
>>          v4l2_ctrl_new_std(&inst->ctrl_handler, &vdec_ctrl_ops,
>>                            V4L2_CID_MPEG_VIDEO_DEC_DISPLAY_DELAY_ENABLE,
>>                            0, 1, 1, 0);
>>
>> With the control registered this way, 0 is the default, and the range 
>> of 0-1.
>> But from your commit message, this is only supported from firmware 
>> 1.9.0 and up.
>> I think the patch should basically adjust the min and def values 
>> according to
>> the detected firmware version.
>>
>> This might actually be more complex, aka per CODEC, and for that you 
>> may want to
>> use v4l2_ctrl_config structure.
>>
>> Nicolas
>>
> 
> Thanks for the tip.
> By the way, how to define different ctrl values for each CODEC format?
> Is it reasonable to new a ctrl after set capture format?
> Or can we change the min/max value after set capture format?
> 
> Thanks,
> Ming

I checked the driver again, and I think there is no issue with ctrl
V4L2_CID_MPEG_VIDEO_DEC_DISPLAY_DELAY_ENABLE,
it has supported to display frame immediately after it's decoded for all
supported CODEC formats.

But there is a issue with amphion vpu, the decoder will pre-parse 3
frames before decoding the first frame, in other words, the delay
between frame input and frame decoding is relatively large, then
firmware difined a low-latency flush mode, that adding some flush
padding data after every frame, then decoder can support to input 1
frame and decode 1 frame, the decoding latency can be reduced.
Only H264 decoder support this format currently, but since v1.9.0,
it can support HEVC format too.

I think my commit message is not accurate. I'll improve the commit
message in V2 patch.

Thanks,
Ming

> 
>>
>>> Signed-off-by: Ming Qian <ming.qian@oss.nxp.com>
>>> ---
>>>   drivers/media/platform/amphion/vpu_malone.c | 14 +++++++++++---
>>>   1 file changed, 11 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/media/platform/amphion/vpu_malone.c 
>>> b/drivers/media/platform/amphion/vpu_malone.c
>>> index 5c6b2a841b6f..8f4aa48b2d65 100644
>>> --- a/drivers/media/platform/amphion/vpu_malone.c
>>> +++ b/drivers/media/platform/amphion/vpu_malone.c
>>> @@ -332,6 +332,8 @@ struct vpu_dec_ctrl {
>>>       u32 buf_addr[VID_API_NUM_STREAMS];
>>>   };
>>> +static const struct malone_padding_scode *get_padding_scode(u32 
>>> type, u32 fmt);
>>> +
>>>   u32 vpu_malone_get_data_size(void)
>>>   {
>>>       return sizeof(struct vpu_dec_ctrl);
>>> @@ -654,8 +656,10 @@ static int vpu_malone_set_params(struct 
>>> vpu_shared_addr *shared,
>>>           hc->jpg[instance].jpg_mjpeg_interlaced = 0;
>>>       }
>>> -    hc->codec_param[instance].disp_imm = 
>>> params->display_delay_enable ? 1 : 0;
>>> -    if (malone_format != MALONE_FMT_AVC)
>>> +    if (params->display_delay_enable &&
>>> +        get_padding_scode(SCODE_PADDING_BUFFLUSH, 
>>> params->codec_format))
>>> +        hc->codec_param[instance].disp_imm = 1;
>>> +    else
>>>           hc->codec_param[instance].disp_imm = 0;
>>>       hc->codec_param[instance].dbglog_enable = 0;
>>>       iface->dbglog_desc.level = 0;
>>> @@ -1024,6 +1028,7 @@ static const struct malone_padding_scode 
>>> padding_scodes[] = {
>>>       {SCODE_PADDING_EOS,      V4L2_PIX_FMT_JPEG,        {0x0, 0x0}},
>>>       {SCODE_PADDING_BUFFLUSH, V4L2_PIX_FMT_H264,        {0x15010000, 
>>> 0x0}},
>>>       {SCODE_PADDING_BUFFLUSH, V4L2_PIX_FMT_H264_MVC,    {0x15010000, 
>>> 0x0}},
>>> +    {SCODE_PADDING_BUFFLUSH, V4L2_PIX_FMT_HEVC,        {0x3e010000, 
>>> 0x20}},
>>>   };
>>>   static const struct malone_padding_scode padding_scode_dft = {0x0, 
>>> 0x0};
>>> @@ -1058,8 +1063,11 @@ static int vpu_malone_add_padding_scode(struct 
>>> vpu_buffer *stream_buffer,
>>>       int ret;
>>>       ps = get_padding_scode(scode_type, pixelformat);
>>> -    if (!ps)
>>> +    if (!ps) {
>>> +        if (scode_type == SCODE_PADDING_BUFFLUSH)
>>> +            return 0;
>>>           return -EINVAL;
>>> +    }
>>>       wptr = readl(&str_buf->wptr);
>>>       if (wptr < stream_buffer->phys || wptr > stream_buffer->phys + 
>>> stream_buffer->length)
>>

  reply	other threads:[~2025-01-07  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  1:51 Ming Qian
2024-12-19  1:51 ` [PATCH 2/2] media: amphion: Add a frame flush mode for decoder Ming Qian
2025-01-06 22:16 ` [PATCH 1/2] media: amphion: Support display delay for Hevc format Nicolas Dufresne
2025-01-07  1:29   ` Ming Qian(OSS)
2025-01-07  5:18     ` Ming Qian(OSS) [this message]
2025-01-08 19:27     ` Nicolas Dufresne

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=fc536f83-912a-4b9f-9523-e6cdb4463eb9@oss.nxp.com \
    --to=ming.qian@oss.nxp.com \
    --cc=eagle.zhou@nxp.com \
    --cc=festevam@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=tao.jiang_2@nxp.com \
    --cc=xiahong.bao@nxp.com \
    /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

all inboxes | Powered by JetHome®