Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	platform-driver-x86@vger.kernel.org, david.e.box@linux.intel.com,
	ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com,
	rodrigo.vivi@intel.com, lucas.demarchi@intel.com
Subject: Re: [PATCH 2/2] drm/xe/vsec: Support BMG devices
Date: Mon, 11 Nov 2024 10:39:59 +0200	[thread overview]
Message-ID: <ZzHC338WnoYgVYTA@smile.fi.intel.com> (raw)
In-Reply-To: <20241108201955.2048085-2-michael.j.ruhl@intel.com>

On Fri, Nov 08, 2024 at 03:19:54PM -0500, Michael J. Ruhl wrote:
> The Battlemage (BMG) discrete graphics card supports the
> Platform, Monitoring Technology (PMT) feature directly
> on the primary PCI device.
> 
> Utilize the PMT callback API to add support for the BMG
> devices.

...

> +	drmm_mutex_init(&xe->drm, &xe->pmt.lock);
> +

No error checks? What's the point of the (second) 'm' then?

...

> +/*
> + * Copyright © 2024 Intel Corporation
> + */

Can be one line.

> +#include <linux/bitfield.h>
> +#include <linux/bits.h>
> +#include <linux/cleanup.h>

+ errno.h

> +#include <linux/intel_vsec.h>
> +#include <linux/module.h>
> +#include <linux/mutex.h>
> +#include <linux/pci.h>

+ types.h

> +#include "xe_device.h"
> +#include "xe_device_types.h"
> +#include "xe_drv.h"
> +#include "xe_mmio.h"
> +#include "xe_platform_types.h"
> +#include "xe_pm.h"
> +#include "xe_vsec.h"

+ blank line?

> +#include "regs/xe_pmt.h"

...


I would add a comment here explaining that it's not a PCI ID,
while looking as that.

> +#define BMG_DEVICE_ID 0xE2F8

...

> +static int guid_decode(u32 guid, int *index, u32 *offset)

xe_guid_decode() to avoid any possible churn in the future due to namespace
collision.

...

> +++ b/drivers/gpu/drm/xe/xe_vsec.h


> +/*
> + * Copyright © 2024 Intel Corporation
> + */

One line?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-11-11  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 20:19 [PATCH 1/2] platform/x86/intel/pmt: allow user offset for PMT callbacks Michael J. Ruhl
2024-11-08 20:19 ` [PATCH 2/2] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-11-11  8:39   ` Andy Shevchenko [this message]
2024-11-12 14:48     ` Ruhl, Michael J
2024-11-08 20:39 ` ✓ CI.Patch_applied: success for series starting with [1/2] platform/x86/intel/pmt: allow user offset for PMT callbacks Patchwork
2024-11-08 20:39 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-08 20:41 ` ✓ CI.KUnit: success " Patchwork
2024-11-08 21:01 ` ✓ CI.Build: " Patchwork
2024-11-08 21:03 ` ✓ CI.Hooks: " Patchwork
2024-11-08 21:05 ` ✓ CI.checksparse: " Patchwork
2024-11-08 21:47 ` ✓ CI.BAT: " Patchwork
2024-11-09 23:58 ` ✗ CI.FULL: failure " Patchwork
2024-11-11  8:34 ` [PATCH 1/2] " Andy Shevchenko
2024-11-12 14:38   ` Ruhl, Michael J
2024-11-12 15:27     ` Andy Shevchenko

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=ZzHC338WnoYgVYTA@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --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