From: Matt Roper <matthew.d.roper@intel.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"José Roberto de Souza" <jose.souza@intel.com>,
stable@vger.kernel.org, holger.philipps@siemens.com,
wagner.dominik@siemens.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, 14 Jun 2023 17:17:35 -0700 [thread overview]
Message-ID: <20230615001735.GV5433@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20230612093030.03336764@md1za8fc.ad001.siemens.net>
On Mon, Jun 12, 2023 at 09:30:30AM +0200, Henning Schild wrote:
> Am Wed, 7 Jun 2023 20:09:58 +0200
> schrieb Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>
> > 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?
>
> I was not sure that was needed for a backport, but will add it once i
> resend.
>
> > Please resend this series with that added so that we can queue them
> > up.
>
> Will do.
>
> Matt would you agree? As i said i just googled/bisected and found this
> one and it seems to help. But you seem to say that it does not fit. I
> am guessing the patch might not be as atomic as could be, that is why
> backporting it helps.
Sorry for the slow response; I've been traveling and am just catching up
on email now.
Since you're running on a platform with integrated graphics, this patch
can't have any functional impact. The function added in this patch only
does something on discrete GPU platforms; on all others it bails out
immediately:
+ if (!IS_DGFX(i915))
+ return;
The only Intel discrete devices that return true from IS_DGFX are DG1,
DG2, and PVC, none of which were supported yet on the 5.10 kernel.
The dmesg splat you pasted in your cover letter is coming from the DRAM
detection code, which is what the other patch in your series
("drm/i915/gen11+: Only load DRAM information from pcode") is dealing
with. So I think that other patch is the only one you should need; this
pcode one isn't having any effect.
Matt
>
> Henning
>
> > thanks,
> >
> > greg k-h
>
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2023-06-15 0:17 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
2023-06-12 7:30 ` Henning Schild
2023-06-15 0:17 ` Matt Roper [this message]
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=20230615001735.GV5433@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=Clinton.A.Taylor@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=henning.schild@siemens.com \
--cc=holger.philipps@siemens.com \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@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