From: Mahesh Kumar <mahesh1.kumar@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, paulo.r.zanoni@intel.com,
maarten.lankhorst@intel.com
Subject: Re: [PATCH v3 1/2] drm/i915/skl+: Check for supported plane configuration in Interlace mode
Date: Wed, 5 Jul 2017 12:09:19 +0530 [thread overview]
Message-ID: <f268a691-583a-f959-89a3-731479ffcad3@intel.com> (raw)
In-Reply-To: <20170704144124.GM12629@intel.com>
Hi,
On Tuesday 04 July 2017 08:11 PM, Ville Syrjälä wrote:
> On Mon, Jul 03, 2017 at 09:28:00PM +0530, Mahesh Kumar wrote:
>> Hi,
>>
>>
>> On Monday 03 July 2017 07:32 PM, Ville Syrjälä wrote:
>>> On Sat, Jul 01, 2017 at 09:35:12AM +0530, Mahesh Kumar wrote:
>>>> Hi,
>>>>
>>>>
>>>> On Friday 30 June 2017 05:56 PM, Ville Syrjälä wrote:
>>>>> On Fri, Jun 30, 2017 at 05:40:59PM +0530, Mahesh Kumar wrote:
>>>>>> In Gen9 platform Interlaced fetch mode doesn't support following plane
>>>>>> configuration:
>>>>>> - Y/Yf tiling
>>>>>> - 90/270 rotation
>>>>> The rotation check seems to be missing from the code?
>>>> 90/270 rotation require Y/Yf tiling, so that will be automagically
>>>> handled as Y-tile case.
>>> Right. OK, series lgtm
>>> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>>
>>> Was there a bugzilla link we should include in these patches?
>> following is bugzilla link for the issue.
>> https://bugs.freedesktop.org/show_bug.cgi?id=90238
> Added that, and pushed the series to dinq. Thanks for the patches.
>
> I had to fix a small checkpatch complaint while applying. Plase always
> review the checkpatch warnings when submitting patches.
ok sure, will start reviewing checkpatch warnings.
thanks for review,
Do we need to push these patches to "stable" as well?
for enabling PF-ID Interlace mode what should be the approach?
Should we always enable PF-ID in GEN9+, or should we create property to
select the fetching mode?
for property based implementation who will be the user-space consumer
for property?
Please let me know your thoughts on that.
thanks,
-Mahesh
>
>> -Mahesh
>>>> -Mahesh
>>>>>> - YUV420 hybrid planar source pixel formats.
>>>>>>
>>>>>> This patch adds check to fail the flip if any of the above configuration
>>>>>> is requested.
>>>>>>
>>>>>> Changes since V1:
>>>>>> - handle checks in intel_plane_atomic_check_with_state (ville)
>>>>>> - takeout plane scaler checks combile with pipe scaler in next patch
>>>>>> Changes since V2:
>>>>>> - No need to check for NV12 as it need scaling, so it will be rejected
>>>>>> by scaling check (ville)
>>>>>>
>>>>>> Signed-off-by: Mahesh Kumar <mahesh1.kumar@intel.com>
>>>>>> ---
>>>>>> drivers/gpu/drm/i915/intel_atomic_plane.c | 15 +++++++++++++++
>>>>>> 1 file changed, 15 insertions(+)
>>>>>>
>>>>>> diff --git a/drivers/gpu/drm/i915/intel_atomic_plane.c b/drivers/gpu/drm/i915/intel_atomic_plane.c
>>>>>> index 4325cb0a04f5..ee76fab7bb6f 100644
>>>>>> --- a/drivers/gpu/drm/i915/intel_atomic_plane.c
>>>>>> +++ b/drivers/gpu/drm/i915/intel_atomic_plane.c
>>>>>> @@ -114,6 +114,8 @@ int intel_plane_atomic_check_with_state(struct intel_crtc_state *crtc_state,
>>>>>> struct drm_i915_private *dev_priv = to_i915(plane->dev);
>>>>>> struct drm_plane_state *state = &intel_state->base;
>>>>>> struct intel_plane *intel_plane = to_intel_plane(plane);
>>>>>> + const struct drm_display_mode *adjusted_mode =
>>>>>> + &crtc_state->base.adjusted_mode;
>>>>>> int ret;
>>>>>>
>>>>>> /*
>>>>>> @@ -173,6 +175,19 @@ int intel_plane_atomic_check_with_state(struct intel_crtc_state *crtc_state,
>>>>>> if (ret)
>>>>>> return ret;
>>>>>>
>>>>>> + /*
>>>>>> + * Y-tiling is not supported in IF-ID Interlace mode in
>>>>>> + * GEN9 and above.
>>>>>> + */
>>>>>> + if (state->fb && INTEL_GEN(dev_priv) >= 9 && crtc_state->base.enable &&
>>>>>> + adjusted_mode->flags & DRM_MODE_FLAG_INTERLACE) {
>>>>>> + if (state->fb->modifier == I915_FORMAT_MOD_Y_TILED ||
>>>>>> + state->fb->modifier == I915_FORMAT_MOD_Yf_TILED) {
>>>>>> + DRM_DEBUG_KMS("Y/Yf tiling not supported in IF-ID mode\n");
>>>>>> + return -EINVAL;
>>>>>> + }
>>>>>> + }
>>>>>> +
>>>>>> /* FIXME pre-g4x don't work like this */
>>>>>> if (intel_state->base.visible)
>>>>>> crtc_state->active_planes |= BIT(intel_plane->id);
>>>>>> --
>>>>>> 2.13.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-07-05 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 12:10 [PATCH v3 0/2] Handle unsupported configuration with IF-ID Mahesh Kumar
2017-06-30 12:10 ` [PATCH v3 1/2] drm/i915/skl+: Check for supported plane configuration in Interlace mode Mahesh Kumar
2017-06-30 12:26 ` Ville Syrjälä
2017-07-01 4:05 ` Mahesh Kumar
2017-07-03 14:02 ` Ville Syrjälä
2017-07-03 15:58 ` Mahesh Kumar
2017-07-04 14:41 ` Ville Syrjälä
2017-07-05 6:39 ` Mahesh Kumar [this message]
2017-07-05 10:13 ` Ville Syrjälä
2017-06-30 12:11 ` [PATCH v3 2/2] drm/i915/skl+: Scaling not supported in IF-ID " Mahesh Kumar
2017-06-30 12:59 ` ✗ Fi.CI.BAT: failure for Handle unsupported configuration with IF-ID (rev3) Patchwork
2017-07-03 16:37 ` ✓ Fi.CI.BAT: success " Patchwork
2017-07-17 7:26 ` [PATCH v3 0/2] Handle unsupported configuration with IF-ID Daniel Vetter
2017-07-18 12:42 ` Mahesh Kumar
2017-07-19 8:22 ` Lankhorst, Maarten
2017-07-19 8:51 ` Daniel Vetter
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=f268a691-583a-f959-89a3-731479ffcad3@intel.com \
--to=mahesh1.kumar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=paulo.r.zanoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).