Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: aacid@kde.org, airlied@gmail.com, ilpanich@gmail.com,
	manasi.d.navare@intel.com, matteoiervasi@gmail.com,
	matthew.s.atwood@intel.com, rodrigo.vivi@intel.com,
	shawn.c.lee@intel.com, stable@vger.kernel.org,
	ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [v5.0 stable PATCH] drm/i915/dp: revert back to max link rate and lane count on eDP
Date: Mon, 15 Apr 2019 16:43:00 +0200	[thread overview]
Message-ID: <20190415144300.GA27194@kroah.com> (raw)
In-Reply-To: <20190415125837.16428-1-jani.nikula@intel.com>

On Mon, Apr 15, 2019 at 03:58:37PM +0300, Jani Nikula wrote:
> commit 21635d7311734d2d1b177f8a95e2f9386174b76d upstream.
> 
> Commit 7769db588384 ("drm/i915/dp: optimize eDP 1.4+ link config fast
> and narrow") started to optize the eDP 1.4+ link config, both per spec
> and as preparation for display stream compression support.
> 
> Sadly, we again face panels that flat out fail with parameters they
> claim to support. Revert, and go back to the drawing board.
> 
> v2: Actually revert to max params instead of just wide-and-slow.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109959
> Fixes: 7769db588384 ("drm/i915/dp: optimize eDP 1.4+ link config fast and narrow")
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Matt Atwood <matthew.s.atwood@intel.com>
> Cc: "Lee, Shawn C" <shawn.c.lee@intel.com>
> Cc: Dave Airlie <airlied@gmail.com>
> Cc: intel-gfx@lists.freedesktop.org
> Cc: <stable@vger.kernel.org> # v5.0+
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
> Tested-by: Albert Astals Cid <aacid@kde.org> # v5.0 backport
> Tested-by: Emanuele Panigati <ilpanich@gmail.com> # v5.0 backport
> Tested-by: Matteo Iervasi <matteoiervasi@gmail.com> # v5.0 backport
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20190405075220.9815-1-jani.nikula@intel.com
> (cherry picked from commit f11cb1c19ad0563b3c1ea5eb16a6bac0e401f428)
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 69 +++++----------------------------
>  1 file changed, 10 insertions(+), 59 deletions(-)

Now queued up, thanks.

greg k-h

  reply	other threads:[~2019-04-15 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1555325493102231@kroah.com>
2019-04-15 12:58 ` [v5.0 stable PATCH] drm/i915/dp: revert back to max link rate and lane count on eDP Jani Nikula
2019-04-15 14:43   ` Greg KH [this message]
2019-04-15 13:47 ` ✗ Fi.CI.BAT: failure for drm/i915/dp: revert back to max link rate and lane count on eDP (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=20190415144300.GA27194@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aacid@kde.org \
    --cc=airlied@gmail.com \
    --cc=ilpanich@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=matteoiervasi@gmail.com \
    --cc=matthew.s.atwood@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=shawn.c.lee@intel.com \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox