From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PATCH 0/2] Don't be alarmed at FLR timeouts
Date: Fri, 17 May 2024 13:25:48 +0200 [thread overview]
Message-ID: <20240517112550.251955-1-andi.shyti@linux.intel.com> (raw)
Hi,
often, on new platforms or firmware updates, we receive reports
of FLR timeout expiration and we shift the timeout we wait for
the reset to complete.
Let's not be alarmed if we reach a timeout while waiting for FLR
resets and print debugs rather than errors. The function is
anyway a void fucntions without any effect.
While at it, increase the timeout.
Thanks,
Andi
Andi Shyti (2):
drm/i915: Increase FLR timeout from 3s to 9s
drm/i915: Don't treat FLR resets as errors
drivers/gpu/drm/i915/intel_uncore.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-05-17 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:25 Andi Shyti [this message]
2024-05-17 11:25 ` [PATCH 1/2] drm/i915: Increase FLR timeout from 3s to 9s Andi Shyti
2024-05-17 11:25 ` [PATCH 2/2] drm/i915: Don't treat FLR resets as errors Andi Shyti
2024-05-17 14:00 ` Nirmoy Das
2024-05-17 19:34 ` Andi Shyti
2024-05-17 20:13 ` Nirmoy Das
2024-05-21 10:56 ` Andi Shyti
2024-05-22 9:07 ` Nirmoy Das
2024-05-17 12:45 ` ✓ Fi.CI.BAT: success for Don't be alarmed at FLR timeouts Patchwork
2024-05-17 17:53 ` ✗ Fi.CI.IGT: failure " Patchwork
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=20240517112550.251955-1-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=nirmoy.das@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