All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konduru, Chandra" <chandra.konduru@intel.com>
To: "Runyan, Arthur J" <arthur.j.runyan@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: Add 90/270 rotation for NV12 format.
Date: Tue, 19 May 2015 23:12:43 +0000	[thread overview]
Message-ID: <76A9B330A4D78C4D99CB292C4CC06C0E36FE665F@fmsmsx101.amr.corp.intel.com> (raw)
In-Reply-To: <C7E999358BBE9E45938BA940F5F5110875787D62@fmsmsx116.amr.corp.intel.com>



> -----Original Message-----
> From: Runyan, Arthur J
> Sent: Monday, May 18, 2015 12:19 PM
> To: Konduru, Chandra; Ville Syrjälä
> Cc: intel-gfx@lists.freedesktop.org; Vetter, Daniel; Syrjala, Ville; Jindal, Sonika
> Subject: RE: [Intel-gfx] [PATCH 2/2] drm/i915: Add 90/270 rotation for NV12
> format.
> 
> The statement is correct - " the X offset must always be even for YUV422+NV12,
> and the Y offset must be even when rotated 90/270 degrees."

Thanks Art.
Then below code to take care evenness for both X and Y offsets when YUV 90/270 
is ok.

Ville, with this, can you give R-b tag on the ones you reviewed? 

> 
> >From: Konduru, Chandra
> >> From: Runyan, Arthur J
> >>
> >> I'll take a look.
> >
> >Art, Any update to close on this?
> >
> >[snip]
> >
> >> > > > @@ -13144,6 +13149,10 @@ intel_check_primary_plane(struct
> >> > > > drm_plane
> >> > > *plane,
> >> > > >  	if (fb && format_is_yuv(fb->pixel_format)) {
> >> > > >  		src->x1 &= ~0x10000;
> >> > > >  		src->x2 &= ~0x10000;
> >> > > > +		if (intel_rotation_90_or_270(state->base.rotation)) {
> >> > > > +			src->y1 &= ~0x10000;
> >> > > > +			src->y2 &= ~0x10000;
> >> > > > +		}
> >> > >
> >> > > This feels fishy. Why do we need to make the Y coordinates even? The
> >> > > reson for making the X coordinates even is to make them macropixel
> >> > > aligned, but there are no macropixels in the Y direction so this
> >> > > doesn't make much sense to me.
> >> >
> >> > Hi Ville,
> >> > Per skl spec, it is expecting even lines aligned with 90/270 rotation
> >> > not only for NV12 but also for 422 formats. Perhaps we might have
> >> > missed when 90/270 enabled for packed YUV formats.
> >>
> >> The src coordinates are always in the fb orientation, so macropixels appear in
> >> the src.x direction only. And when we do 90/270 rotation the hardware Y
> offset
> >> comes from src.x coordinates.
> >>
> >> The spec does seem a bit confused though; It claims the X offset must always
> be
> >> even for YUV422+NV12, and the Y offset must be even when rotated 90/270
> >> degrees. I suspect the X offset text just didn't get updated when 90/270
> rotation
> >> was added.
> >>
> >> Art, can you confirm?
> >>
> >> --
> >> Ville Syrjälä
> >> Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-05-19 23:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09  3:22 [PATCH 0/2] Add NV12 90/270 support for skl planes Chandra Konduru
2015-05-09  3:22 ` [PATCH 1/2] drm/i915: call intel_tile_height with correct parameter Chandra Konduru
2015-05-11  9:41   ` Tvrtko Ursulin
2015-05-11 10:28   ` Daniel Vetter
2015-05-09  3:22 ` [PATCH 2/2] drm/i915: Add 90/270 rotation for NV12 format Chandra Konduru
2015-05-11 12:03   ` Ville Syrjälä
2015-05-11 23:32     ` Konduru, Chandra
2015-05-12 10:44       ` Ville Syrjälä
2015-05-12 19:26         ` Runyan, Arthur J
2015-05-15 21:58           ` Konduru, Chandra
2015-05-18 19:19             ` Runyan, Arthur J
2015-05-19 23:12               ` Konduru, Chandra [this message]
2015-05-20 12:27               ` Ville Syrjälä
2015-05-22 18:07                 ` Runyan, Arthur J
2015-05-22 18:28                   ` Ville Syrjälä

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=76A9B330A4D78C4D99CB292C4CC06C0E36FE665F@fmsmsx101.amr.corp.intel.com \
    --to=chandra.konduru@intel.com \
    --cc=arthur.j.runyan@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@intel.com \
    --cc=ville.syrjala@linux.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.