From: Dominik Brodowski <linux@dominikbrodowski.net>
To: "Souza, Jose" <jose.souza@intel.com>, airlied@redhat.com
Cc: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"s.zharkoff@gmail.com" <s.zharkoff@gmail.com>,
"boris.brezillon@collabora.com" <boris.brezillon@collabora.com>,
"airlied@redhat.com" <airlied@redhat.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"jernej.skrabec@siol.net" <jernej.skrabec@siol.net>,
"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jonas@kwiboo.se" <jonas@kwiboo.se>
Subject: 5.5.6-rc1+: lockup on boot -- drm/i915/display: Force the state compute phase once to enable PSR
Date: Sun, 1 Mar 2020 16:15:55 +0100 [thread overview]
Message-ID: <20200301151555.GA127893@light.dominikbrodowski.net> (raw)
In-Reply-To: <20200218185847.GA15931@light.dominikbrodowski.net>
On Tue, Feb 18, 2020 at 07:58:47PM +0100, Dominik Brodowski wrote:
> On Tue, Feb 18, 2020 at 06:01:37PM +0000, Souza, Jose wrote:
> > Hi
> >
> > Yes this patch has a issue and we have a fix, I'm trying to find
> > someone to review it, more information:
> > https://gitlab.freedesktop.org/drm/intel/issues/1151
>
> Alas, that patch does not apply cleanly to -master.
Any update on this patch? It doesn't seem to have landed in -master yet,
though it solves a clear regression and without such a patch, my laptops
refuse to boot. So it'd be much appreciated if that patch (or a variant
thereof) is pushed upstream rather sooner than later.
Thanks,
Dominik
prev parent reply other threads:[~2020-03-01 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 20:09 drm/bridge and lockup on boot Dominik Brodowski
2020-02-17 21:08 ` Boris Brezillon
2020-02-18 11:48 ` lockup on boot -- drm/i915/display: Force the state compute phase once to enable PSR Dominik Brodowski
2020-02-18 18:01 ` Souza, Jose
2020-02-18 18:58 ` Dominik Brodowski
2020-03-01 15:15 ` Dominik Brodowski [this message]
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=20200301151555.GA127893@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=airlied@redhat.com \
--cc=boris.brezillon@collabora.com \
--cc=gwan-gyeong.mun@intel.com \
--cc=jani.nikula@intel.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=jose.souza@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=s.zharkoff@gmail.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).