From: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Cc: bp@alien8.de, lucas.demarchi@intel.com,
matthew.d.roper@intel.com, hariom.pandey@intel.com
Subject: [PATCH] x86/gpu: add JSL stolen memory support
Date: Wed, 4 Nov 2020 17:35:06 +0530 [thread overview]
Message-ID: <20201104120506.172447-1-tejaskumarx.surendrakumar.upadhyay@intel.com> (raw)
JSL re-uses the same stolen memory as ICL and EHL.
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@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..534cc3f78c6b 100644
--- a/arch/x86/kernel/early-quirks.c
+++ b/arch/x86/kernel/early-quirks.c
@@ -549,6 +549,7 @@ static const struct pci_device_id intel_early_ids[] __initconst = {
INTEL_CNL_IDS(&gen9_early_ops),
INTEL_ICL_11_IDS(&gen11_early_ops),
INTEL_EHL_IDS(&gen11_early_ops),
+ INTEL_JSL_IDS(&gen11_early_ops),
INTEL_TGL_12_IDS(&gen11_early_ops),
INTEL_RKL_IDS(&gen11_early_ops),
};
--
2.28.0
next reply other threads:[~2020-11-04 12:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 12:05 Tejas Upadhyay [this message]
2020-11-04 17:35 ` [PATCH] x86/gpu: add JSL stolen memory support Bjorn Helgaas
2020-11-05 9:46 ` Joonas Lahtinen
2020-11-05 14:17 ` Bjorn Helgaas
2020-11-06 9:39 ` Daniel Vetter
2020-11-18 12:10 ` Surendrakumar Upadhyay, TejaskumarX
2020-11-18 16:02 ` Bjorn Helgaas
2020-11-18 21:57 ` Daniel Vetter
2020-11-18 23:14 ` Bjorn Helgaas
2020-11-19 9:37 ` Daniel Vetter
2020-11-19 19:19 ` Bjorn Helgaas
2020-11-19 22:01 ` Jesse Barnes
2020-11-30 10:44 ` Surendrakumar Upadhyay, TejaskumarX
2020-11-30 16:51 ` Bjorn Helgaas
2020-12-02 5:21 ` Surendrakumar Upadhyay, TejaskumarX
2020-12-02 20:22 ` Bjorn Helgaas
2020-12-03 3:23 ` Surendrakumar Upadhyay, TejaskumarX
2020-12-03 8:46 ` Joonas Lahtinen
2020-12-03 15:25 ` Bjorn Helgaas
2020-12-03 16:09 ` Surendrakumar Upadhyay, TejaskumarX
2021-01-20 10:04 ` Surendrakumar Upadhyay, TejaskumarX
2022-01-20 1:10 ` Lucas De Marchi
2022-01-20 7:35 ` Joonas Lahtinen
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=20201104120506.172447-1-tejaskumarx.surendrakumar.upadhyay@intel.com \
--to=tejaskumarx.surendrakumar.upadhyay@intel.com \
--cc=bp@alien8.de \
--cc=hariom.pandey@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--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).