Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Ruhl, Michael J" <michael.j.ruhl@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	 "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	 "david.e.box@linux.intel.com" <david.e.box@linux.intel.com>,
	 "Brost, Matthew" <matthew.brost@intel.com>,
	 "andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>
Subject: RE: [PATCH v9 5/6] platform/x86/intel/pmt: Add support for PMT base adjust
Date: Tue, 30 Jul 2024 16:08:34 +0300 (EEST)	[thread overview]
Message-ID: <9c8cbcf0-1f9b-64c6-9dc5-110f09f98d1d@linux.intel.com> (raw)
In-Reply-To: <IA1PR11MB6418A4F423C1D099EA5A2395C1B02@IA1PR11MB6418.namprd11.prod.outlook.com>

On Tue, 30 Jul 2024, Ruhl, Michael J wrote:

> >-----Original Message-----
> >From: Ruhl, Michael J <michael.j.ruhl@intel.com>
> >Sent: Thursday, July 25, 2024 8:24 AM
> >To: intel-xe@lists.freedesktop.org; platform-driver-x86@vger.kernel.org;
> >david.e.box@linux.intel.com; ilpo.jarvinen@linux.intel.com; Brost, Matthew
> ><matthew.brost@intel.com>; andriy.shevchenko@linux.intel.com
> >Cc: Ruhl, Michael J <michael.j.ruhl@intel.com>
> >Subject: [PATCH v9 5/6] platform/x86/intel/pmt: Add support for PMT base
> >adjust
> >
> >DVSEC offsets are based on the endpoint BAR.  If an endpoint is
> >not available allow the offset information to be adjusted by the
> >parent driver.
> 
> Hello,
> 
> Any further comments or questions WRT this patch?

Hi,

Please don't send take notice of my patch/series asap emails. Especially 
this close to the original sending, at minimum wait at least 2 weeks. But 
in case of platform-drivers-x86, that's hardly necessary even then as we 
don't forget patches, they're tracked in patchwork which is kept up to 
date. You can find you if your patch is still in the queue from the 
patchwork, if it is, we'll get to it eventually.

