From: Martin Peres <martin.peres@free.fr>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH RFC] drm/i915: reduce cursor size for GEN5 hardware
Date: Tue, 7 Feb 2017 17:03:09 +0200 [thread overview]
Message-ID: <781c5548-c87d-7be1-f18d-1b1d86b5eb74@free.fr> (raw)
In-Reply-To: <fc474e55-573d-e363-9e6e-eabd4a54d79f@kleine-koenig.org>
On 07/02/17 15:22, Uwe Kleine-König wrote:
> Hello,
>
> On 02/01/2017 03:37 PM, Ville Syrjälä wrote:
>> On Wed, Feb 01, 2017 at 01:41:08PM +0100, Maarten Lankhorst wrote:
>>> Op 31-01-17 om 20:13 schreef Uwe Kleine-König:
>>>> On Tue, Jan 31, 2017 at 10:03:26AM +0100, Maarten Lankhorst wrote:
>>>>> Op 31-01-17 om 09:09 schreef Uwe Kleine-König:
>>>>> Just curious, does this help?
>>>>>
>>>>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>>>>> index ae2c0bb4b2e8..13de4c526ca6 100644
>>>>> --- a/drivers/gpu/drm/i915/intel_pm.c
>>>>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>>>>> @@ -1838,7 +1838,7 @@ static uint32_t ilk_compute_cur_wm(const struct intel_crtc_state *cstate,
>>>>> * this is necessary to avoid flickering.
>>>>> */
>>>>> int cpp = 4;
>>>>> - int width = pstate->base.visible ? pstate->base.crtc_w : 64;
>>>>> + int width = 256;
>>>>>
>>>>> if (!cstate->base.active)
>>>>> return 0;
>>>>>
>>>> On a kernel with this patch applied I cannot reproduce the flickering. I
>>>> keep that kernel running but expect that it also fixes the crash.
>>>
>>> Ok that's good news.
>>>
>>> Maybe ville or matt can comment whether this patch is the right fix?
>>
>> Well, it's just extending the hack even further. The right fix would be
>> to fix the wm programming sequence to respect the frame boundaries
>> correctly (ie. my old vblank based wm stuff).
>
> so I wonder how this goes forward. The situation seems to be well
> understood, but other than testing patches I don't know what to do (and
> there is currently no patch to test).
>
> Best regards
> Uwe
>
The way I understand this is that no-one wants to restrict the
capabilities exposed by the kernel and would like a proper fix for this.
However, I agree with Uwe, given the low priority status of Gen5 (people
would rather work on hw that is used by a lot of people), we should
probably accept the patch proposed by Maarten as it fixes someone's
workflow and does not regress anything meaningful.
The proper fix for watermark computation can be worked on as time
permits, later on.
Again, I would like to thanks Uwe for pushing hard for this, we are
definitely not active-enough on this issue, flashing screens should be a
big NO-NO, yet we seem to be OK with it :s
Martin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-07 15:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 8:09 [PATCH RFC] drm/i915: reduce cursor size for GEN5 hardware Uwe Kleine-König
2017-01-31 9:03 ` Maarten Lankhorst
2017-01-31 19:13 ` Uwe Kleine-König
2017-02-01 12:41 ` Maarten Lankhorst
2017-02-01 14:37 ` Ville Syrjälä
2017-02-07 13:22 ` Uwe Kleine-König
2017-02-07 15:03 ` Martin Peres [this message]
2017-02-07 15:35 ` Ville Syrjälä
2017-02-07 17:51 ` Maarten Lankhorst
2017-02-07 17:58 ` Ville Syrjälä
2017-02-17 11:10 ` Uwe Kleine-König
2017-02-17 15:01 ` [PATCH] drm/i915: Fix legacy cursor vs. watermarks for ILK-BDW ville.syrjala
2017-02-17 20:04 ` Uwe Kleine-König
2017-02-17 20:18 ` Ville Syrjälä
2017-02-20 9:04 ` Maarten Lankhorst
2017-02-20 13:38 ` Ville Syrjälä
2017-02-20 14:30 ` Maarten Lankhorst
2017-02-24 13:11 ` Ville Syrjälä
2017-02-25 15:31 ` Maarten Lankhorst
2017-03-02 14:58 ` Ville Syrjälä
2017-03-21 13:42 ` Ander Conselvan De Oliveira
2017-03-21 14:43 ` Ville Syrjälä
2017-01-31 9:25 ` ✗ Fi.CI.BAT: warning for drm/i915: reduce cursor size for GEN5 hardware Patchwork
2017-02-17 17:52 ` ✓ Fi.CI.BAT: success for drm/i915: reduce cursor size for GEN5 hardware (rev4) 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=781c5548-c87d-7be1-f18d-1b1d86b5eb74@free.fr \
--to=martin.peres@free.fr \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=uwe@kleine-koenig.org \
--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.