From: Aditya Swarup <aditya.swarup@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
x86@kernel.org, Lucas De Marchi <lucas.demarchi@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>
Subject: [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support
Date: Mon, 25 Jan 2021 02:59:31 -0800 [thread overview]
Message-ID: <20210125105931.268977-2-aditya.swarup@intel.com> (raw)
In-Reply-To: <20210125105931.268977-1-aditya.swarup@intel.com>
From: Caz Yokoyama <caz.yokoyama@intel.com>
Alderlake-S is a Gen 12 based hybrid processor architeture. As it
belongs to Gen 12 family, it uses the same GTT stolen memory settings
like its predecessors - ICL(Gen 11) and TGL(Gen 12). This patch inherits
the gen11 and gen 9 quirks for determining base and size of stolen
memory.
Note that this patch depends on commit 0883d63b19bb
("drm/i915/adl_s: Add ADL-S platform info and PCI ids")
Bspec: 52055
Bspec: 49589
Bspec: 49636
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Imre Deak <imre.deak@intel.com>
Cc: x86@kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Cc: Thomas Gleixner <tglx@linutronix.de>,
Cc: Borislav Petkov <bp@suse.de>
Signed-off-by: Caz Yokoyama <caz.yokoyama@intel.com>
Signed-off-by: Aditya Swarup <aditya.swarup@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
arch/x86/kernel/early-quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
index a4b5af03dcc1..6edd1e2ee8af 100644
--- a/arch/x86/kernel/early-quirks.c
+++ b/arch/x86/kernel/early-quirks.c
@@ -551,6 +551,7 @@ static const struct pci_device_id intel_early_ids[] __initconst = {
INTEL_EHL_IDS(&gen11_early_ops),
INTEL_TGL_12_IDS(&gen11_early_ops),
INTEL_RKL_IDS(&gen11_early_ops),
+ INTEL_ADLS_IDS(&gen11_early_ops),
};
struct resource intel_graphics_stolen_res __ro_after_init = DEFINE_RES_MEM(0, 0);
--
2.27.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-25 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 10:59 [Intel-gfx] [PATCH 0/1] Add Alderlake-S stolen memory changes Aditya Swarup
2021-01-25 10:59 ` Aditya Swarup [this message]
2021-01-25 17:33 ` [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support Borislav Petkov
2021-01-25 12:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add Alderlake-S stolen memory changes Patchwork
2021-01-25 13:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-25 16:13 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-26 0:17 [Intel-gfx] [PATCH 0/1] " Aditya Swarup
2021-01-26 0:17 ` [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support Aditya Swarup
2021-01-26 10:28 ` Borislav Petkov
2021-01-26 14:59 ` Lucas De Marchi
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=20210125105931.268977-2-aditya.swarup@intel.com \
--to=aditya.swarup@intel.com \
--cc=bp@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).