All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/intel_device_info: Add IS_DGFX() support
Date: Mon, 25 Apr 2022 05:24:06 +0000	[thread overview]
Message-ID: <6b377d0333494eb1940bd2f96ba15cb8@intel.com> (raw)
In-Reply-To: <87y1zx6qzs.wl-ashutosh.dixit@intel.com>



> -----Original Message-----
> From: Dixit, Ashutosh <ashutosh.dixit@intel.com>
> Sent: Friday, April 22, 2022 9:38 PM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>
> Cc: igt-dev@lists.freedesktop.org; Vivi, Rodrigo <rodrigo.vivi@intel.com>
> Subject: Re: [igt-dev] [PATCH i-g-t] lib/intel_device_info: Add IS_DGFX() support
> 
> On Fri, 22 Apr 2022 05:59:12 -0700, Anshuman Gupta wrote:
> >
> > Currently IGT is lacking IS_DGFX() macro support.
> > There are some power features like D3Cold are only supported on
> > discrete card. So IGT test/tools specific to D3Cold requires to
> > consume IS_DGFX().
> > Adding a is_dgfx field in intel_device_info and initializing it for
> > DG1. All future discrete platform would require to initialize this
> > field.
> 
> #define IS_DGFX(fd) gem_has_lmem(fd) ?
> 
> gem_has_lmem() is already pretty widely used so maybe we should not
> introduce another way to achieve the same goal?
Before introducing this , I thought on using gem_has_lmem.
But I was not sure in case every discrete platform mandatory to have lmem region.
If it is guaranteed that every discrete platform will have lmem memory region ?
I will  drop  this patch.
Thanks,
Anshuman Gupta.

  reply	other threads:[~2022-04-25  5:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 12:59 [igt-dev] [PATCH i-g-t] lib/intel_device_info: Add IS_DGFX() support Anshuman Gupta
2022-04-22 14:12 ` Kamil Konieczny
2022-04-22 16:07 ` Dixit, Ashutosh
2022-04-25  5:24   ` Gupta, Anshuman [this message]
2022-04-25  5:44     ` Dixit, Ashutosh
2022-04-25  6:10       ` Gupta, Anshuman
2022-04-25  6:54         ` Dixit, Ashutosh
2022-04-25 12:58       ` Petri Latvala
2022-04-22 16:50 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2022-04-22 17:24 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=6b377d0333494eb1940bd2f96ba15cb8@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=igt-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.