public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Marian Mihailescu <mihailescu2m@gmail.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory
Date: Wed, 15 Mar 2017 22:30:58 +1030	[thread overview]
Message-ID: <BD887BB3-53F1-4CBF-ACFF-0B6F271ABFE5@gmail.com> (raw)
In-Reply-To: <CABxcv=n6GxpcLN6CR2mL+SZX95M9Vj6gg5iK3U3ggYTCK20KXg@mail.gmail.com>

Thanks for the quick reply.

Decoding works without issues for me too.
I did not change the CMA size or used s5p_mfc.mem parameter. However, according to the Marek, the default 8M should be enough for 3 instances of H264 encoders/decoders. My test was encoding a 30 seconds 720p clip, so I thought memory should not be a big issue; also it’s working w/o these patches applied, so I think CMA size is enough.
Nevertheless, I will try setting them, but I would feel better if someone else would try encoding too.

Cheers,
Marian

> On 15 Mar. 2017, at 10:19 pm, Javier Martinez Canillas <javier@dowhile0.org> wrote:
> 
> Hello Marian,
> 
> On Wed, Mar 15, 2017 at 8:36 AM, Marian Mihailescu
> <mihailescu2m@gmail.com> wrote:
>> Hi,
>> 
>> After testing these patches, encoding using MFC fails when requesting
>> buffers for capture (it works for output) with ENOMEM (it complains it
>> cannot allocate memory on bank1).
>> Did anyone else test encoding?
>> 
> 
> I've not tested encoding, but I did test decoding and it works for me
> with Shuah's patch to increase the CMA memory [0]. Did you test with
> that one as well?
> 
> Also you could try using the 5p_mfc.mem kernel param as explained in
> the commit message of "media: s5p-mfc: Add support for probe-time
> preallocated block based allocator".
> 
> [0]: https://patchwork.kernel.org/patch/9596737/
> 
>> Thanks,
>> Marian
>> 
> 
> Best regards,
> Javier

  reply	other threads:[~2017-03-15 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170317120635eucas1p1d13c446f1418de46a49516e95bf9075d@eucas1p1.samsung.com>
2017-03-15 11:36 ` [PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory Marian Mihailescu
2017-03-15 11:49   ` Javier Martinez Canillas
2017-03-15 12:00     ` Marian Mihailescu [this message]
2017-03-15 12:25       ` Javier Martinez Canillas
2017-03-17 12:06   ` Andrzej Hajda
2017-03-22  9:33     ` Marian Mihailescu
2017-03-22  9:40       ` Marek Szyprowski
2017-03-22 10:04         ` Marian Mihailescu
2017-03-22 10:17       ` Marek Szyprowski
     [not found] <CGME20170220133910eucas1p10f347d7688dd51ea70d15994c9d5d1f1@eucas1p1.samsung.com>
2017-02-20 13:38 ` Marek Szyprowski

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=BD887BB3-53F1-4CBF-ACFF-0B6F271ABFE5@gmail.com \
    --to=mihailescu2m@gmail.com \
    --cc=javier@dowhile0.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=shuahkh@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