From: Petri Latvala <petri.latvala@intel.com>
To: Talla Raviteja Goud <ravitejax.goud.talla@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] lib: sync i915_pciids.h with kernel
Date: Wed, 20 Apr 2022 16:50:32 +0300 [thread overview]
Message-ID: <YmAPqDh2NStF3ZPh@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20220420124920.3628871-1-ravitejax.goud.talla@intel.com>
On Wed, Apr 20, 2022 at 06:19:20PM +0530, Talla Raviteja Goud wrote:
> From: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
>
> Adding Raptor lake P platform definitions
>
> Signed-off-by: Adam Miszczak <adam.miszczak@intel.com>
> Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Signed-off-by: Raviteja Goud Talla <ravitejax.goud.talla@intel.com>
Write the kernel commit sha the file is copied from in the commit
message. And change intel_device_info.c in a separate commit.
See git log lib/i915_pciids.h for examples.
--
Petri Latvala
> ---
> lib/i915_pciids.h | 9 +++++++++
> lib/intel_device_info.c | 1 +
> 2 files changed, 10 insertions(+)
>
> diff --git a/lib/i915_pciids.h b/lib/i915_pciids.h
> index 533890dc..f4b21a26 100644
> --- a/lib/i915_pciids.h
> +++ b/lib/i915_pciids.h
> @@ -681,4 +681,13 @@
> INTEL_VGA_DEVICE(0xA788, info), \
> INTEL_VGA_DEVICE(0xA789, info)
>
> +/*RPL-P */
> +#define INTEL_RPLP_IDS(info) \
> + INTEL_VGA_DEVICE(0xA720, info), \
> + INTEL_VGA_DEVICE(0xA721, info), \
> + INTEL_VGA_DEVICE(0xA7A0, info), \
> + INTEL_VGA_DEVICE(0xA7A1, info), \
> + INTEL_VGA_DEVICE(0xA7A8, info), \
> + INTEL_VGA_DEVICE(0xA7A9, info)
> +
> #endif /* _I915_PCIIDS_H */
> diff --git a/lib/intel_device_info.c b/lib/intel_device_info.c
> index e55841df..0253a732 100644
> --- a/lib/intel_device_info.c
> +++ b/lib/intel_device_info.c
> @@ -521,6 +521,7 @@ static const struct pci_id_match intel_device_match[] = {
> INTEL_ADLS_IDS(&intel_alderlake_s_info),
> INTEL_RPLS_IDS(&intel_raptorlake_s_info),
> INTEL_ADLP_IDS(&intel_alderlake_p_info),
> + INTEL_RPLP_IDS(&intel_alderlake_p_info),
> INTEL_ADLN_IDS(&intel_alderlake_n_info),
>
> INTEL_VGA_DEVICE(PCI_MATCH_ANY, &intel_generic_info),
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-04-20 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 12:49 [igt-dev] [i-g-t] lib: sync i915_pciids.h with kernel Talla Raviteja Goud
2022-04-20 13:19 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: sync i915_pciids.h with kernel (rev11) Patchwork
2022-04-20 13:50 ` Petri Latvala [this message]
2022-04-20 15:22 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 4:34 [igt-dev] [PATCH i-g-t] lib: sync i915_pciids.h with kernel Matt Roper
2022-08-03 15:00 ` [igt-dev] [i-g-t] " Wayne Boyer
2021-12-16 11:15 Tejas Upadhyay
2021-12-16 11:27 ` Petri Latvala
2021-12-16 11:37 ` Surendrakumar Upadhyay, TejaskumarX
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=YmAPqDh2NStF3ZPh@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ravitejax.goud.talla@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