Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Henning Schild <henning.schild@siemens.com>
Cc: stable@vger.kernel.org, holger.philipps@siemens.com,
	wagner.dominik@siemens.com,
	"José Roberto de Souza" <jose.souza@intel.com>,
	"Matt Roper" <matthew.d.roper@intel.com>,
	"Clinton Taylor" <Clinton.A.Taylor@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Radhakrishna Sripada" <radhakrishna.sripada@intel.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>
Subject: Re: [PATCH 5.10 1/2] drm/i915/dg1: Wait for pcode/uncore handshake at startup
Date: Wed, 7 Jun 2023 20:09:58 +0200	[thread overview]
Message-ID: <2023060719-seminar-patrol-68d8@gregkh> (raw)
In-Reply-To: <20230602160507.2057-2-henning.schild@siemens.com>

On Fri, Jun 02, 2023 at 06:05:06PM +0200, Henning Schild wrote:
> From: Matt Roper <matthew.d.roper@intel.com>
> 
> From: Matt Roper <matthew.d.roper@intel.com>

Twice?

> 
> [ Upstream commit f9c730ede7d3f40900cb493890d94d868ff2f00f ]
> 
> DG1 does some additional pcode/uncore handshaking at
> boot time; this handshaking must complete before various other pcode
> commands are effective and before general work is submitted to the GPU.
> We need to poll a new pcode mailbox during startup until it reports that
> this handshaking is complete.
> 
> The bspec doesn't give guidance on how long we may need to wait for this
> handshaking to complete.  For now, let's just set a really long timeout;
> if we still don't get a completion status by the end of that timeout,
> we'll just continue on and hope for the best.
> 
> v2 (Lucas): Rename macros to make clear the relation between command and
>    result (requested by José)
> 
> Bspec: 52065
> Cc: Clinton Taylor <Clinton.A.Taylor@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20201001063917.3133475-2-lucas.demarchi@intel.com

You also need to sign-off on a patch you submit for inclusion anywhere,
right?

Please resend this series with that added so that we can queue them up.

thanks,

greg k-h

  reply	other threads:[~2023-06-07 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 16:05 [PATCH 5.10 0/2] backport i915 fixes to 5.10 Henning Schild
2023-06-02 16:05 ` [PATCH 5.10 1/2] drm/i915/dg1: Wait for pcode/uncore handshake at startup Henning Schild
2023-06-07 18:09   ` Greg Kroah-Hartman [this message]
2023-06-12  7:30     ` Henning Schild
2023-06-15  0:17       ` Matt Roper
2023-06-15  7:10         ` Henning Schild
2023-06-02 16:05 ` [PATCH 5.10 2/2] drm/i915/gen11+: Only load DRAM information from pcode Henning Schild
2023-06-02 16:14 ` [PATCH 5.10 0/2] backport i915 fixes to 5.10 Matt Roper
2023-06-02 16:33   ` Henning Schild
2023-06-02 16:43     ` Souza, Jose
2023-06-02 17:03       ` Henning Schild

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=2023060719-seminar-patrol-68d8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Clinton.A.Taylor@intel.com \
    --cc=henning.schild@siemens.com \
    --cc=holger.philipps@siemens.com \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=radhakrishna.sripada@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    --cc=wagner.dominik@siemens.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