Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@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, matthew.brost@intel.com
Subject: Re: [PATCH v5 2/6] platform/x86/intel/vsec: Add PMT read callbacks
Date: Sat, 6 Jul 2024 16:32:25 +0300 (EEST)	[thread overview]
Message-ID: <92c284d5-84ed-f2c5-0506-d1d5ab484362@linux.intel.com> (raw)
In-Reply-To: <20240701141730.3585133-3-michael.j.ruhl@intel.com>

On Mon, 1 Jul 2024, Michael J. Ruhl wrote:

> From: "David E. Box" <david.e.box@linux.intel.com>
> 
> Some PMT providers require device specific actions before their telemetry
> can be read. Provide assignable PMT read callbacks to allow providers to
> perform those actions.
> 
> Reviewed-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> ---
>  drivers/platform/x86/intel/vsec.c | 1 +
>  include/linux/intel_vsec.h        | 5 +++++
>  2 files changed, 6 insertions(+)
> 
> diff --git a/drivers/platform/x86/intel/vsec.c b/drivers/platform/x86/intel/vsec.c
> index 2b46807f868b..7b5cc9993974 100644
> --- a/drivers/platform/x86/intel/vsec.c
> +++ b/drivers/platform/x86/intel/vsec.c
> @@ -212,6 +212,7 @@ static int intel_vsec_add_dev(struct pci_dev *pdev, struct intel_vsec_header *he
>  	intel_vsec_dev->num_resources = header->num_entries;
>  	intel_vsec_dev->quirks = info->quirks;
>  	intel_vsec_dev->base_addr = info->base_addr;
> +	intel_vsec_dev->priv_data = info->priv_data;
>  
>  	if (header->id == VSEC_ID_SDSI)
>  		intel_vsec_dev->ida = &intel_vsec_sdsi_ida;
> diff --git a/include/linux/intel_vsec.h b/include/linux/intel_vsec.h
> index ff7998cadab4..003301783331 100644
> --- a/include/linux/intel_vsec.h
> +++ b/include/linux/intel_vsec.h
> @@ -67,10 +67,15 @@ enum intel_vsec_quirks {
>  	VSEC_QUIRK_EARLY_HW     = BIT(4),
>  };
>  
> +struct pmt_callbacks {
> +	int (*read_telem)(void *args, u32 guid, u64 *data, u32 count);
> +};

Please add kerneldoc.

> +
>  /* Platform specific data */
>  struct intel_vsec_platform_info {
>  	struct device *parent;
>  	struct intel_vsec_header **headers;
> +	void *priv_data;
>  	unsigned long caps;
>  	unsigned long quirks;
>  	u64 base_addr;

Where's the kerneldoc for this struct?

I know you moved things around in the earlier patch, but moving things 
into kernel-wide scope comes with a higher standard on documenting things.

-- 
 i.


  reply	other threads:[~2024-07-06 13:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 14:17 [PATCH v5 0/6] Support PMT features in Xe Michael J. Ruhl
2024-07-01 14:17 ` [PATCH v5 1/6] platform/x86/intel/vsec.h: Move to include/linux Michael J. Ruhl
2024-07-01 14:17 ` [PATCH v5 2/6] platform/x86/intel/vsec: Add PMT read callbacks Michael J. Ruhl
2024-07-06 13:32   ` Ilpo Järvinen [this message]
2024-07-01 14:17 ` [PATCH v5 3/6] platform/x86/intel/pmt: Use PMT callbacks Michael J. Ruhl
2024-07-01 14:17 ` [PATCH v5 4/6] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-07-06 13:31   ` Ilpo Järvinen
2024-07-08 20:04     ` Ruhl, Michael J
2024-07-01 14:17 ` [PATCH v5 5/6] platform/x86/intel/pmt: Add support for PMT base adjust Michael J. Ruhl
2024-07-01 14:17 ` [PATCH v5 6/6] drm/xe/vsec: Add support for DG2 Michael J. Ruhl
2024-07-01 18:10 ` ✓ CI.Patch_applied: success for Support PMT features in Xe (rev6) Patchwork
2024-07-01 18:11 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-01 18:12 ` ✓ CI.KUnit: success " Patchwork
2024-07-01 18:24 ` ✓ CI.Build: " Patchwork
2024-07-01 18:26 ` ✓ CI.Hooks: " Patchwork
2024-07-01 18:28 ` ✓ CI.checksparse: " Patchwork
2024-07-01 18:50 ` ✓ CI.BAT: " Patchwork
2024-07-01 20:11 ` ✗ CI.FULL: failure " 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=92c284d5-84ed-f2c5-0506-d1d5ab484362@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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