From: Raag Jadav <raag.jadav@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com
Subject: Re: [PATCH v6 1/3] drm/xe: Add functions and sysfs for boot survivability
Date: Thu, 3 Apr 2025 19:47:49 +0300 [thread overview]
Message-ID: <Z-67tX1--b3w-Lh1@black.fi.intel.com> (raw)
In-Reply-To: <20250128095632.1294722-2-riana.tauro@intel.com>
Bumping this since I just discovered something.
On Tue, Jan 28, 2025 at 03:26:30PM +0530, Riana Tauro wrote:
...
> +#define PCODE_SCRATCH(x) XE_REG(0x138320 + ((x) * 4))
If we're referring to PCODE_FIT_DATA_0_2_0_GTTMMADR[0], it actually
starts from 0x138300.
Anything to worry about here?
Raag
next prev parent reply other threads:[~2025-04-03 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 9:56 [PATCH v6 0/3] Enable Survivability mode Riana Tauro
2025-01-28 9:56 ` [PATCH v6 1/3] drm/xe: Add functions and sysfs for boot survivability Riana Tauro
2025-04-03 16:47 ` Raag Jadav [this message]
2025-01-28 9:56 ` [PATCH v6 2/3] drm/xe: Enable Boot Survivability mode Riana Tauro
2025-01-29 7:27 ` K V P, Satyanarayana
2025-01-30 6:32 ` Riana Tauro
2025-01-30 6:35 ` K V P, Satyanarayana
2025-01-28 9:56 ` [PATCH v6 3/3] drm/xe: Initialize mei-gsc and vsec in survivability mode Riana Tauro
2025-01-28 10:29 ` ✓ CI.Patch_applied: success for Enable Survivability mode (rev7) Patchwork
2025-01-28 10:30 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-28 10:31 ` ✓ CI.KUnit: success " Patchwork
2025-01-28 10:47 ` ✓ CI.Build: " Patchwork
2025-01-28 10:49 ` ✗ CI.Hooks: failure " Patchwork
2025-01-28 10:51 ` ✓ CI.checksparse: success " Patchwork
2025-01-28 11:25 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-28 22:03 ` ✗ Xe.CI.Full: 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=Z-67tX1--b3w-Lh1@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox