From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 2/6] drm/i915: Remove the link rate and lane count loop in compute config
Date: Tue, 27 Sep 2016 14:55:10 -0700 [thread overview]
Message-ID: <20160927215510.GA19006@intel.com> (raw)
In-Reply-To: <87r386kcc8.fsf@intel.com>
On Mon, Sep 26, 2016 at 04:41:27PM +0300, Jani Nikula wrote:
> On Fri, 16 Sep 2016, Manasi Navare <manasi.d.navare@intel.com> wrote:
> > While configuring the pipe during modeset, it should use
> > max clock and max lane count and reduce the bpp until
> > the requested mode rate is less than or equal to
> > available link BW.
> > This is required to pass DP Compliance.
>
> As I wrote in reply to patch 1/6, this is not a DP spec requirement. The
> link policy maker can freely choose the link parameters as long as the
> sink supports them.
>
> BR,
> Jani.
>
>
Thanks for your review feedback.
This change was driven by Video Pattern generation tests in CTS spec. Eg: In
test 4.3.3.1, the test requests 640x480 @ max link rate of 2.7Gbps and 4 lanes.
The test will pass if it sets the link rate to 2.7 and lane count = 4.
But in the existing implementation, this video mode request triggers a modeset
but the compute_config function starts with the lowest link rate and lane count and
trains the link at 1.62 and 4 lanes which does not match the expeced values of link
rate = 2.7 and lane count = 4 and the test fails.
Regards
Manasi
> >
> > v3:
> > * Add Debug print if requested mode cannot be supported
> > during modeset (Dhinakaran Pandiyan)
> > v2:
> > * Removed the loop since we use max values of clock
> > and lane count (Dhinakaran Pandiyan)
> >
> > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_dp.c | 22 ++++++++--------------
> > 1 file changed, 8 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > index d81c67cb..65b4559 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -1644,23 +1644,17 @@ intel_dp_compute_config(struct intel_encoder *encoder,
> > for (; bpp >= 6*3; bpp -= 2*3) {
> > mode_rate = intel_dp_link_required(adjusted_mode->crtc_clock,
> > bpp);
> > + clock = max_clock;
> > + lane_count = max_lane_count;
> > + link_clock = common_rates[clock];
> > + link_avail = intel_dp_max_data_rate(link_clock,
> > + lane_count);
> >
> > - for (clock = min_clock; clock <= max_clock; clock++) {
> > - for (lane_count = min_lane_count;
> > - lane_count <= max_lane_count;
> > - lane_count <<= 1) {
> > -
> > - link_clock = common_rates[clock];
> > - link_avail = intel_dp_max_data_rate(link_clock,
> > - lane_count);
> > -
> > - if (mode_rate <= link_avail) {
> > - goto found;
> > - }
> > - }
> > - }
> > + if (mode_rate <= link_avail)
> > + goto found;
> > }
> >
> > + DRM_DEBUG_KMS("Requested Mode Rate not supported\n");
> > return false;
> >
> > found:
>
> --
> Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-27 21:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 1:08 [PATCH 0/5] Remaining patches for upfront link training on DDI platforms Manasi Navare
2016-09-14 1:08 ` [PATCH v5 1/5] drm/i915: Fallback to lower link rate and lane count during link training Manasi Navare
2016-09-14 8:15 ` Mika Kahola
2016-09-15 19:56 ` Manasi Navare
2016-09-14 1:08 ` [PATCH v3 2/5] drm/i915: Remove the link rate and lane count loop in compute config Manasi Navare
2016-09-14 1:08 ` [PATCH v2 3/5] drm/i915: Change the placement of some static functions in intel_dp.c Manasi Navare
2016-09-15 7:41 ` Mika Kahola
2016-09-15 19:08 ` Manasi Navare
2016-09-14 1:08 ` [PATCH v17 4/5] drm/i915/dp: Enable Upfront link training on DDI platforms Manasi Navare
2016-09-14 1:08 ` [PATCH v3 5/5] drm/i915/dp/mst: Add support for upfront link training for DP MST Manasi Navare
2016-09-15 17:48 ` Pandiyan, Dhinakaran
2016-09-15 19:25 ` Manasi Navare
2016-09-19 17:03 ` Jim Bride
2016-09-19 17:22 ` Manasi Navare
2016-09-14 5:38 ` ✓ Fi.CI.BAT: success for Remaining patches for upfront link training on DDI platforms Patchwork
2016-09-16 0:03 ` [PATCH 0/6] " Manasi Navare
2016-09-16 0:03 ` [PATCH v6 1/6] drm/i915: Fallback to lower link rate and lane count during link training Manasi Navare
2016-09-16 9:29 ` Mika Kahola
2016-09-16 18:45 ` [PATCH v7 " Manasi Navare
2016-09-26 13:39 ` Jani Nikula
2016-09-27 15:25 ` Manasi Navare
2016-09-27 17:07 ` Jani Nikula
2016-09-29 6:41 ` Manasi Navare
2016-09-29 11:26 ` Jani Nikula
2016-09-29 11:44 ` Chris Wilson
2016-09-29 15:10 ` Ville Syrjälä
2016-09-29 15:48 ` Jani Nikula
2016-09-29 16:05 ` Manasi Navare
2016-09-29 23:17 ` Manasi Navare
2016-10-03 23:29 ` Manasi Navare
2016-09-16 0:04 ` [PATCH v3 2/6] drm/i915: Remove the link rate and lane count loop in compute config Manasi Navare
2016-09-26 13:41 ` Jani Nikula
2016-09-27 13:39 ` Jani Nikula
2016-09-27 22:13 ` Manasi Navare
2016-09-28 7:14 ` Jani Nikula
2016-09-28 22:30 ` Manasi Navare
2016-09-27 21:55 ` Manasi Navare [this message]
2016-09-28 7:38 ` Jani Nikula
2016-09-28 16:45 ` Manasi Navare
2016-09-29 14:52 ` Jani Nikula
2016-09-16 0:04 ` [PATCH v3 3/6] drm/i915: Change the placement of some static functions in intel_dp.c Manasi Navare
2016-09-16 8:12 ` Mika Kahola
2016-09-16 0:04 ` [PATCH 4/6] drm/i915: Code cleanup to use dev_priv and INTEL_GEN Manasi Navare
2016-09-16 7:40 ` Mika Kahola
2016-09-26 13:45 ` Jani Nikula
2016-09-28 0:03 ` Manasi Navare
2016-09-16 0:04 ` [PATCH v17 5/6] drm/i915/dp: Enable Upfront link training on DDI platforms Manasi Navare
2016-09-20 22:04 ` [PATCH v18 " Manasi Navare
2016-09-27 13:59 ` Jani Nikula
2016-09-29 12:15 ` Jani Nikula
2016-09-29 16:05 ` Jani Nikula
2016-09-16 0:04 ` [PATCH v3 6/6] drm/i915/dp/mst: Add support for upfront link training for DP MST Manasi Navare
2016-09-16 0:47 ` ✓ Fi.CI.BAT: success for series starting with [v6,1/6] drm/i915: Fallback to lower link rate and lane count during link training Patchwork
2016-09-16 19:25 ` ✓ Fi.CI.BAT: success for series starting with [v7,1/6] drm/i915: Fallback to lower link rate and lane count during link training (rev2) Patchwork
2016-09-20 8:45 ` [PATCH 0/6] Remaining patches for upfront link training on DDI platforms Jani Nikula
2016-09-20 22:49 ` ✓ Fi.CI.BAT: success for series starting with [v7,1/6] drm/i915: Fallback to lower link rate and lane count during link training (rev3) 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=20160927215510.GA19006@intel.com \
--to=manasi.d.navare@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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).