From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"Lee, Shawn C" <shawn.c.lee@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Lee@freedesktop.org
Subject: Re: [PATCH] drm/i915: optimzie eDP 1.4 config
Date: Wed, 05 Sep 2018 12:58:17 +0300 [thread overview]
Message-ID: <87wos01d1i.fsf@intel.com> (raw)
In-Reply-To: <153607131647.2853.8468028082757051432@skylake-alporthouse-com>
On Tue, 04 Sep 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Lee, Shawn C (2018-09-04 15:55:41)
>> eDP 1.4 introduce a new link rates flexibility and selection.
>> It provided system specific link rate optimization and power
>> efficiency. We should keep eDP 1.3 and older version to use
>> max link rate approach to avoid any side effect. And eDP 1.4
>> used the optimization link rate and lane count setting.
>>
>> Cc: Matt Atwood <matthew.s.atwood@intel.com>
>> Signed-off-by: Lee, Shawn C <shawn.c.lee@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 436c22de33b6..903d640fe712 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -1953,8 +1953,10 @@ intel_dp_compute_link_config(struct intel_encoder *encoder,
>> * configuration, and typically these values correspond to the
>> * native resolution of the panel.
>> */
>
> Having just finished a comment explaining why we override the limits for
> eDP, the following logic is confusing without at least a mention above.
I think the proper approach with the appropriate explanations is [1]. I
think it's harmful to start optimizing on eDP 1.4 without also
optimizing for fast and narrow link per spec at the same time.
BR,
Jani.
[1] http://patchwork.freedesktop.org/patch/msgid/20180905095321.13843-1-jani.nikula@intel.com
>
>> - limits.min_lane_count = limits.max_lane_count;
>> - limits.min_clock = limits.max_clock;
>> + if (intel_dp->edp_dpcd[0] <= DP_EDP_13) {
>> + limits.min_lane_count = limits.max_lane_count;
>> + limits.min_clock = limits.max_clock;
>> + }
>> }
>>
>> intel_dp_adjust_compliance_config(intel_dp, pipe_config, &limits);
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-05 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 14:55 [PATCH] drm/i915: optimzie eDP 1.4 config Lee, Shawn C
2018-09-04 14:28 ` Chris Wilson
2018-09-05 9:58 ` Jani Nikula [this message]
2018-09-05 9:58 ` Jani Nikula
2018-09-04 15:12 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-09-04 21:05 ` ✓ Fi.CI.IGT: " 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=87wos01d1i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Lee@freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shawn.c.lee@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