From: Raag Jadav <raag.jadav@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>,
"andi.shyti@linux.intel.com" <andi.shyti@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Nilawar, Badal" <badal.nilawar@intel.com>,
"Tauro, Riana" <riana.tauro@intel.com>
Subject: Re: [PATCH v1] drm/i915/dg2: enable G8 with a workaround
Date: Tue, 15 Oct 2024 11:37:05 +0300 [thread overview]
Message-ID: <Zw4psVTdcC-wEoR_@black.fi.intel.com> (raw)
In-Reply-To: <CY5PR11MB621150027D63DDA95B01427895442@CY5PR11MB6211.namprd11.prod.outlook.com>
On Mon, Oct 14, 2024 at 10:01:50AM +0530, Gupta, Anshuman wrote:
> > On Tue, Oct 08, 2024 at 08:24:42PM +0300, Jani Nikula wrote:
> > > On Mon, 07 Oct 2024, Raag Jadav <raag.jadav@intel.com> wrote:
> > > > Host BIOS doesn't enable G8 power mode due to an issue on DG2, so we
> AFAIU it discrete card firmware not HOST bios.
Yes, although firmware relies on native ASPM for G8 entry, which is setup
by host BIOS.
https://www.intel.com/content/www/us/en/support/articles/000092564/graphics.html
Raag
next prev parent reply other threads:[~2024-10-15 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 12:24 [PATCH v1] drm/i915/dg2: enable G8 with a workaround Raag Jadav
2024-10-07 13:05 ` Nilawar, Badal
2024-10-07 13:17 ` Nilawar, Badal
2024-10-08 3:43 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-10-08 3:53 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-08 17:24 ` [PATCH v1] " Jani Nikula
2024-10-09 12:47 ` Raag Jadav
2024-10-09 13:05 ` Jani Nikula
2024-10-09 16:42 ` Raag Jadav
2024-10-09 16:50 ` Jani Nikula
2024-10-09 19:05 ` Matt Roper
2024-10-14 4:31 ` Gupta, Anshuman
2024-10-15 8:37 ` Raag Jadav [this message]
2024-10-14 6:30 ` kernel test robot
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=Zw4psVTdcC-wEoR_@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=riana.tauro@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.