devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mirela Rabulea (OSS)" <mirela.rabulea@oss.nxp.com>
To: "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>
Cc: dl-linux-imx <linux-imx@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"laurent.pinchart+renesas@ideasonboard.com" 
	<laurent.pinchart+renesas@ideasonboard.com>,
	Aisheng Dong <aisheng.dong@nxp.com>,
	Laurentiu Palcu <laurentiu.palcu@nxp.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Robert Chiras <robert.chiras@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"paul.kocialkowski@bootlin.com" <paul.kocialkowski@bootlin.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"niklas.soderlund+renesas@ragnatech.se" 
	<niklas.soderlund+renesas@ragnatech.se>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	"dafna.hirschfeld@collabora.com" <dafna.hirschfeld@collabora.com>,
	"ezequiel@collabora.com" <ezequiel@collabora.com>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Subject: Re: [EXT] Re: [PATCH v5 07/10] media: Add parsing for APP14 data segment in jpeg helpers
Date: Fri, 4 Dec 2020 14:13:34 +0000	[thread overview]
Message-ID: <2bffcb5a2454dfc2188cc11b0f796f965cc7291e.camel@oss.nxp.com> (raw)
In-Reply-To: <6acf2724130aa2e927cd116ecd216bec3e0321a5.camel@pengutronix.de>

Hi Phipipp,

On Wed, 2020-12-02 at 16:18 +0100, Philipp Zabel wrote:
> 
> Hi Mirela,
> 
> On Thu, 2020-11-12 at 05:05 +0200, Mirela Rabulea (OSS) wrote:
> > From: Mirela Rabulea <mirela.rabulea@nxp.com>
> > 
> > According to Rec. ITU-T T.872 (06/2012) 6.5.3
> > APP14 segment is for color encoding, it contains a transform flag,
> > which
> > may have values of 0, 1 and 2 and are interpreted as follows:
> > 0 - CMYK for images that are encoded with four components
> >   - RGB for images that are encoded with three components
> > 1 - An image encoded with three components using YCbCr colour
> > encoding.
> > 2 - An image encoded with four components using YCCK colour
> > encoding.
> > 
> > This is used in imx-jpeg decoder, to distinguish between
> > YUV444 and RGB24.
> > 
> > Signed-off-by: Mirela Rabulea <mirela.rabulea@nxp.com>
> > ---
> > Changes in v5:
> > This was patch 8 in previous version
> > Replaced a struct for app14 data with just an int, since the
> > transform flag is the only meaningfull information from this
> > segment
> 
> Could we turn this into an enum for the transform flag, and include
> the
> above spec reference in its kerneldoc comment? I think this would be
> better than checking for (app14_tf == <magic_number>) in the drivers.

Appreciate your feedback, for all patches, I'll address it in v6.
Where would be a better place for this enum, v4l2-jpeg.h, or maybe
include/uapi/linux/v4l2-controls.h?

Thanks,
Mirela

