From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 8/8] drm/i915/skl: Allow Y (and Yf) frame buffer creation
Date: Fri, 27 Feb 2015 09:45:27 +0000 [thread overview]
Message-ID: <54F03CB7.8040208@linux.intel.com> (raw)
In-Reply-To: <20150226164410.GQ24485@phenom.ffwll.local>
On 02/26/2015 04:44 PM, Daniel Vetter wrote:
> On Wed, Feb 25, 2015 at 04:47:24PM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> By this patch all underlying bits have been implemented and this
>> patch actually enables the feature.
>>
>> v2: Validate passed in fb modifiers to reject garbage. (Daniel Vetter)
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com> (v1)
>> ---
>> drivers/gpu/drm/i915/intel_display.c | 26 +++++++++++++++++++++-----
>> 1 file changed, 21 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index 1d50934..3232ddd 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -12783,6 +12783,19 @@ static int intel_framebuffer_init(struct drm_device *dev,
>> WARN_ON(!mutex_is_locked(&dev->struct_mutex));
>>
>> if (mode_cmd->flags & DRM_MODE_FB_MODIFIERS) {
>> + /* Passed in modifier sanity checking. */
>> + switch (mode_cmd->modifier[0]) {
>> + case DRM_FORMAT_MOD_NONE:
>> + case I915_FORMAT_MOD_X_TILED:
>> + case I915_FORMAT_MOD_Y_TILED:
>> + case I915_FORMAT_MOD_Yf_TILED:
>> + break;
>> + default:
>> + DRM_ERROR("Unsupported fb modifier 0x%llx!\n",
>> + mode_cmd->modifier[0]);
>> + return -EINVAL;
>> + }
>> +
>> /* Enforce that fb modifier and tiling mode match, but only for
>> * X-tiled. This is needed for FBC. */
>> if (!!(obj->tiling_mode == I915_TILING_X) !=
>> @@ -12790,6 +12803,14 @@ static int intel_framebuffer_init(struct drm_device *dev,
>> DRM_DEBUG("tiling_mode doesn't match fb modifier\n");
>> return -EINVAL;
>> }
>> +
>> + if (INTEL_INFO(dev)->gen < 9 &&
>> + (mode_cmd->modifier[0] == I915_FORMAT_MOD_Y_TILED ||
>> + mode_cmd->modifier[0] == I915_FORMAT_MOD_Yf_TILED)) {
>> + DRM_DEBUG("Unsupported tiling 0x%llx!\n",
>> + mode_cmd->modifier[0]);
>> + return -EINVAL;
>> + }
>> } else {
>> if (obj->tiling_mode == I915_TILING_X)
>> mode_cmd->modifier[0] = I915_FORMAT_MOD_X_TILED;
>> @@ -12799,11 +12820,6 @@ static int intel_framebuffer_init(struct drm_device *dev,
>> }
>> }
>>
>> - if (mode_cmd->modifier[0] == I915_FORMAT_MOD_Y_TILED) {
>> - DRM_DEBUG("hardware does not support tiling Y\n");
>> - return -EINVAL;
>> - }
>
> My idea was actually to put the switch here (reduces one indent level) and
> put the per-gen stuff into the switch statement too. I.e.
>
> /* Passed in modifier sanity checking. */
> switch (mode_cmd->modifier[0]) {
> case I915_FORMAT_MOD_Y_TILED:
> case I915_FORMAT_MOD_Yf_TILED:
> if (INTEL_INFO(dev)->gen < 9) {
> DRM_DEBUG("Unsupported tiling 0x%llx!\n",
> mode_cmd->modifier[0]);
> return -EINVAL;
>
> }
> case DRM_FORMAT_MOD_NONE:
> case I915_FORMAT_MOD_X_TILED:
> break;
> default:
> DRM_ERROR("Unsupported fb modifier 0x%llx!\n",
> mode_cmd->modifier[0]);
> return -EINVAL;
> }
>
> That gives us a natural place for extensions later on if we need to add
> more special cases.
Yes I agree this patch being only on v2 was way disproportionate
compared to some others from this series. ;)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-27 9:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:47 [PATCH v4 0/8] Skylake Y tiled scanout Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 1/8] drm/i915/skl: Add new displayable tiling formats Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 2/8] drm/i915/skl: Allow scanning out Y and Yf fbs Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 3/8] drm/i915/skl: Adjust intel_fb_align_height() for Yb/Yf tiling Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 4/8] drm/i915/skl: Teach pin_and_fence_fb_obj() about Y tiling constraints Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 5/8] drm/i915/skl: Adjust get_plane_config() to support Yb/Yf tiling Tvrtko Ursulin
2015-02-26 15:52 ` Damien Lespiau
2015-02-25 16:47 ` [PATCH 6/8] drm/i915/skl: Updated watermark programming Tvrtko Ursulin
2015-02-26 16:45 ` Damien Lespiau
2015-02-27 9:34 ` Tvrtko Ursulin
2015-02-25 16:47 ` [PATCH 7/8] drm/i915/skl: Update watermarks for Y tiling Tvrtko Ursulin
2015-02-26 16:59 ` Damien Lespiau
2015-02-27 9:39 ` Tvrtko Ursulin
2015-02-27 14:24 ` Damien Lespiau
2015-02-25 16:47 ` [PATCH 8/8] drm/i915/skl: Allow Y (and Yf) frame buffer creation Tvrtko Ursulin
2015-02-26 14:55 ` shuang.he
2015-02-26 16:44 ` Daniel Vetter
2015-02-27 9:45 ` Tvrtko Ursulin [this message]
2015-02-27 14:20 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2015-02-27 11:15 [PATCH v5 0/8] Skylake Y tiled scanout Tvrtko Ursulin
2015-02-27 11:15 ` [PATCH 8/8] drm/i915/skl: Allow Y (and Yf) frame buffer creation Tvrtko Ursulin
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=54F03CB7.8040208@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
/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