From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Dave Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2] drm/i915: correct the pitch check for NV12 framebuffer
Date: Wed, 12 Dec 2018 23:15:29 +0200 [thread overview]
Message-ID: <20181212211529.GG9144@intel.com> (raw)
In-Reply-To: <CAKMK7uERO41TiF3X-szKjNAq42UVuGA_dW8FViaCAUeXbW70Lw@mail.gmail.com>
On Wed, Dec 12, 2018 at 09:33:49PM +0100, Daniel Vetter wrote:
> On Wed, Dec 12, 2018 at 9:24 PM Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
> >
> > On Tue, Dec 11, 2018 at 04:39:05PM -0800, Dongseong Hwang wrote:
> > > framebuffer for NV12 requires the pitch to the multiplier of 4, instead
> > > of the width. This patch corrects it.
> > >
> > > For instance, a 480p video, whose width and pitch are 854 and 896
> > > respectively, is excluded for NV12 plane so far.
> > >
> > > Signed-off-by: Dongseong Hwang <dongseong.hwang@intel.com>
> > > Cc: Chandra Konduru <chandra.konduru@intel.com>
> > > Cc: Vidya Srinivas <vidya.srinivas@intel.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> > > ---
> > > drivers/gpu/drm/i915/intel_display.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > index 13e5650..8a3de12 100644
> > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > @@ -14600,7 +14600,7 @@ static int intel_framebuffer_init(struct intel_framebuffer *intel_fb,
> > > if (fb->format->format == DRM_FORMAT_NV12 &&
> > > (fb->width < SKL_MIN_YUV_420_SRC_W ||
> > > fb->height < SKL_MIN_YUV_420_SRC_H ||
> > > - (fb->width % 4) != 0 || (fb->height % 4) != 0)) {
> > > + (fb->pitches[0] % 4) != 0 || (fb->height % 4) != 0)) {
> >
> > The stride can never be misaligned like that. It'll be at least tile
> > aligned, or 64 byte aligned with linear buffers.
> >
> > Anyways this entire piece of code doesn't make too much sense. The fb
> > size doesn't really matter for us, only the src viewport size matters.
> > That one we limit to a minimum of 2x2 pixels w/o scaling, and 16x16
> > pixems w/ scaling. So looks like this code can be just ripped out.
>
> Do we have igt testcases for these cornercases in igt? Obviously would
> need to be intel specific subtests ...
Can't spot anything quite that specific. Someone would need to write
one I suppose. Also Imre has a test somewhere on the list for testing
the plane clipping underrun fails which tests small src viewport sizes,
and JP has been working on a rotation vs. clipping test that is also
somewhat related. Not sure if we could combine any of these somehow
to avoid having too many similar tests.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-12 21:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 0:39 [PATCH v2] drm/i915: correct the pitch check for NV12 framebuffer Dongseong Hwang
2018-12-12 1:06 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-12-12 4:59 ` ✓ Fi.CI.IGT: " Patchwork
2018-12-12 20:24 ` [PATCH v2] " Ville Syrjälä
2018-12-12 20:33 ` Daniel Vetter
2018-12-12 21:15 ` Ville Syrjälä [this message]
2018-12-12 21:18 ` [Intel-gfx] " Singaiah Chintalapudi
2018-12-13 0:51 ` Hwang, Dongseong
2018-12-19 8:29 ` [PATCH v3] " raviraj.p.sitaram
2019-01-22 16:39 ` Sitaram, Raviraj P
2019-01-25 21:34 ` Ville Syrjälä
2018-12-19 9:19 ` ✓ Fi.CI.BAT: success for drm/i915: correct the pitch check for NV12 framebuffer (rev2) Patchwork
2018-12-19 10:51 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-23 6:53 ` ✓ Fi.CI.BAT: success for drm/i915: correct the pitch check for NV12 framebuffer (rev3) Patchwork
2019-01-23 9:55 ` ✓ Fi.CI.IGT: " Patchwork
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=20181212211529.GG9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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.