All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matt Atwood <matthew.s.atwood@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH] lib/pciids: Sync pci id changes for DG2/MTL/BMG/PTL
Date: Thu, 6 Feb 2025 14:35:31 -0500	[thread overview]
Message-ID: <Z6UPA-zaG1AwWAlX@intel.com> (raw)
In-Reply-To: <Z6UMzbDHC9vMPRI2@msatwood-mobl>

On Thu, Feb 06, 2025 at 11:26:05AM -0800, Matt Atwood wrote:
> On Thu, Feb 06, 2025 at 10:01:13AM -0800, Matt Roper wrote:
> > On Thu, Feb 06, 2025 at 09:06:32AM -0800, Matt Atwood wrote:
> > > On Wed, Feb 05, 2025 at 03:30:55PM -0800, Matt Roper wrote:
> > > > On Tue, Feb 04, 2025 at 09:53:02AM -0800, Matt Atwood wrote:
> > > > > There have been several changes to pciids upstream that need to be
> > > > > sync'd into igt.
> > > > > 
> > > > > Sync with the following kernel commits:
> > > > > f9a15b968dce ("drm/intel/pciids: Refactor DG2 PCI IDs into segment
> > > > > ranges")
> > > > > e35ecd95ecf2 ("drm/i915/display: Add MTL subplatforms definition")
> > > > > fa8ffaae1b15 ("drm/xe/bmg: Add new PCI IDs")
> > > > > 16016ade13f6 ("drm/xe/ptl: Update the PTL pci id table")
> > > > 
> > > > The updates below look correct (they match the kernel header), but the
> > > > commit message here is confusing.  IGT updates to this file generally
> > > > specify which actual kernel commit you're synchronizing against; none of
> > > > the four listed above match the content you've copied here because there
> > > > are additional changes not present in those.
> > > Because there are now several out of sync next branches, saying as
> > > of this commit idea was not working. Hence this approach.
> > 
> > You should generally be syncing with drm-next after things land there.
> > So which drm-next commit are you syncing with for this commit?
> They hadnt been in a drm-next commit yet. At the time it was just after
> a next cut, at this point we can probably just wait for them to land.

I agree with Atwood here. We had changes coming from drm-intel-next
and changes coming to drm-xe-next. In the kernel history the changes
coming from drm-xe-next are on top of the drm-intel-next ones. But
they landed first here in the IGT.

Now it is in a situation that individual patches from drm-intel-next
would conflict here badly. The safest thing is to keep it simple and
use a single patch like this.

This is the final copy of the file directly with the proper mention
to the commit ids. I really believe we should just go ahead and push
this to finalize the alignment before something else gets in the way.

> 
> MattA
> > 
> > 
> > Matt
> > 
> > > 
> > > MattA
> > > > 
> > > > 
> > > > Matt
> > > > 
> > > > > 
> > > > > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > > > > ---
> > > > >  lib/pciids.h | 62 +++++++++++++++++++++++++++++++++++++++-------------
> > > > >  1 file changed, 47 insertions(+), 15 deletions(-)
> > > > > 
> > > > > diff --git a/lib/pciids.h b/lib/pciids.h
> > > > > index 23f349f65..4736ea525 100644
> > > > > --- a/lib/pciids.h
> > > > > +++ b/lib/pciids.h
> > > > > @@ -717,37 +717,66 @@
> > > > >  	MACRO__(0xA7AB, ## __VA_ARGS__)
> > > > >  
> > > > >  /* DG2 */
> > > > > -#define INTEL_DG2_G10_IDS(MACRO__, ...) \
> > > > > -	MACRO__(0x5690, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x5691, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x5692, ## __VA_ARGS__), \
> > > > > +#define INTEL_DG2_G10_D_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x56A0, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56A1, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x56A2, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x56A2, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G10_E_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x56BE, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56BF, ## __VA_ARGS__)
> > > > >  
> > > > > -#define INTEL_DG2_G11_IDS(MACRO__, ...) \
> > > > > -	MACRO__(0x5693, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x5694, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x5695, ## __VA_ARGS__), \
> > > > > +#define INTEL_DG2_G10_M_IDS(MACRO__, ...) \
> > > > > +	MACRO__(0x5690, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x5691, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x5692, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G10_IDS(MACRO__, ...) \
> > > > > +	INTEL_DG2_G10_D_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G10_E_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G10_M_IDS(MACRO__, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G11_D_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x56A5, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56A6, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56B0, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x56B1, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x56B1, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G11_E_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x56BA, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56BB, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56BC, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56BD, ## __VA_ARGS__)
> > > > >  
> > > > > -#define INTEL_DG2_G12_IDS(MACRO__, ...) \
> > > > > -	MACRO__(0x5696, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x5697, ## __VA_ARGS__), \
> > > > > +#define INTEL_DG2_G11_M_IDS(MACRO__, ...) \
> > > > > +	MACRO__(0x5693, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x5694, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x5695, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G11_IDS(MACRO__, ...) \
> > > > > +	INTEL_DG2_G11_D_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G11_E_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G11_M_IDS(MACRO__, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G12_D_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x56A3, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56A4, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56B2, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x56B3, ## __VA_ARGS__)
> > > > >  
> > > > > +#define INTEL_DG2_G12_M_IDS(MACRO__, ...) \
> > > > > +	MACRO__(0x5696, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x5697, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_G12_IDS(MACRO__, ...) \
> > > > > +	INTEL_DG2_G12_D_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G12_M_IDS(MACRO__, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_DG2_D_IDS(MACRO__, ...) \
> > > > > +	INTEL_DG2_G10_D_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G11_D_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > +	INTEL_DG2_G12_D_IDS(MACRO__, ## __VA_ARGS__)
> > > > > +
> > > > >  #define INTEL_DG2_IDS(MACRO__, ...) \
> > > > >  	INTEL_DG2_G10_IDS(MACRO__, ## __VA_ARGS__), \
> > > > >  	INTEL_DG2_G11_IDS(MACRO__, ## __VA_ARGS__), \
> > > > > @@ -782,9 +811,12 @@
> > > > >  	INTEL_ARL_S_IDS(MACRO__, ## __VA_ARGS__)
> > > > >  
> > > > >  /* MTL */
> > > > > -#define INTEL_MTL_IDS(MACRO__, ...) \
> > > > > +#define INTEL_MTL_U_IDS(MACRO__, ...) \
> > > > >  	MACRO__(0x7D40, ## __VA_ARGS__), \
> > > > > -	MACRO__(0x7D45, ## __VA_ARGS__), \
> > > > > +	MACRO__(0x7D45, ## __VA_ARGS__)
> > > > > +
> > > > > +#define INTEL_MTL_IDS(MACRO__, ...) \
> > > > > +	INTEL_MTL_U_IDS(MACRO__, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x7D55, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x7D60, ## __VA_ARGS__), \
> > > > >  	MACRO__(0x7DD5, ## __VA_ARGS__)
> > > > > -- 
> > > > > 2.45.0
> > > > > 
> > > > 
> > > > -- 
> > > > Matt Roper
> > > > Graphics Software Engineer
> > > > Linux GPU Platform Enablement
> > > > Intel Corporation
> > 
> > -- 
> > Matt Roper
> > Graphics Software Engineer
> > Linux GPU Platform Enablement
> > Intel Corporation

  reply	other threads:[~2025-02-06 19:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 17:53 [PATCH] lib/pciids: Sync pci id changes for DG2/MTL/BMG/PTL Matt Atwood
2025-02-04 18:16 ` Rodrigo Vivi
2025-02-05  1:14 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-02-05  1:15 ` ✓ i915.CI.BAT: " Patchwork
2025-02-05  7:05 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-05  9:13 ` ✗ i915.CI.Full: " Patchwork
2025-02-05 23:30 ` [PATCH] " Matt Roper
2025-02-06 17:06   ` Matt Atwood
2025-02-06 18:01     ` Matt Roper
2025-02-06 19:26       ` Matt Atwood
2025-02-06 19:35         ` Rodrigo Vivi [this message]
2025-02-06 19:44           ` Matt Roper
2025-02-07 21:04             ` Lucas De Marchi
2025-02-10 17:44               ` Rodrigo Vivi

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=Z6UPA-zaG1AwWAlX@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=matthew.s.atwood@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.