From: javier.martin@vista-silicon.com (javier Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Support for 'Coda' video codec IP.
Date: Mon, 2 Jul 2012 13:13:17 +0200 [thread overview]
Message-ID: <CACKLOr1shAodE9FDD9dZ1dgAKy4PyPRQAsyMOiNzqQ0uQFTYGA@mail.gmail.com> (raw)
In-Reply-To: <20120702105427.GP2698@pengutronix.de>
On 2 July 2012 12:54, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Mon, Jul 02, 2012 at 12:36:46PM +0200, javier Martin wrote:
>> Hi Sascha,
>> I almost have a final version ready which includes multi-instance
>> support (not tested though) [1]. As I stated, we assumed the extra
>> effort of looking at your code in [2] in order to provide a mechanism
>> that preserves compatibility between VPUs in i.MX21, i.MX51 and
>> i.MX53. This is the only thing left in order to send the driver for
>> mainline submission.
>>
>> While I was reading your code I found out that you keep the following
>> formats for v1 (codadx6-i.MX27) codec:
>>
>> static int vpu_v1_codecs[VPU_CODEC_MAX] = {
>> [VPU_CODEC_AVC_DEC] = 2,
>> [VPU_CODEC_VC1_DEC] = -1,
>> [VPU_CODEC_MP2_DEC] = -1,
>> [VPU_CODEC_DV3_DEC] = -1,
>> [VPU_CODEC_RV_DEC] = -1,
>> [VPU_CODEC_MJPG_DEC] = 0x82,
>> [VPU_CODEC_AVC_ENC] = 3,
>> [VPU_CODEC_MP4_ENC] = 1,
>> [VPU_CODEC_MJPG_ENC] = 0x83,
>> };
>>
>> As I understand, this means the following operations are supported:
>>
>> 1- H264 decoding.
>> 2- H264 encoding
>> 3- MP4 encoding.
>> 4- MJPG decoding.
>> 5- MJPG encoding.
>>
>> I totally agree with MP4 and H264 formats but, are you sure about
>> MJPG? I have a i.MX27 v1 codec (codadx6) but I didn't know that this
>> codec supported MJPG. Have you tested this code with an i.MX27 and
>> MJPG? Where did you find out that it supports this format?
>
> We haven't tested MJPG on the i.MX27. The table above is from the
> original Freescale code, so I assume it's correct and I assume that
> the coda dx6 can do MJPEG.
Fabio, could you confirm that the VPU in the i.MX27 supports MJPG too?
>> Are you
>> using firmware version 2.2.4 for v1 codecs?
>
> No, 2.2.5
Where did you get that firmware version? The only related download I
can find in [1] is
'MX273DS_FULL_VPU_SW_AND_VPU_FIRMWARE_2.2.4_WINCE_TO2.X_ONLY' which
includes firmware 2.2.4.
[1] http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX27&nodeId=018rH3ZrDR66AF&fpsp=1&tab=Design_Tools_Tab
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
next prev parent reply other threads:[~2012-07-02 11:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 14:11 [RFC] Support for 'Coda' video codec IP Javier Martin
2012-06-19 18:17 ` Sascha Hauer
2012-06-20 7:51 ` javier Martin
2012-06-20 9:01 ` Sascha Hauer
2012-06-20 10:00 ` Mark Brown
2012-06-20 13:09 ` Shawn Guo
2012-06-20 13:31 ` Mark Brown
2012-06-20 13:56 ` Shawn Guo
2012-06-20 14:27 ` Mark Brown
2012-06-20 14:25 ` javier Martin
2012-06-20 14:33 ` Shawn Guo
2012-07-02 10:36 ` javier Martin
2012-07-02 10:54 ` Sascha Hauer
2012-07-02 11:13 ` javier Martin [this message]
2012-07-02 13:48 ` javier Martin
2012-07-03 19:42 ` Fabio Estevam
2012-06-20 14:03 ` Shawn Guo
2012-06-20 14:10 ` javier Martin
2012-06-20 14:25 ` Shawn Guo
2012-06-20 14:31 ` Sascha Hauer
2012-06-20 3:26 ` Fabio Estevam
2012-06-20 8:09 ` javier Martin
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=CACKLOr1shAodE9FDD9dZ1dgAKy4PyPRQAsyMOiNzqQ0uQFTYGA@mail.gmail.com \
--to=javier.martin@vista-silicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).