public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: BDW: Adding Reserved PCI IDs.
Date: Wed, 11 Jun 2014 10:47:45 -0700	[thread overview]
Message-ID: <20140611174743.GA950@bwidawsk.net> (raw)
In-Reply-To: <1402422067-5717-1-git-send-email-rodrigo.vivi@intel.com>

On Tue, Jun 10, 2014 at 10:41:07AM -0700, Rodrigo Vivi wrote:
> These PCI IDs are reserved on BSpec and can be used at any time in the future.
> So let's add this now in order to avoid issues that we already faced on previous
> platforms, like finding out about new ids when user reported accelaration weren't
> enabled.
> 
> v2: Reserved IDs doesn't have GT defined. So, creating a separated list. (Ben)
> 
> Cc: Ben Widawsky <ben@bwidawsk.net>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  include/drm/i915_pciids.h | 16 ++++++++++++++--
>  1 file changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> index 0572035..0968478 100644
> --- a/include/drm/i915_pciids.h
> +++ b/include/drm/i915_pciids.h
> @@ -237,13 +237,25 @@
>  #define INTEL_BDW_GT3D_IDS(info) \
>  	_INTEL_BDW_D_IDS(3, info)
>  
> +#define INTEL_BDW_RSVDM_IDS(info) \
> +	INTEL_VGA_DEVICE(0x1632, info), \
> +	INTEL_VGA_DEVICE(0x1636, info), \
> +	INTEL_VGA_DEVICE(0x163B, info), \
> +	INTEL_VGA_DEVICE(0x163A, info)
> +
> +#define INTEL_BDW_RSVDD_IDS(info) \
> +	INTEL_VGA_DEVICE(0x163D, info), \
> +	INTEL_VGA_DEVICE(0x163E, info)
> +
>  #define INTEL_BDW_M_IDS(info) \
>  	INTEL_BDW_GT12M_IDS(info), \
> -	INTEL_BDW_GT3M_IDS(info)
> +	INTEL_BDW_GT3M_IDS(info), \
> +	INTEL_BDW_RSVDM_IDS(info)
>  
>  #define INTEL_BDW_D_IDS(info) \
>  	INTEL_BDW_GT12D_IDS(info), \
> -	INTEL_BDW_GT3D_IDS(info)
> +	INTEL_BDW_GT3D_IDS(info), \
> +	INTEL_BDW_RSVDD_IDS(info)
>  
>  #define INTEL_CHV_IDS(info) \
>  	INTEL_VGA_DEVICE(0x22b0, info), \

I thought we saved off the GT info, but now that I actually look at the
code, we do not. Therefore, I actually think v1 is a better patch.

In either case, both v1 and v2 are:
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>

I apologize for the extra work.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2014-06-11 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 17:09 [PATCH] drm/i915: BDW: Adding Reserved PCI IDs Rodrigo Vivi
2014-06-11  0:17 ` Ben Widawsky
2014-06-10 17:41   ` Rodrigo Vivi
2014-06-11 17:47     ` Ben Widawsky [this message]
2014-06-13  0:39       ` Rodrigo Vivi
2014-06-24 13:19         ` Jani Nikula
2014-06-24 15:32           ` Chris Wilson

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=20140611174743.GA950@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --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