stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: stable@vger.kernel.org, tvrtko.ursulin@intel.com,
	Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Subject: Re: [PATCH stable-5.15] drm/i915: Workaround broken BIOS DBUF configuration on TGL/RKL
Date: Mon, 14 Mar 2022 10:21:58 +0100	[thread overview]
Message-ID: <Yi8JNtEenUwDiWD1@kroah.com> (raw)
In-Reply-To: <20220307165607.32368-1-ville.syrjala@linux.intel.com>

On Mon, Mar 07, 2022 at 06:56:07PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> commit 4e6f55120c7eccf6f9323bb681632e23cbcb3f3c upstream.
> 
> On TGL/RKL the BIOS likes to use some kind of bogus DBUF layout
> that doesn't match what the spec recommends. With a single active
> pipe that is not going to be a problem, but with multiple pipes
> active skl_commit_modeset_enables() goes into an infinite loop
> since it can't figure out any order in which it can commit the
> pipes without causing DBUF overlaps between the planes.
> 
> We'd need some kind of extra DBUF defrag stage in between to
> make the transition possible. But that is clearly way too complex
> a solution, so in the name of simplicity let's just sanitize the
> DBUF state by simply turning off all planes when we detect a
> pipe encroaching on its neighbours' DBUF slices. We only have
> to disable the primary planes as all other planes should have
> already been disabled (if they somehow were enabled) by
> earlier sanitization steps.
> 
> And for good measure let's also sanitize in case the DBUF
> allocations of the pipes already seem to overlap each other.
> 
> Cc: <stable@vger.kernel.org> # v5.14+
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4762
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20220204141818.1900-3-ville.syrjala@linux.intel.com
> Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> (cherry picked from commit 15512021eb3975a8c2366e3883337e252bb0eee5)
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> (cherry picked from commit 4e6f55120c7eccf6f9323bb681632e23cbcb3f3c)
> ---
> The chain of additional cherry-picks needed to get
> intel_plane_disable_noatomic() destaticed looked pretty
> hairy, so I just fixed it up manually.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-03-14  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 12:32 FAILED: patch "[PATCH] drm/i915: Workaround broken BIOS DBUF configuration on" failed to apply to 5.15-stable tree gregkh
2022-03-07 16:56 ` [PATCH stable-5.15] drm/i915: Workaround broken BIOS DBUF configuration on TGL/RKL Ville Syrjala
2022-03-14  9:21   ` Greg KH [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=Yi8JNtEenUwDiWD1@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=tvrtko.ursulin@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).