Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Disable PL1 power limit when loading GuC firmware
Date: Sat, 11 Mar 2023 12:46:05 -0800	[thread overview]
Message-ID: <87v8j7kodu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230311003358.1660191-1-ashutosh.dixit@intel.com>

On Fri, 10 Mar 2023 16:33:58 -0800, Ashutosh Dixit wrote:
>
> On dGfx, the PL1 power limit being enabled and set to a low value results
> in a low GPU operating freq. It also negates the freq raise operation which
> is done before GuC firmware load. As a result GuC firmware load can time
> out. Such timeouts were seen in the GL #8062 bug below (where the PL1 power
> limit was enabled and set to a low value). Therefore disable the PL1 power
> limit when possible when loading GuC firmware.

There are a couple of bugs in the patch. Please don't review yet, will post
a v2. Thanks.

  reply	other threads:[~2023-03-11 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  0:33 [Intel-gfx] [PATCH] drm/i915/guc: Disable PL1 power limit when loading GuC firmware Ashutosh Dixit
2023-03-11 20:46 ` Dixit, Ashutosh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-16  3:59 Ashutosh Dixit
2023-03-24 18:15 ` Belgaumkar, Vinay
2023-03-24 23:31   ` Dixit, Ashutosh
2023-03-25  0:06     ` Belgaumkar, Vinay
2023-03-27 16:57       ` Dixit, Ashutosh
2023-03-26 11:52     ` Rodrigo Vivi
2023-03-27 16:58       ` Dixit, Ashutosh
2023-03-27 17:47         ` Rodrigo Vivi
2023-03-28  9:14           ` Tvrtko Ursulin
2023-04-06  4:52             ` Dixit, Ashutosh
2023-04-06  4:50           ` Dixit, Ashutosh

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=87v8j7kodu.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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