From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>,
intel-xe@lists.freedesktop.org, gregory.f.germano@intel.com,
Vitasta Wattal <vitasta.wattal@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH] drm/xe/bmg: Add PCI IDs
Date: Wed, 05 Jun 2024 10:43:47 +0300 [thread overview]
Message-ID: <878qzjdebw.fsf@intel.com> (raw)
In-Reply-To: <t3iomfnitxsag5zzgphoo2bdw2zqnfjrb65ql7dd23dsgaqlny@grzcncimpr3w>
On Tue, 04 Jun 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Tue, Jun 04, 2024 at 11:03:51AM GMT, Jani Nikula wrote:
>>On Mon, 03 Jun 2024, Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com> wrote:
>>> From: Matt Roper <matthew.d.roper@intel.com>
>>>
>>> Add the initial set of device IDs for Battlemage.
>>>
>>> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>>> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
>>
>>Please note that since commit 54836ee194f9 ("drm/i915/display: change
>>display probe to identify GMD ID based platforms") you'll also need to
>>add the PCI IDs to i915_pciids.h and add the platform desc in
>>i915/display/intel_display_device.c for display probe.
>
> that was not the plan when we started xe_pciids.h. Now that display side
> will use pci id to find a static desc, I think there's no point in
> keeping the headers separate. Should we unify them?
Plans changed... and I agree we should unify. Though I don't think
there's any rush. The hard part was done when I switched i915 to the
same type of macros as xe uses. But do we want to have a single
include/drm/intel/pciids.h or split by some criteria?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-06-05 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 14:54 [PATCH] drm/xe/bmg: Add PCI IDs Balasubramani Vivekanandan
2024-06-03 16:08 ` Gustavo Sousa
2024-06-04 8:03 ` Jani Nikula
2024-06-04 21:21 ` Lucas De Marchi
2024-06-05 7:43 ` Jani Nikula [this message]
2024-06-04 18:35 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-04 18:36 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-04 18:36 ` ✓ CI.KUnit: success " Patchwork
2024-06-04 18:48 ` ✓ CI.Build: " Patchwork
2024-06-04 18:48 ` ✗ CI.Hooks: failure " Patchwork
2024-06-04 18:50 ` ✓ CI.checksparse: success " Patchwork
2024-06-04 19:33 ` ✓ CI.BAT: " Patchwork
2024-06-05 0:26 ` ✗ CI.FULL: failure " Patchwork
2024-06-12 16:57 ` Matt Roper
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=878qzjdebw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=gregory.f.germano@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=vitasta.wattal@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.