From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v1] drm/i915/pxp/mtl: Update gsc-heci cmd size and timeout
Date: Thu, 10 Aug 2023 23:55:18 +0000 [thread overview]
Message-ID: <5ce59609fe1f8464ee59bfca5c6ff9ed24bb633d.camel@intel.com> (raw)
In-Reply-To: <20230707183426.1952655-1-alan.previn.teres.alexis@intel.com>
On Fri, 2023-07-07 at 11:34 -0700, Teres Alexis, Alan Previn wrote:
> Update the max GSC-HECI packet size and the max firmware
> response timeout to match internal fw specs.
>
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
I'm going to re-rev this and change the subject slightly to "Update gsc-heci cmd submission
to align with spec". The two changes in this patch will be included but the cmd-packet size
is now to be increased to 64K. Also, the counting of the timeout needs to start from when
the request has his the cmd streamer hardware (not from when the PXP subsystem has thrown it
over the wall to the GuC). Although this latter change would imply a longer timeout period,
the change to observe this longer timeout should be applicable to code that is actually
triggering a PXP session creation/teardown.
In addition to that, we also need to update the LRC common defaults to inclure forcing
the runalone bit for PXP contexts (as that is the updated hardware spec'd
expectation).
...alan
prev parent reply other threads:[~2023-08-10 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 18:34 [Intel-gfx] [PATCH v1] drm/i915/pxp/mtl: Update gsc-heci cmd size and timeout Alan Previn
2023-07-07 19:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-07-07 23:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-12 17:39 ` Teres Alexis, Alan Previn
2023-08-10 23:55 ` Teres Alexis, Alan Previn [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=5ce59609fe1f8464ee59bfca5c6ff9ed24bb633d.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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