From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Damian Hobson-Garcia <dhobsong@igel.co.jp>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Yoshihiro Kaneko <ykaneko0929@gmail.com>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC] v4l: vsp1: Align crop rectangle to even boundary for YUV formats
Date: Thu, 18 Jun 2015 20:18:12 +0000 [thread overview]
Message-ID: <9503303.Op9lV3ecnM@avalon> (raw)
In-Reply-To: <5559A030.4030301@igel.co.jp>
Hi Damian,
On Monday 18 May 2015 17:17:52 Damian Hobson-Garcia wrote:
> On 2015-05-04 7:13 AM, Laurent Pinchart wrote:
> > On Thursday 30 April 2015 14:22:02 Sergei Shtylyov wrote:
> >> On 4/29/2015 8:05 PM, Yoshihiro Kaneko wrote:
> >>> From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
> >>>
> >>> Make sure that there are valid values in the crop rectangle to ensure
> >>> that the color plane doesn't get shifted when cropping.
> >>> Since there is no distintion between 12bit and 16bit YUV formats in
> >>
> >> Вistinсtion.
> >>
> >>> at the subdev level, use the more restrictive 12bit limits for all YUV
> >>> formats.
> >
> > I would like to mention in the commit message that only the top coordinate
> > constraints differ between the YUV formats, as the subsampling coefficient
> > is always two in the horizontal direction.
>
> I believe that the height value has the same constraint as the top.
Sure, I meant only the vertical coordinates, sorry.
> > Do you foresee a use case for odd cropping top coordinates ?
>
> There might be a case when you're blending surfaces together and one
> extends beyond the boundary of the other and you want to clip away the
> non-overlapping portions.
Let's wait until someone requests support for that use case :-)
> >>> if (rwpf->entity.type = VSP1_ENTITY_WPF) {
> >>> - sel->r.left = min_t(unsigned int, sel->r.left, 255);
> >>> - sel->r.top = min_t(unsigned int, sel->r.top, 255);
> >>> + int maxcrop > >
> > I would declare maxcrop as an unsigned int.
> >
> >>> + format->code = MEDIA_BUS_FMT_AYUV8_1X32 ? 254 : 255;
> >>
> >> I think you need an empty line here.
> >>
> >>> + sel->r.left = min_t(unsigned int, sel->r.left, maxcrop);
> >>> + sel->r.top = min_t(unsigned int, sel->r.top, maxcrop);
> >
> > Is this needed ? Based on what I understand from the datasheet the WPF
> > crops the image before passing it to the DMA engine. At that point YUV
> > data isn't subsampled, so it looks like we don't need to restrict the
> > left and top to even values.
>
> I think that you're correct. There is no subsampling at this stage in
> the pipeline so the maxcrop setting should be fine at 255 regardless of
> the format.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Damian Hobson-Garcia <dhobsong@igel.co.jp>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Yoshihiro Kaneko <ykaneko0929@gmail.com>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC] v4l: vsp1: Align crop rectangle to even boundary for YUV formats
Date: Thu, 18 Jun 2015 23:18:12 +0300 [thread overview]
Message-ID: <9503303.Op9lV3ecnM@avalon> (raw)
In-Reply-To: <5559A030.4030301@igel.co.jp>
Hi Damian,
On Monday 18 May 2015 17:17:52 Damian Hobson-Garcia wrote:
> On 2015-05-04 7:13 AM, Laurent Pinchart wrote:
> > On Thursday 30 April 2015 14:22:02 Sergei Shtylyov wrote:
> >> On 4/29/2015 8:05 PM, Yoshihiro Kaneko wrote:
> >>> From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
> >>>
> >>> Make sure that there are valid values in the crop rectangle to ensure
> >>> that the color plane doesn't get shifted when cropping.
> >>> Since there is no distintion between 12bit and 16bit YUV formats in
> >>
> >> Вistinсtion.
> >>
> >>> at the subdev level, use the more restrictive 12bit limits for all YUV
> >>> formats.
> >
> > I would like to mention in the commit message that only the top coordinate
> > constraints differ between the YUV formats, as the subsampling coefficient
> > is always two in the horizontal direction.
>
> I believe that the height value has the same constraint as the top.
Sure, I meant only the vertical coordinates, sorry.
> > Do you foresee a use case for odd cropping top coordinates ?
>
> There might be a case when you're blending surfaces together and one
> extends beyond the boundary of the other and you want to clip away the
> non-overlapping portions.
Let's wait until someone requests support for that use case :-)
> >>> if (rwpf->entity.type == VSP1_ENTITY_WPF) {
> >>> - sel->r.left = min_t(unsigned int, sel->r.left, 255);
> >>> - sel->r.top = min_t(unsigned int, sel->r.top, 255);
> >>> + int maxcrop =
> >
> > I would declare maxcrop as an unsigned int.
> >
> >>> + format->code == MEDIA_BUS_FMT_AYUV8_1X32 ? 254 : 255;
> >>
> >> I think you need an empty line here.
> >>
> >>> + sel->r.left = min_t(unsigned int, sel->r.left, maxcrop);
> >>> + sel->r.top = min_t(unsigned int, sel->r.top, maxcrop);
> >
> > Is this needed ? Based on what I understand from the datasheet the WPF
> > crops the image before passing it to the DMA engine. At that point YUV
> > data isn't subsampled, so it looks like we don't need to restrict the
> > left and top to even values.
>
> I think that you're correct. There is no subsampling at this stage in
> the pipeline so the maxcrop setting should be fine at 255 regardless of
> the format.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-06-18 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 17:05 [PATCH/RFC] v4l: vsp1: Align crop rectangle to even boundary for YUV formats Yoshihiro Kaneko
2015-04-29 17:05 ` Yoshihiro Kaneko
2015-04-30 11:22 ` Sergei Shtylyov
2015-04-30 11:22 ` Sergei Shtylyov
2015-04-30 11:44 ` Geert Uytterhoeven
2015-04-30 11:44 ` Geert Uytterhoeven
2015-04-30 12:00 ` Sergei Shtylyov
2015-04-30 12:00 ` Sergei Shtylyov
2015-05-03 22:13 ` Laurent Pinchart
2015-05-03 22:13 ` Laurent Pinchart
2015-05-18 8:17 ` Damian Hobson-Garcia
2015-05-18 8:17 ` Damian Hobson-Garcia
2015-06-18 20:18 ` Laurent Pinchart [this message]
2015-06-18 20:18 ` 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=9503303.Op9lV3ecnM@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dhobsong@igel.co.jp \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ykaneko0929@gmail.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.