Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "K V P, Satyanarayana" <satyanarayana.k.v.p@intel.com>
To: Jakub Kolakowski <jakub1.kolakowski@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <satyanarayana.k.v.p@intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/sriov: Mark BMG as SR-IOV capable
Date: Thu, 10 Jul 2025 16:14:59 +0530	[thread overview]
Message-ID: <430401fa-0684-4096-9bc3-d982e9e0e3a3@intel.com> (raw)
In-Reply-To: <20250710103040.375610-3-jakub1.kolakowski@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]


On 10-07-2025 16:00, Jakub Kolakowski wrote:
> From: Michal Wajdeczko<michal.wajdeczko@intel.com>
>
> Enable SRIOV support for BMG platforms.
>
> Signed-off-by: Michal Wajdeczko<michal.wajdeczko@intel.com>
> Tested-by: Jakub Kolakowski<jakub1.kolakowski@intel.com>
> Cc: Michal Wajdeczko<michal.wajdeczko@intel.com>
> Cc: Lucas De Marchi<lucas.demarchi@intel.com>
> Cc: Satyanarayana K V P<satyanarayana.k.v.p@intel.com>
> ---
> V1 -> V2:
> - updated commit message (Satyanarayana K V P)
> ---
>   drivers/gpu/drm/xe/xe_pci.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index e9c5d3150efc..0f5147e26ee4 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -331,6 +331,7 @@ static const struct xe_device_desc bmg_desc = {
>   	.has_mbx_power_limits = true,
>   	.has_gsc_nvm = 1,
>   	.has_heci_cscfi = 1,
> +	.has_sriov = true,
>   	.max_gt_per_tile = 2,
>   	.needs_scratch = true,
>   };

LGTM.

Reviewed-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com <mailto:satyanarayana.k.v.p@intel.com>>

[-- Attachment #2: Type: text/html, Size: 2287 bytes --]

  reply	other threads:[~2025-07-10 10:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 10:30 [PATCH v2 0/2] Add SR-IOV support for BMG Jakub Kolakowski
2025-07-10 10:30 ` [PATCH v2 1/2] drm/xe/bmg: Don't use WA 16023588340 and 22019338487 on VF Jakub Kolakowski
2025-07-10 10:42   ` K V P, Satyanarayana
2025-07-10 15:47   ` Kolakowski, Jakub1
2025-07-10 10:30 ` [PATCH v2 2/2] drm/xe/sriov: Mark BMG as SR-IOV capable Jakub Kolakowski
2025-07-10 10:44   ` K V P, Satyanarayana [this message]
2025-07-10 15:52   ` Kolakowski, Jakub1
2025-07-11  3:51     ` Lucas De Marchi
2025-07-10 10:47 ` ✗ CI.checkpatch: warning for Add SR-IOV support for BMG (rev2) Patchwork
2025-07-10 10:48 ` ✓ CI.KUnit: success " Patchwork
2025-07-10 11:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-10 14:49 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-10 16:08 ` ✗ CI.checkpatch: warning for Add SR-IOV support for BMG (rev4) Patchwork
2025-07-10 16:09 ` ✓ CI.KUnit: success " Patchwork
2025-07-10 16:25 ` [PATCH v2 0/2] Add SR-IOV support for BMG Lucas De Marchi
2025-07-10 16:55 ` ✓ Xe.CI.BAT: success for Add SR-IOV support for BMG (rev4) Patchwork
2025-07-10 21:57 ` ✗ Xe.CI.Full: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-07-12  8:49 [PATCH v2 2/2] drm/xe/sriov: Mark BMG as SR-IOV capable Alex Crow

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=430401fa-0684-4096-9bc3-d982e9e0e3a3@intel.com \
    --to=satyanarayana.k.v.p@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.wajdeczko@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