From: Daniel Vetter <daniel@ffwll.ch>
To: Chandra Konduru <chandra.konduru@intel.com>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
ville.syrjala@intel.com
Subject: Re: [PATCH 08/12] drm/i915: Add NV12 support to intel_framebuffer_init
Date: Tue, 19 May 2015 10:24:01 +0200 [thread overview]
Message-ID: <20150519082401.GJ15256@phenom.ffwll.local> (raw)
In-Reply-To: <1431925865-7637-9-git-send-email-chandra.konduru@intel.com>
On Sun, May 17, 2015 at 10:11:01PM -0700, Chandra Konduru wrote:
> This patch adds NV12 as supported format to
> intel_framebuffer_init and performs various checks.
>
> Signed-off-by: Chandra Konduru <chandra.konduru@intel.com>
> Testcase: igt/kms_nv12
> ---
> drivers/gpu/drm/i915/intel_display.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 42924a6..41cd26f 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -14043,6 +14043,33 @@ static int intel_framebuffer_init(struct drm_device *dev,
> return -EINVAL;
> }
> break;
> + case DRM_FORMAT_NV12:
> + if (INTEL_INFO(dev)->gen < 9) {
> + DRM_DEBUG("unsupported pixel format: %s\n",
> + drm_get_format_name(mode_cmd->pixel_format));
> + return -EINVAL;
> + }
> + if (!mode_cmd->offsets[1]) {
> + DRM_DEBUG("uv start offset not set\n");
> + return -EINVAL;
> + }
Nope. It's perfectly ok to have NV12 with a 0 offset for the uv plane, if
it's e.g. in a separate buffer object. Which is the part this series seems
to be completely missing - there's no code at all to look up (and store in
intel_framebuffer the 2nd i915_bo pointer) the 2nd buffer handle afaics.
You should also change your igts to use 2 separate buffers, just for test
coverage.
-Daniel
> + if (mode_cmd->pitches[0] != mode_cmd->pitches[1] ||
> + mode_cmd->handles[0] != mode_cmd->handles[1]) {
> + DRM_DEBUG("y and uv subplanes have different parameters\n");
> + return -EINVAL;
> + }
> + if (mode_cmd->modifier[1] == I915_FORMAT_MOD_Yf_TILED &&
> + (mode_cmd->offsets[1] & 0xFFF)) {
> + DRM_DEBUG("tile-Yf uv offset 0x%x isn't starting on new tile-row\n",
> + mode_cmd->offsets[1]);
> + return -EINVAL;
> + }
> + if (mode_cmd->modifier[1] == I915_FORMAT_MOD_Y_TILED &&
> + ((mode_cmd->offsets[1] % mode_cmd->pitches[1]) % 4)) {
> + DRM_DEBUG("tile-Y uv offset 0x%x isn't 4-line aligned\n",
> + mode_cmd->offsets[1]);
> + }
> + break;
> default:
> DRM_DEBUG("unsupported pixel format: %s\n",
> drm_get_format_name(mode_cmd->pixel_format));
> --
> 1.7.9.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-19 8:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 5:10 [PATCH 00/12] drm/i915: Adding NV12 for skylake display Chandra Konduru
2015-05-18 5:10 ` [PATCH 01/12] drm/i915: Add register definitions for NV12 support Chandra Konduru
2015-05-18 5:10 ` [PATCH 02/12] drm/i915: Set scaler mode for NV12 Chandra Konduru
2015-05-18 5:10 ` [PATCH 03/12] drm/i915: Stage scaler request for NV12 as src format Chandra Konduru
2015-05-21 11:27 ` Ville Syrjälä
2015-05-21 16:24 ` Konduru, Chandra
2015-05-21 16:49 ` Ville Syrjälä
2015-05-18 5:10 ` [PATCH 04/12] drm/i915: Update format_is_yuv() to include NV12 Chandra Konduru
2015-05-21 11:29 ` Ville Syrjälä
2015-05-18 5:10 ` [PATCH 05/12] drm/i915: Upscale scaler max scale for NV12 Chandra Konduru
2015-05-18 5:10 ` [PATCH 06/12] drm/i915: Add NV12 as supported format for primary plane Chandra Konduru
2015-05-18 5:11 ` [PATCH 07/12] drm/i915: Add NV12 as supported format for sprite plane Chandra Konduru
2015-05-18 5:11 ` [PATCH 08/12] drm/i915: Add NV12 support to intel_framebuffer_init Chandra Konduru
2015-05-19 8:24 ` Daniel Vetter [this message]
2015-05-19 16:31 ` Konduru, Chandra
2015-05-20 7:36 ` Daniel Vetter
2015-05-21 0:31 ` Konduru, Chandra
2015-05-21 9:33 ` Daniel Vetter
2015-05-21 16:11 ` Konduru, Chandra
2015-05-21 17:34 ` Runyan, Arthur J
2015-05-22 19:06 ` Runyan, Arthur J
2015-05-18 5:11 ` [PATCH 09/12] drm/i915: Enable NV12 primary plane via crtc set config Chandra Konduru
2015-05-18 5:11 ` [PATCH 10/12] drm/i915: Add NV12 to primary plane programming Chandra Konduru
2015-05-18 5:11 ` [PATCH 11/12] drm/i915: Add NV12 to sprite " Chandra Konduru
2015-05-18 5:11 ` [PATCH 12/12] drm/i915: Add 90/270 rotation for NV12 format Chandra Konduru
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=20150519082401.GJ15256@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chandra.konduru@intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox