From: ayaka <ayaka@soulik.info>
To: linux-media@vger.kernel.org
Cc: kyungmin.park@samsung.com, jtp.park@samsung.com, m.chehab@samsung.com
Subject: Re: [PATCH] s5p-mfc: correct the formats info for encoder
Date: Tue, 23 Sep 2014 00:50:20 +0800 [thread overview]
Message-ID: <5420534C.7070701@soulik.info> (raw)
In-Reply-To: <072d01cfd682$4cf2b220$e6d81660$%debski@samsung.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
2014/09/23 00:28, Kamil Debski wrote:
> Hi Ayaka,
>
> Sorry for such a late reply - I just noticed this patch.
>
>> The NV12M is supported by all the version of MFC, so it is better
>> to use it as default OUTPUT format. MFC v5 doesn't support NV21,
>> I have tested it, for the SEC doc it is not supported either.
>
> A proper Sign-off is missing here.
>
Sorry to miss it again.
> According to the documentation of MFC v5 I have non-tiled format
> is supported. Which documentation were you looking at?
>
But the V4L2_PIX_FMT_NV12MT is only supported by MFC_V5_BIT from your
code, V4L2_PIX_FMT_NV12M is supported by all the version.
>> From my documentation:
> ++++++++++++++ ENC_MAP_FOR_CUR 0xC51C Memory structure setting
> register of the current frame. R/W 0x00000000
>
> Bits Name Description Reset Value [31:2] RESERVED Reserved 0 [1:0]
> ENC_MAP_FOR_CUR Memory structure of the current frame 0 : Linear
> mode 3 : 64x32 tiled mode 0 ++++++++++++++
>
In the page 2277. The same result.
I think the V4L2_PIX_FMT_NV12MT is 64x32 Tiles mode, but what I remove
for MFC v5 is V4L2_PIX_FMT_NV21M.
> Best wishes,
>
- --
ayaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJUIFNLAAoJEPsGh4kgR4i5HcIP/2qwn7uIFq66qpSajXmtcLx3
3/wt8n26u6GhTMUnIJKZS07FGtv7qizUVqeY3WmfWQw3jLaUjZeVviVH08y3DrE8
+7Vjq2rxz57ou4bBtc4qIgTWB7z2yuVSpBOYUB94laItQ7KDap4EgLf89m4KaKTt
5nULR0byxXh+RuUOw80v0eP/TBz7SRfYZnulASV9QlGS6T3Xp6v4U6W8LbSbieR5
63PwPxYP7aDVb5R6qzaLIVXNuI53vn5VhrQ6JJUfKee5YSbkV/Ff6XK+7/P162Pn
5cVt06X+RUeZXHGqCroMNb9cdm+7JHOZL458NPn4NmTJnFcPNu6JzW9iLymHeHC8
iFmNhpDuHJBulKsW44lqKe1fHT22a5C/oJAI1ZS9c3yrH+TqHkfEkUJjglSRByzj
ptTFFZVTCdiL5VwnDlfowR4ZzrkZuoWzHIn5cGeHogvbLbxCbtV67+IFpWlXfyJu
rKnCI+DKYb5cjEiHm7kzGbAO04AfNMT79sNwrD+sPuvnaFyRiy2rjKv3ubnPFRVp
3agNRzAcCgmsW3K10P3ism4ceJUqeZtFvieCQrjiQdxj8EB7QAcgOhgn3K//zrQ1
mQP7xuVQcwpaRIOx/3jSlVWYFrkFs2+tmgS9oEn+v40gXOQXk8rML21gHvpDuCnf
qJXx0UVYQRV7Bhgv8EFW
=SNTL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-09-22 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 16:15 [PATCH] correct formats info in s5p-mfc encoder ayaka
2014-07-23 16:15 ` [PATCH] s5p-mfc: correct the formats info for encoder ayaka
2014-09-22 16:28 ` Kamil Debski
2014-09-22 16:50 ` ayaka [this message]
2014-10-22 11:46 ` Kamil Debski
2014-10-22 14:07 ` ayaka
2014-10-22 14:07 ` ayaka
-- strict thread matches above, loose matches on Subject: below --
2014-10-22 18:03 ayaka
2014-10-22 18:03 ` 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=5420534C.7070701@soulik.info \
--to=ayaka@soulik.info \
--cc=jtp.park@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@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