Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] xe/xe_huc_copy: use IS_TIGERLAKE macro
Date: Wed, 5 Apr 2023 08:52:49 +0200	[thread overview]
Message-ID: <20230405085249.1aa1872f@maurocar-mobl2> (raw)
In-Reply-To: <20230404152958.yw5htrfsiyjgoidn@ldmartin-desk2.lan>

Hi Lucas,

On Tue, 4 Apr 2023 08:29:58 -0700
Lucas De Marchi <lucas.demarchi@intel.com> wrote:

> On Tue, Apr 04, 2023 at 09:52:00AM +0200, Mauro Carvalho Chehab wrote:
> >On Mon, 3 Apr 2023 23:27:01 -0700
> >Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> >  
> >> On Tue, Mar 28, 2023 at 10:39:08AM +0200, Mauro Carvalho Chehab wrote:  
> >> >From: Mauro Carvalho Chehab <mchehab@kernel.org>
> >> >
> >> >Instead of hardcoding the PCI IDs at the test, use a macro
> >> >to check if the platform is compatible with the test.
> >> >
> >> >Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>  
> >>
> >> neither this or the previous solution scale well. Can we get this info
> >> from huc_info in debugfs?
> >>
> >> We are already loading HuC in platforms other than TGL  
> >
> >Changing IGT to not use IS_platform macros anymore is not an easy task,
> >as this is used on lots of place, for both i915 and Xe drivers.  
> 
> I'm not talking generically everywhere in igt. I'm talking specifically
> about huc. For i915 there is a query, for xe we don't have it. But the
> same info can be obtained from the huc_info file in debugfs.

Ah, I see. I was thinking that you wanted to replace the IS_platform
macros with something else based on HuC debugfs data.

Yeah, for this specific sense, I fully agree that we need a better
solution to detect HuC and if it has support for whatever functionality
huc-specific tests are exercising.

Regards,
Mauro

      parent reply	other threads:[~2023-04-05  6:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  8:39 [igt-dev] [PATCH i-g-t] xe/xe_huc_copy: use IS_TIGERLAKE macro Mauro Carvalho Chehab
2023-03-28  9:47 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-28 14:14 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-03-28 18:08 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2023-04-04  6:27 ` [igt-dev] [PATCH i-g-t] " Lucas De Marchi
2023-04-04  7:52   ` Mauro Carvalho Chehab
2023-04-04 15:29     ` Lucas De Marchi
2023-04-04 15:32       ` Matt Atwood
2023-04-05  6:52       ` Mauro Carvalho Chehab [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=20230405085249.1aa1872f@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@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