From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, g.liakhovetski@gmx.de,
m.szyprowski@samsung.com, riverful.kim@samsung.com,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RFC/PATCH] v4l: Add V4L2_MBUS_FMT_JPEG_1X8 media bus format
Date: Thu, 24 Mar 2011 15:58:02 +0100 [thread overview]
Message-ID: <4D8B5BFA.3090205@samsung.com> (raw)
In-Reply-To: <201103241538.43283.laurent.pinchart@ideasonboard.com>
Hi Laurent,
thanks for your comments.
On 03/24/2011 03:38 PM, Laurent Pinchart wrote:
> Hi Sylwester,
>
> On Thursday 24 March 2011 15:19:54 Sylwester Nawrocki wrote:
>> Add V4L2_MBUS_FMT_JPEG_1X8 format and the corresponding Docbook
>> documentation.
>>
>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>> ---
>>
>> Hi all,
>>
>> I would like to propose and addition of JPEG format to the list
>> of media bus formats. The requirement of this format had already
>> been discussed in the past [1], [2].
>> This patch adds relevant entry in v4l2-mediabus.h header and
>> the documentation. Initially I have added only bus width information
>> to the format code. I am not sure what other information could be
>> included. I am open to suggestions if anyone knows about any other
>> requirements.
>>
>> JPEG format on media bus is, among others, required for Samsung
>> S5P MIPI CSI receiver [3] and M-5MOLS camera drivers [4].
>>
>> Comments are welcome!
>>
>> --
>> Regards,
>> Sylwester Nawrocki,
>> Samsung Poland R&D Center
>>
>> [1] http://www.spinics.net/lists/linux-media/msg27980.html
>> [2] http://www.spinics.net/lists/linux-media/msg28651.html
>> [3] http://www.spinics.net/lists/linux-samsung-soc/msg03807.html
>> [4] http://lwn.net/Articles/433836/
>> ---
>> Documentation/DocBook/v4l/subdev-formats.xml | 45
>> ++++++++++++++++++++++++++ include/linux/v4l2-mediabus.h |
>> 3 ++
>> 2 files changed, 48 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/DocBook/v4l/subdev-formats.xml
>> b/Documentation/DocBook/v4l/subdev-formats.xml index b5376e2..60a6fe2
>> 100644
>> --- a/Documentation/DocBook/v4l/subdev-formats.xml
>> +++ b/Documentation/DocBook/v4l/subdev-formats.xml
>> @@ -2463,5 +2463,50 @@
>> </tgroup>
>> </table>
>> </section>
>> +
>> + <section>
>> + <title>JPEG Compressed Formats</title>
>> +
>> + <para>Those data formats are used to transfer arbitrary byte-based
>> image + data obtained from JPEG compression process. The format code
>> + is made of the following information.
>> + <itemizedlist>
>> + <listitem>The bus width in bits.</listitem>
>> + </itemizedlist>
>> +
>> + <para>For instance, a format where bus width is 8 bits will be named
>> + <constant>V4L2_MBUS_FMT_JPEG_1X8</constant>.
>> + </para>
>> +
>> + </para>
>> +
>> + <para>The following table lists existing JPEG compressed
>> formats.</para> +
>> + <table pgwide="0" frame="none" id="v4l2-mbus-pixelcode-jpeg">
>> + <title>JPEG Formats</title>
>> + <tgroup cols="23">
Oops, looks like I've send wrong patch version. That should read
<tgroup cols="3">
>> + <colspec colname="id" align="left" />
>> + <colspec colname="code" align="left"/>
>> + <colspec colname="remarks" align="left"/>
>> + <thead>
>> + <row>
>> + <entry>Identifier</entry>
>> + <entry>Code</entry>
>> + <entry>Remarks</entry>
>> + </row>
>> + </thead>
>> + <tbody valign="top">
>> + <row id="V4L2-MBUS-FMT-JPEG-1X8">
>> + <entry>V4L2_MBUS_FMT_JPEG_1X8</entry>
>> + <entry>0x4001</entry>
>> + <entry> This format shall be used for of transmission of JPEG
..and s/for of/for
>> + data over MIPI CSI-2 bus with User Defined 8-bit Data types.
>
> JPEG formats are not limited to MIPI, some parallel sensors can transmit JPEG
> as well.
Yes, I am aware of that. One of examples could be the old TCM8240MD sensor.
http://www.sparkfun.com/datasheets/Sensors/Imaging/TCM8240MD_E150405_REV13.pdf
My intention was to indicate that V4L2_MBUS_FMT_JPEG_1X8 format is
the preferred one for "User Defined 8-bit Data Transmission" over
the serial MIPI-CSI link.
I'm not sure if "Remarks" column is needed.
Maybe something like:
...
+ <entry>0x4001</entry>
+ <entry> This format is recommended for transmission of JPEG
+ data over MIPI CSI-2 bus with User Defined 8-bit Data types.
+ <entry>
...
would be better?
--
Regards,
Sylwester
--
Sylwester Nawrocki
Samsung Poland R&D Center
next prev parent reply other threads:[~2011-03-24 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 14:19 [RFC/PATCH] v4l: Add V4L2_MBUS_FMT_JPEG_1X8 media bus format Sylwester Nawrocki
2011-03-24 14:38 ` Laurent Pinchart
2011-03-24 14:58 ` Sylwester Nawrocki [this message]
2011-03-24 16:31 ` Laurent Pinchart
2011-03-25 15:29 ` [RFC/PATCH v2] " Sylwester Nawrocki
2011-03-29 15:11 ` Laurent Pinchart
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=4D8B5BFA.3090205@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=g.liakhovetski@gmx.de \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=riverful.kim@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 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.