> 
> >  drivers/media/v4l2-core/v4l2-jpeg.c | 39
> > +++++++++++++++++++++++++++--
> >  include/media/v4l2-jpeg.h           |  6 +++--
> >  2 files changed, 41 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/media/v4l2-core/v4l2-jpeg.c
> > b/drivers/media/v4l2-core/v4l2-jpeg.c
> > index 8947fd95c6f1..3181ce544f79 100644
> > --- a/drivers/media/v4l2-core/v4l2-jpeg.c
> > +++ b/drivers/media/v4l2-core/v4l2-jpeg.c
> > @@ -45,6 +45,7 @@ MODULE_LICENSE("GPL");
> >  #define DHP  0xffde  /* hierarchical progression */
> >  #define EXP  0xffdf  /* expand reference */
> >  #define APP0 0xffe0  /* application data */
> > +#define APP14        0xffee  /* application data for colour
> > encoding */
> >  #define APP15        0xffef
> >  #define JPG0 0xfff0  /* extensions */
> >  #define JPG13        0xfffd
> > @@ -444,8 +445,37 @@ static int jpeg_skip_segment(struct
> > jpeg_stream *stream)
> >       return jpeg_skip(stream, len - 2);
> >  }
> > 
> > +/* Rec. ITU-T T.872 (06/2012) 6.5.3 */
> > +static int jpeg_parse_app14_data(struct jpeg_stream *stream)
> > +{
> > +     int ret;
> > +     int Lp;
> 
> Let's keep variables lower case.
> 
> > +     int skip;
> > +     int tf;
> > +
> > +     Lp = jpeg_get_word_be(stream);
> > +     if (Lp < 0)
> > +             return Lp;
> 
> Should we check that Ap1 to 6 are actually "Adobe\0"?
> 
> > +     /* get to Ap12 */
> > +     ret = jpeg_skip(stream, 11);
> > +     if (ret < 0)
> > +             return -EINVAL;
> > +
> > +     tf = jpeg_get_byte(stream);
> > +     if (tf < 0)
> > +             return tf;
> > +
> > +     skip = Lp - 2 - 11;
> > +     ret = jpeg_skip(stream, skip);
> > +     if (ret < 0)
> > +             return -EINVAL;
> > +     else
> > +             return tf;
> > +}
> > +
> >  /**
> > - * jpeg_parse_header - locate marker segments and optionally parse
> > headers
> > + * v4l2_jpeg_parse_header - locate marker segments and optionally
> > parse headers
> >   * @buf: address of the JPEG buffer, should start with a SOI
> > marker
> >   * @len: length of the JPEG buffer
> >   * @out: returns marker segment positions and optionally parsed
> > headers
> > @@ -476,6 +506,9 @@ int v4l2_jpeg_parse_header(void *buf, size_t
> > len, struct v4l2_jpeg_header *out)
> >       if (marker != SOI)
> >               return -EINVAL;
> > 
> > +     /* init value to signal if this marker is not present */
> > +     out->app14_tf = -EINVAL;
> > +
> >       /* loop through marker segments */
> >       while ((marker = jpeg_next_marker(&stream)) >= 0) {
> >               switch (marker) {
> > @@ -519,7 +552,9 @@ int v4l2_jpeg_parse_header(void *buf, size_t
> > len, struct v4l2_jpeg_header *out)
> >                       ret = jpeg_parse_restart_interval(&stream,
> >                                                       &out-
> > >restart_interval);
> >                       break;
> > -
> > +             case APP14:
> > +                     out->app14_tf =
> > jpeg_parse_app14_data(&stream);
> > +                     break;
> >               case SOS:
> >                       ret = jpeg_reference_segment(&stream, &out-
> > >sos);
> >                       if (ret < 0)
> > diff --git a/include/media/v4l2-jpeg.h b/include/media/v4l2-jpeg.h
> > index ddba2a56c321..008e0476d928 100644
> > --- a/include/media/v4l2-jpeg.h
> > +++ b/include/media/v4l2-jpeg.h
> > @@ -100,10 +100,11 @@ struct v4l2_jpeg_scan_header {
> >   *                  order, optional
> >   * @restart_interval: number of MCU per restart interval, Ri
> >   * @ecs_offset: buffer offset in bytes to the entropy coded
> > segment
> > + * @app14_tf: transform flag from app14 data
> >   *
> >   * When this structure is passed to v4l2_jpeg_parse_header, the
> > optional scan,
> > - * quantization_tables, and huffman_tables pointers must be
> > initialized to NULL
> > - * or point at valid memory.
> > + * quantization_tables and huffman_tables pointers must be
> > initialized
> > + * to NULL or point at valid memory.
> 
> Unnecessary, unrelated change? I'd drop this.
> 
> >   */
> >  struct v4l2_jpeg_header {
> >       struct v4l2_jpeg_reference sof;
> > @@ -119,6 +120,7 @@ struct v4l2_jpeg_header {
> >       struct v4l2_jpeg_reference *huffman_tables;
> >       u16 restart_interval;
> >       size_t ecs_offset;
> > +     int app14_tf;
> >  };
> > 
> >  int v4l2_jpeg_parse_header(void *buf, size_t len, struct
> > v4l2_jpeg_header *out);
> 
> regards
> Philipp

  reply	other threads:[~2020-12-04 14:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  3:05 [PATCH v5 00/10] Add V4L2 driver for i.MX8 JPEG Encoder/Decoder Mirela Rabulea (OSS)
2020-11-12  3:05 ` [PATCH v5 01/10] media: v4l: Add packed YUV444 24bpp pixel format Mirela Rabulea (OSS)
2020-11-12  3:05 ` [PATCH v5 02/10] firmware: imx: scu-pd: Add power domains for imx-jpeg Mirela Rabulea (OSS)
2020-11-16  8:26   ` Shawn Guo
2020-11-12  3:05 ` [PATCH v5 03/10] media: dt-bindings: Add bindings for i.MX8QXP/QM JPEG driver Mirela Rabulea (OSS)
2020-11-16 19:18   ` Rob Herring
2020-11-12  3:05 ` [PATCH v5 04/10] media: imx-jpeg: Add V4L2 driver for i.MX8 JPEG Encoder/Decoder Mirela Rabulea (OSS)
2020-11-12  3:05 ` [PATCH v5 05/10] arm64: dts: imx8qxp: Add jpeg encoder/decoder nodes Mirela Rabulea (OSS)
2020-11-12  8:36   ` Ezequiel Garcia
2020-11-13 16:12     ` [EXT] " Mirela Rabulea (OSS)
2020-11-12  3:05 ` [PATCH v5 06/10] Add maintainer for IMX jpeg v4l2 driver Mirela Rabulea (OSS)
2020-11-12  3:05 ` [PATCH v5 07/10] media: Add parsing for APP14 data segment in jpeg helpers Mirela Rabulea (OSS)
2020-11-24 15:27   ` Mirela Rabulea
2020-12-02 15:18   ` Philipp Zabel
2020-12-04 14:13     ` Mirela Rabulea (OSS) [this message]
2020-12-04 14:32       ` [EXT] " Philipp Zabel
2020-11-12  3:05 ` [PATCH v5 08/10] media: Quit parsing stream if doesn't start with SOI Mirela Rabulea (OSS)
2020-12-02 15:18   ` Philipp Zabel
2020-11-12  3:05 ` [PATCH v5 09/10] media: Avoid parsing quantization and huffman tables Mirela Rabulea (OSS)
2020-12-02 12:12   ` Hans Verkuil
2020-12-02 15:30     ` Philipp Zabel
2020-12-02 15:22   ` Philipp Zabel
2020-11-12  3:05 ` [PATCH v5 10/10] media: imx-jpeg: Use v4l2 jpeg helpers in mxc-jpeg Mirela Rabulea (OSS)
2020-12-02 15:41   ` Philipp Zabel

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=2bffcb5a2454dfc2188cc11b0f796f965cc7291e.camel@oss.nxp.com \
    --to=mirela.rabulea@oss.nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=dafna.hirschfeld@collabora.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurentiu.palcu@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=robert.chiras@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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).