From: Andrzej Hajda <a.hajda@samsung.com>
To: randy <lxr1234@hotmail.com>, Kamil Debski <k.debski@samsung.com>,
linux-media@vger.kernel.org
Cc: kyungmin.park@samsung.com
Subject: Re: using MFC memory to memery encoder, start stream and queue order problem
Date: Thu, 16 Jan 2014 13:37:24 +0100 [thread overview]
Message-ID: <52D7D284.1080700@samsung.com> (raw)
In-Reply-To: <BLU0-SMTP184B0B9737C458456530152ADBE0@phx.gbl>
On 01/15/2014 04:50 PM, randy wrote:
>
> Sorry, I forget to switch to new kernel,
> but in new kernel it doesn't work too.
> root@kagami:~/v4l2-mfc-encoder# ./mfc-encode -m /dev/video1 -c
> h264,header_mode=1 -d 1
> mfc codec encoding example application
> Andrzej Hajda <a.hajda@samsung.com>
> Copyright 2012 Samsung Electronics Co., Ltd.
>
> 106.984340799:args.c:parse_args:190: codec: H264
> 106.984870424:args.c:parse_args:187: opt header_mode=1
> 106.999434841:mfc.c:mfc_create:87: MFC device /dev/video1 opened with fd=3
> 107.15356632:v4l_dev.c:v4l_req_bufs:116: Succesfully requested 16
> buffers for device 3:0
> 107.15534549:func_dev.c:func_req_bufs:42: Succesfully requested 16
> buffers for device -1:1
> 107.15708424:func_dev.c:func_enq_buf:113: Enqueued buffer 0/16 to -1:1
> 107.15862049:func_dev.c:func_enq_buf:113: Enqueued buffer 1/16 to -1:1
> 107.16004132:func_dev.c:func_enq_buf:113: Enqueued buffer 2/16 to -1:1
> 107.16146841:func_dev.c:func_enq_buf:113: Enqueued buffer 3/16 to -1:1
> 107.16284799:func_dev.c:func_enq_buf:113: Enqueued buffer 4/16 to -1:1
> 107.16429049:func_dev.c:func_enq_buf:113: Enqueued buffer 5/16 to -1:1
> 107.16569382:func_dev.c:func_enq_buf:113: Enqueued buffer 6/16 to -1:1
> 107.16715257:func_dev.c:func_enq_buf:113: Enqueued buffer 7/16 to -1:1
> 107.16859924:func_dev.c:func_enq_buf:113: Enqueued buffer 8/16 to -1:1
> 107.17006674:func_dev.c:func_enq_buf:113: Enqueued buffer 9/16 to -1:1
> 107.17158466:func_dev.c:func_enq_buf:113: Enqueued buffer 10/16 to -1:1
> 107.17307132:func_dev.c:func_enq_buf:113: Enqueued buffer 11/16 to -1:1
> 107.17455632:func_dev.c:func_enq_buf:113: Enqueued buffer 12/16 to -1:1
> 107.17599216:func_dev.c:func_enq_buf:113: Enqueued buffer 13/16 to -1:1
> 107.17748299:func_dev.c:func_enq_buf:113: Enqueued buffer 14/16 to -1:1
> 107.17897341:func_dev.c:func_enq_buf:113: Enqueued buffer 15/16 to -1:1
> v4l_dev.c:v4l_req_bufs:111: error: Failed to request 4 buffers for
> device 3:1)
> root@kagami:~/v4l2-mfc-encoder# ls -l demo.out
> -rw-r--r-- 1 root root 0 Jan 15 15:49 demo.out
> root@kagami:~/v4l2-mfc-encoder# uname -a
> Linux kagami 3.13.0-rc8-00018-g8f39393-dirty #17 SMP PREEMPT Wed Jan 15
> 18:40:53 CST 2014 armv7l GNU/Linux
> root@kagami:~/v4l2-mfc-encoder# dmesg|grep mfc
> [ 1.295000] s5p-mfc 13400000.codec: decoder registered as /dev/video0
> [ 1.295000] s5p-mfc 13400000.codec: encoder registered as /dev/video1
> [ 100.645000] s5p_mfc_alloc_priv_buf:43: Allocating private buffer failed
> [ 100.645000] s5p_mfc_alloc_codec_buffers_v5:177: Failed to allocate
> Bank1 temporary buffer
> [ 107.065000] s5p_mfc_alloc_priv_buf:43: Allocating private buffer failed
> [ 107.065000] s5p_mfc_alloc_codec_buffers_v5:177: Failed to allocate
> Bank1 temporary buffer
Try to increase CMA size in kernel config - CONFIG_CMA_SIZE_MBYTES,
by default it is set to 16MB, try for example 64MB.
Regards
Andrzej
next prev parent reply other threads:[~2014-01-16 12:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 11:35 using MFC memory to memery encoder, start stream and queue order problem randy
2014-01-02 12:29 ` Kamil Debski
[not found] ` <BLU0-SMTP266BE9BC66B254061740251ADCB0@phx.gbl>
[not found] ` <02c801cf07ba$8518f2f0$8f4ad8d0$%debski@samsung.com>
2014-01-02 14:03 ` randy
2014-01-03 8:15 ` randy
2014-01-03 8:15 ` randy
2014-01-03 15:16 ` randy
2014-01-08 14:42 ` Kamil Debski
2014-01-08 15:44 ` randy
[not found] ` <52CD725E.5060903@hotmail.com>
2014-01-10 9:15 ` randy
2014-01-10 11:13 ` Andrzej Hajda
2014-01-10 15:23 ` randy
2014-01-13 10:15 ` Andrzej Hajda
2014-01-13 11:18 ` Andrzej Hajda
2014-01-13 15:44 ` randy
2014-01-13 16:18 ` Kamil Debski
2014-01-14 5:17 ` randy
2014-01-14 10:29 ` Andrzej Hajda
2014-01-14 16:50 ` randy
2014-01-15 7:08 ` Andrzej Hajda
2014-01-15 15:50 ` randy
2014-01-16 12:37 ` Andrzej Hajda [this message]
2014-01-16 19:30 ` randy
2014-01-16 20:10 ` randy
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=52D7D284.1080700@samsung.com \
--to=a.hajda@samsung.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=lxr1234@hotmail.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