public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/cml: Add Missing PCI IDs
Date: Tue, 13 Aug 2019 20:33:51 +0530	[thread overview]
Message-ID: <7394715f-2c14-6b43-bd9b-e0652ba053f4@intel.com> (raw)
In-Reply-To: <20190812222737.29356-1-anusha.srivatsa@intel.com>



On 8/13/2019 3:57 AM, Anusha Srivatsa wrote:
> The BSpec has added three new IDS for CML.
> Update the IDs in accordance to the Spec.
> 
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
> ---
>   include/drm/i915_pciids.h | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> index a70c982ddff9..b1f66b117c74 100644
> --- a/include/drm/i915_pciids.h
> +++ b/include/drm/i915_pciids.h
> @@ -466,7 +466,10 @@
>   	INTEL_VGA_DEVICE(0x9BC5, info), \
>   	INTEL_VGA_DEVICE(0x9BC8, info), \
>   	INTEL_VGA_DEVICE(0x9BC4, info), \
> -	INTEL_VGA_DEVICE(0x9BC2, info)
> +	INTEL_VGA_DEVICE(0x9BC2, info), \
> +	INTEL_VGA_DEVICE(0x9BC6, info), \
> +	INTEL_VGA_DEVICE(0x9BE6, info), \
> +	INTEL_VGA_DEVICE(0x9BF6, info)
Verified with B.Specs index 33734, feel free to use.
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
>   
>   #define INTEL_KBL_IDS(info) \
>   	INTEL_KBL_GT1_IDS(info), \
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2019-08-13 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 22:27 [PATCH] drm/i915/cml: Add Missing PCI IDs Anusha Srivatsa
2019-08-12 23:18 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-13 11:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-08-13 15:03 ` Gupta, Anshuman [this message]

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=7394715f-2c14-6b43-bd9b-e0652ba053f4@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=intel-gfx@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