From: Sakari Ailus <sakari.ailus@iki.fi>
To: Su Jiaquan <jiaquan.lnx@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-media <linux-media@vger.kernel.org>,
jqsu@marvell.com, xzhao10@marvell.com
Subject: Re: How to express planar formats with mediabus format code?
Date: Sun, 01 Sep 2013 17:38:23 +0300 [thread overview]
Message-ID: <5223515F.8030002@iki.fi> (raw)
In-Reply-To: <CALxrGmWreOkjKuBrR4Y2i=V2EvwHxeP69vsziAZrYQWQvZWfGw@mail.gmail.com>
Hi Jiaquan and Laurent,
Apologies for my delayed reply.
Su Jiaquan wrote:
> Hi Sakari,
>
> On Thu, Aug 22, 2013 at 7:29 PM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>> Hi Jiaquan,
>>
>> On Wednesday 21 August 2013 18:14:50 Su Jiaquan wrote:
>>> On Tue, Aug 20, 2013 at 8:53 PM, Laurent Pinchart wrote:
>>>> Hi Jiaquan,
>>>>
>>>> I'm not sure if that's needed here. Vendor-specific formats still need to
>>>> be documented, so we could just create a custom YUV format for your case.
>>>> Let's start with the beginning, could you describe what gets transmitted
>>>> on the bus when that special format is selected ?
>>>
>>> For YUV420P format, the data format sent from IPC is similar to
>>> V4L2_MBUS_FMT_YUYV8_1_5X8, but the content for each line is different:
>>> For odd line, it's YYU YYU YYU... For even line, it's YYV YYV YYV...
>>> then DMA engine send them to RAM in planar format.
>>>
>>> For YUV420SP format, the data format sent from IPC is YYUV YYUV
>>> YYUV(maybe called V4L2_MBUS_FMT_YYUV8_2X8?), but DMA engine drop UV
>>> every other line, then send them to RAM as semi-planar.
>>
>> V4L2_MBUS_FMT_YYUV8_2X8 looks good to me.
>>
>>> Well, the first data format is too odd, I don't have a clue how to
>>> call it, do you have suggestion?
>>
>> Maybe V4L2_MBUS_FMT_YU8_YV8_1_5X8 ? I've CC'ed Sakari Ailus, he's often pretty
>> creative for these issues.
>>
>> --
>> Regards,
>>
>> Laurent Pinchart
>>
>
> Does the format V4L2_MBUS_FMT_YU8_YV8_1_5X8 sounds good to you? Do you
> have better idea how we should describe this format?
If bus (or DMA) transfers 8 bits at a time, then yes. Otherwise perhaps
...1X12.
The documentation should be extended to cover different components on
alternating lines; I don't think we've had such cases before. I think
just a note telling to do exactly as above should suffice.
--
Kind regards,
Sakari Ailus
sakari.ailus@iki.fi
prev parent reply other threads:[~2013-09-01 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 2:32 How to express planar formats with mediabus format code? Su Jiaquan
2013-08-04 21:02 ` Guennadi Liakhovetski
2013-08-06 9:18 ` Su Jiaquan
2013-08-06 9:40 ` Guennadi Liakhovetski
2013-08-08 21:12 ` Laurent Pinchart
2013-08-09 17:06 ` Su Jiaquan
2013-08-15 8:27 ` Su Jiaquan
2013-08-20 12:53 ` Laurent Pinchart
2013-08-21 10:14 ` Su Jiaquan
2013-08-22 11:29 ` Laurent Pinchart
2013-08-30 7:57 ` Su Jiaquan
2013-09-01 14:38 ` Sakari Ailus [this message]
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=5223515F.8030002@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=g.liakhovetski@gmx.de \
--cc=jiaquan.lnx@gmail.com \
--cc=jqsu@marvell.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=xzhao10@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.