From: Petri Latvala <petri.latvala@intel.com>
To: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] lib/i915: Add DG1 platform definition
Date: Wed, 12 Aug 2020 12:42:41 +0300 [thread overview]
Message-ID: <20200812094241.GQ7444@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200812090548.4973-3-adam.miszczak@linux.intel.com>
On Wed, Aug 12, 2020 at 11:05:48AM +0200, Adam Miszczak wrote:
> Signed-off-by: Adam Miszczak <adam.miszczak@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> lib/intel_chipset.h | 2 ++
> lib/intel_device_info.c | 8 ++++++++
> 2 files changed, 10 insertions(+)
>
> diff --git a/lib/intel_chipset.h b/lib/intel_chipset.h
> index 18f860ca..51093091 100644
> --- a/lib/intel_chipset.h
> +++ b/lib/intel_chipset.h
> @@ -74,6 +74,7 @@ struct intel_device_info {
> bool is_elkhartlake : 1;
> bool is_tigerlake : 1;
> bool is_rocketlake : 1;
> + bool is_dg1 : 1;
> const char *codename;
> };
>
> @@ -173,6 +174,7 @@ void intel_check_pch(void);
> #define IS_ICELAKE(devid) (intel_get_device_info(devid)->is_icelake)
> #define IS_TIGERLAKE(devid) (intel_get_device_info(devid)->is_tigerlake)
> #define IS_ROCKETLAKE(devid) (intel_get_device_info(devid)->is_rocketlake)
> +#define IS_DG1(devid) (intel_get_device_info(devid)->is_dg1)
>
> #define IS_GEN(devid, x) (intel_get_device_info(devid)->gen & (1u << ((x)-1)))
> #define AT_LEAST_GEN(devid, x) (intel_get_device_info(devid)->gen & -(1u << ((x)-1)))
> diff --git a/lib/intel_device_info.c b/lib/intel_device_info.c
> index e5720443..d5f70156 100644
> --- a/lib/intel_device_info.c
> +++ b/lib/intel_device_info.c
> @@ -327,6 +327,12 @@ static const struct intel_device_info intel_rocketlake_info = {
> .codename = "rocketlake"
> };
>
> +static const struct intel_device_info intel_dg1_info = {
> + .gen = BIT(11),
> + .is_dg1 = true,
> + .codename = "dg1"
> +};
> +
> static const struct pci_id_match intel_device_match[] = {
> INTEL_I810_IDS(&intel_i810_info),
> INTEL_I815_IDS(&intel_i815_info),
> @@ -413,6 +419,8 @@ static const struct pci_id_match intel_device_match[] = {
> INTEL_TGL_12_IDS(&intel_tigerlake_info),
> INTEL_RKL_IDS(&intel_rocketlake_info),
>
> + INTEL_DG1_IDS(&intel_dg1_info),
> +
> INTEL_VGA_DEVICE(PCI_MATCH_ANY, &intel_generic_info),
> };
>
> --
> 2.27.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-08-12 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 9:05 [igt-dev] [PATCH i-g-t 0/2] lib/i915: Add DG1 platform definition Adam Miszczak
2020-08-12 9:05 ` [igt-dev] [PATCH i-g-t 1/2] lib: sync i915_pciids.h with kernel Adam Miszczak
2020-08-12 9:40 ` Petri Latvala
2020-08-12 9:05 ` [igt-dev] [PATCH i-g-t 2/2] lib/i915: Add DG1 platform definition Adam Miszczak
2020-08-12 9:42 ` Petri Latvala [this message]
2020-08-12 9:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-12 11:38 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20200812094241.GQ7444@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.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