public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: ayaka <ayaka@soulik.info>
To: Kamil Debski <k.debski@samsung.com>, linux-media@vger.kernel.org
Cc: kyungmin.park@samsung.com, jtp.park@samsung.com, mchehab@osg.samsung.com
Subject: Re: [PATCH 3/4] [media] s5p-mfc: don't close instance after free OUTPUT buffers
Date: Sun, 14 Feb 2016 02:03:56 +0800	[thread overview]
Message-ID: <56BF700C.8060000@soulik.info> (raw)
In-Reply-To: <003501d15f57$8f1904b0$ad4b0e10$@samsung.com>

I reviewed the code again

2016-02-04 22:23, Kamil Debski wrote:
> Hi,
>
>> From: ayaka [mailto:ayaka@soulik.info]
>> Sent: Saturday, January 30, 2016 7:54 PM
>>
>> Free buffers in OUTPUT is quite normal to detect the driver's buffer
> capacity,
>> it doesn't mean the application want to close that mfc instance.
>>
>> Signed-off-by: ayaka <ayaka@soulik.info>
>> ---
>>   drivers/media/platform/s5p-mfc/s5p_mfc_dec.c | 1 -
>>   1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c
>> b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c
>> index aebe4fd..609b17b 100644
>> --- a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c
>> +++ b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c
>> @@ -474,7 +474,6 @@ static int reqbufs_output(struct s5p_mfc_dev *dev,
>> struct s5p_mfc_ctx *ctx,
>>   		ret = vb2_reqbufs(&ctx->vq_src, reqbufs);
>>   		if (ret)
>>   			goto out;
>> -		s5p_mfc_close_mfc_inst(dev, ctx);
>>   		ctx->src_bufs_cnt = 0;
>>   		ctx->output_state = QUEUE_FREE;
>>   	} else if (ctx->output_state == QUEUE_FREE) {
> What exactly do you mean by "detecting buffer capacity"  ? Is it the max
> number of buffer
> that can be allocated?
>
> Anyway, if the instance is not closed, then in a consecutive call to reqbufs
> (with cound != 0)
> the instance will be opened for a second time. So either the instance has to
> be closed, or
Does the s5p_mfc_open_mfc_inst() open a new instance?In that case if 
reqbufs->count == 0, it won't open a new instance. Also before allocate 
buffers, it will check whether the instance has been opened.
So I think the instance won't be opened twice.
> it should be opened in another place.
>
> Best wishes,


  reply	other threads:[~2016-02-13 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 18:53 [PATCH 0/4] [media] s5p-mfc: remove a few little bugs in driver ayaka
2016-01-30 18:53 ` [PATCH 1/4] [media] s5p-mfc: Add handling of buffer freeing reqbufs request ayaka
2016-01-30 19:27   ` kbuild test robot
2016-01-30 18:53 ` [PATCH 2/4] [media] s5p-mfc: remove unnecessary check in try_fmt ayaka
2016-01-30 18:53 ` [PATCH 3/4] [media] s5p-mfc: don't close instance after free OUTPUT buffers ayaka
2016-02-04 14:23   ` Kamil Debski
2016-02-13 18:03     ` ayaka [this message]
2016-01-30 18:53 ` [PATCH 4/4] [media] s5p-mfc: fix a typo in s5p_mfc_dec ayaka

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=56BF700C.8060000@soulik.info \
    --to=ayaka@soulik.info \
    --cc=jtp.park@samsung.com \
    --cc=k.debski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.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