From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, lucas.demarchi@intel.com
Subject: Re: [PATCH 1/2] drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE()
Date: Wed, 04 Sep 2024 13:24:28 +0300 [thread overview]
Message-ID: <877cbrsomb.fsf@intel.com> (raw)
In-Reply-To: <ce15f8f2a6b672155f9728c8e6a5f49d33fafd24.1725443418.git.jani.nikula@intel.com>
On Wed, 04 Sep 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> With IGT no longer using INTEL_VGA_DEVICE(), we can make it kernel
> specific and use designated initializers. Ditto for
> INTEL_QUANTA_VGA_DEVICE(). Remove the superfluous comments while at it.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> ---
>
> IGT INTEL_VGA_DEVICE removal:
>
> https://lore.kernel.org/r/20240902134907.2186238-2-jani.nikula@intel.com
IGT commit e966143f5c5f ("lib/intel_device_info: use dedicated macro for
struct pci_id_match init").
> ---
> include/drm/intel/i915_pciids.h | 35 +++++++++++++--------------------
> 1 file changed, 14 insertions(+), 21 deletions(-)
>
> diff --git a/include/drm/intel/i915_pciids.h b/include/drm/intel/i915_pciids.h
> index 2bf03ebfcf73..6a78df5687c5 100644
> --- a/include/drm/intel/i915_pciids.h
> +++ b/include/drm/intel/i915_pciids.h
> @@ -25,27 +25,20 @@
> #ifndef _I915_PCIIDS_H
> #define _I915_PCIIDS_H
>
> -/*
> - * A pci_device_id struct {
> - * __u32 vendor, device;
> - * __u32 subvendor, subdevice;
> - * __u32 class, class_mask;
> - * kernel_ulong_t driver_data;
> - * };
> - * Don't use C99 here because "class" is reserved and we want to
> - * give userspace flexibility.
> - */
> -#define INTEL_VGA_DEVICE(id, info) { \
> - 0x8086, id, \
> - ~0, ~0, \
> - 0x030000, 0xff0000, \
> - (unsigned long) info }
> -
> -#define INTEL_QUANTA_VGA_DEVICE(info) { \
> - 0x8086, 0x16a, \
> - 0x152d, 0x8990, \
> - 0x030000, 0xff0000, \
> - (unsigned long) info }
> +#ifdef __KERNEL__
> +#define INTEL_VGA_DEVICE(_id, _info) { \
> + PCI_DEVICE(PCI_VENDOR_ID_INTEL, (_id)), \
> + .class = PCI_BASE_CLASS_DISPLAY << 16, .class_mask = 0xff << 16, \
> + .driver_data = (kernel_ulong_t)(_info), \
> +}
> +
> +#define INTEL_QUANTA_VGA_DEVICE(_info) { \
> + .vendor = PCI_VENDOR_ID_INTEL, .device = 0x16a, \
> + .subvendor = 0x152d, .subdevice = 0x8990, \
> + .class = PCI_BASE_CLASS_DISPLAY << 16, .class_mask = 0xff << 16, \
> + .driver_data = (kernel_ulong_t)(_info), \
> +}
> +#endif
>
> #define INTEL_I810_IDS(MACRO__, ...) \
> MACRO__(0x7121, ## __VA_ARGS__), /* I810 */ \
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-04 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 9:51 [PATCH 0/2] drm/i915/pciids: cleanups Jani Nikula
2024-09-04 9:51 ` [PATCH 1/2] drm/i915/pciids: use designated initializers in INTEL_VGA_DEVICE() Jani Nikula
2024-09-04 10:24 ` Jani Nikula [this message]
2024-09-05 17:14 ` Rodrigo Vivi
2024-09-05 18:02 ` Jani Nikula
2024-09-04 9:51 ` [PATCH 2/2] drm/i915/pciids: separate ARL and MTL PCI IDs Jani Nikula
2024-09-05 17:15 ` Rodrigo Vivi
2024-09-05 11:15 ` ✗ Fi.CI.IGT: failure for drm/i915/pciids: cleanups Patchwork
2024-09-05 11:16 ` ✓ Fi.CI.BAT: success " 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=877cbrsomb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).