A maintainer (or some reviewer, if we're lucky :-)) will get to your 
patch/series eventually. People just have many things to do and have to 
prioritize their time. We're barely past the merge window so there's 
plenty of time in this cycle and this tends to be the busiest time of the 
cycle.

-- 
 i.

> >Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
> >---
> > drivers/platform/x86/intel/pmt/class.h     | 1 +
> > drivers/platform/x86/intel/pmt/telemetry.c | 9 +++++++++
> > drivers/platform/x86/intel/vsec.c          | 1 +
> > include/linux/intel_vsec.h                 | 3 +++
> > 4 files changed, 14 insertions(+)
> >
> >diff --git a/drivers/platform/x86/intel/pmt/class.h
> >b/drivers/platform/x86/intel/pmt/class.h
> >index a267ac964423..984cd40ee814 100644
> >--- a/drivers/platform/x86/intel/pmt/class.h
> >+++ b/drivers/platform/x86/intel/pmt/class.h
> >@@ -46,6 +46,7 @@ struct intel_pmt_entry {
> > 	void __iomem		*base;
> > 	struct pmt_callbacks	*cb;
> > 	unsigned long		base_addr;
> >+	s32			base_adjust;
> > 	size_t			size;
> > 	u32			guid;
> > 	int			devid;
> >diff --git a/drivers/platform/x86/intel/pmt/telemetry.c
> >b/drivers/platform/x86/intel/pmt/telemetry.c
> >index c9feac859e57..88e4f1315097 100644
> >--- a/drivers/platform/x86/intel/pmt/telemetry.c
> >+++ b/drivers/platform/x86/intel/pmt/telemetry.c
> >@@ -78,6 +78,13 @@ static int pmt_telem_header_decode(struct
> >intel_pmt_entry *entry,
> > 	header->access_type = TELEM_ACCESS(readl(disc_table));
> > 	header->guid = readl(disc_table + TELEM_GUID_OFFSET);
> > 	header->base_offset = readl(disc_table + TELEM_BASE_OFFSET);
> >+	if (entry->base_adjust) {
> >+		u32 new_base = header->base_offset + entry->base_adjust;
> >+
> >+		dev_dbg(dev, "Adjusting base offset from 0x%x to 0x%x\n",
> >+			header->base_offset, new_base);
> >+		header->base_offset = new_base;
> >+	}
> >
> > 	/* Size is measured in DWORDS, but accessor returns bytes */
> > 	header->size = TELEM_SIZE(readl(disc_table));
> >@@ -302,6 +309,8 @@ static int pmt_telem_probe(struct auxiliary_device
> >*auxdev, const struct auxilia
> > 	for (i = 0; i < intel_vsec_dev->num_resources; i++) {
> > 		struct intel_pmt_entry *entry = &priv->entry[priv-
> >>num_entries];
> >
> >+		entry->base_adjust = intel_vsec_dev->base_adjust;
> >+
> > 		mutex_lock(&ep_lock);
> > 		ret = intel_pmt_dev_create(entry, &pmt_telem_ns,
> >intel_vsec_dev, i);
> > 		mutex_unlock(&ep_lock);
> >diff --git a/drivers/platform/x86/intel/vsec.c
> >b/drivers/platform/x86/intel/vsec.c
> >index 7b5cc9993974..be079d62a7bc 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->base_adjust = info->base_adjust;
> > 	intel_vsec_dev->priv_data = info->priv_data;
> >
> > 	if (header->id == VSEC_ID_SDSI)
> >diff --git a/include/linux/intel_vsec.h b/include/linux/intel_vsec.h
> >index 11ee185566c3..75d17fa10d05 100644
> >--- a/include/linux/intel_vsec.h
> >+++ b/include/linux/intel_vsec.h
> >@@ -88,6 +88,7 @@ struct pmt_callbacks {
> >  * @caps:      bitmask of PMT capabilities for the given headers
> >  * @quirks:    bitmask of VSEC device quirks
> >  * @base_addr: allow a base address to be specified (rather than derived)
> >+ * @base_adjust: allow adjustment to base offset information
> >  */
> > struct intel_vsec_platform_info {
> > 	struct device *parent;
> >@@ -96,6 +97,7 @@ struct intel_vsec_platform_info {
> > 	unsigned long caps;
> > 	unsigned long quirks;
> > 	u64 base_addr;
> >+	s32 base_adjust;
> > };
> >
> > /**
> >@@ -121,6 +123,7 @@ struct intel_vsec_device {
> > 	size_t priv_data_size;
> > 	unsigned long quirks;
> > 	u64 base_addr;
> >+	s32 base_adjust;
> > };
> >
> > int intel_vsec_add_aux(struct pci_dev *pdev, struct device *parent,
> >--
> >2.44.0
> 


  reply	other threads:[~2024-07-30 13:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 12:23 [PATCH v9 0/6] Support PMT features in Xe Michael J. Ruhl
2024-07-25 12:23 ` [PATCH v9 1/6] platform/x86/intel/vsec.h: Move to include/linux Michael J. Ruhl
2024-07-25 12:23 ` [PATCH v9 2/6] platform/x86/intel/vsec: Add PMT read callbacks Michael J. Ruhl
2024-07-25 12:23 ` [PATCH v9 3/6] platform/x86/intel/pmt: Use PMT callbacks Michael J. Ruhl
2024-07-25 12:23 ` [PATCH v9 4/6] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-08-07 19:23   ` David E. Box
2024-08-12  9:01   ` Ilpo Järvinen
2024-08-12 17:14     ` Ruhl, Michael J
2024-07-25 12:23 ` [PATCH v9 5/6] platform/x86/intel/pmt: Add support for PMT base adjust Michael J. Ruhl
2024-07-30 12:29   ` Ruhl, Michael J
2024-07-30 13:08     ` Ilpo Järvinen [this message]
2024-08-08 19:49   ` David E. Box
2024-08-08 21:01     ` Rodrigo Vivi
2024-08-09  0:57       ` David E. Box
2024-08-09 18:21         ` Ruhl, Michael J
2024-08-12  9:22           ` Ilpo Järvinen
2024-08-13 16:59             ` Rodrigo Vivi
2024-07-25 12:23 ` [PATCH v9 6/6] drm/xe/vsec: Add support for DG2 Michael J. Ruhl
2024-07-25 13:26 ` ✓ CI.Patch_applied: success for Support PMT features in Xe (rev11) Patchwork
2024-07-25 13:26 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-25 13:27 ` ✓ CI.KUnit: success " Patchwork
2024-07-25 13:39 ` ✓ CI.Build: " Patchwork
2024-07-25 13:41 ` ✓ CI.Hooks: " Patchwork
2024-07-25 13:43 ` ✓ CI.checksparse: " Patchwork
2024-07-25 14:03 ` ✓ CI.BAT: " Patchwork
2024-07-25 16:59 ` ✗ CI.FULL: failure " Patchwork
2024-08-12 14:23 ` [PATCH v9 0/6] Support PMT features in Xe Hans de Goede
2024-08-12 18:13   ` Ruhl, Michael J

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=9c8cbcf0-1f9b-64c6-9dc5-110f09f98d1d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@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