From: Andy Shevchenko <andriy.shevchenko@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>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v11] drm/xe/vsec: Support BMG devices
Date: Thu, 15 Aug 2024 13:55:20 +0300 [thread overview]
Message-ID: <Zr3emGSJGy7Y2VAB@smile.fi.intel.com> (raw)
In-Reply-To: <IA1PR11MB641878A813B6D2EC044BD28FC1872@IA1PR11MB6418.namprd11.prod.outlook.com>
On Wed, Aug 14, 2024 at 08:47:28PM +0000, Ruhl, Michael J wrote:
> > -----Original Message-----
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Wednesday, August 14, 2024 2:41 PM
> > On Wed, Aug 14, 2024 at 04:49:05PM +0000, Ruhl, Michael J wrote:
> > > > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > > Sent: Wednesday, August 14, 2024 9:56 AM On Tue, Aug 13, 2024 at
> > > > 02:29:27PM +0000, Ruhl, Michael J wrote:
> > > > > > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > > > > Sent: Tuesday, August 13, 2024 10:11 AM On Mon, Aug 12, 2024 at
> > > > > > 04:04:22PM -0400, Michael J. Ruhl wrote:
...
> > > > > > > +#define BMG_DEVICE_ID 0xE2F8
> > > > > >
> > > > > > Is this defined in any specification? I mean is the format the
> > > > > > same as PCI device ID?
> > > > >
> > > > > I think that this is defined in BMG PMT yaml definition. It is
> > > > > provide in the PMT discovery data, so it is defined by the specific device.
> > > >
> > > > Is there any documentation / specification about this?
> > > > Can it be UUID or 64-bit number or other format?
> > > > _Where_ is this being specified?
> > >
> > > The GUID is defined by the YAML file associated with the PMT device.
> > > In this case 16 bits are a device ID.
> > >
> > > From the cover letter of the PMT patch set (Intel Platform Monitoring
> > Technology):
> > >
> > > -
> > > The GUID uniquely identifies the register space of any monitor data
> > > exposed by the capability. The GUID is associated with an XML file
> > > from the vendor that describes the mapping of the register space along
> > > with properties of the monitor data.
> > > --
> > >
> > > I was told that this was the value to use for this specific device/feature.
> > >
> > > It is specified internally. Not sure if there is any "documentation"
> > > available beyond that.
> >
> > The YAML is *not* the specification. Do we have one that I can access to?
> > And I asked not about GUID, I asked about ID.
>
> Andy,
>
> For the BMG device, the device ID is defined as part PMT GUID, and
> will be defined by the BMG PMT YAML specification.
>
> So this is a vendor defined value.
Okay, thank you for clarification.
> Need to do some testing, and then I will re-post the patch.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-08-15 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 20:04 [PATCH v11] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-08-12 20:11 ` ✗ CI.Patch_applied: failure for drm/xe/vsec: Support BMG devices (rev3) Patchwork
2024-08-13 14:11 ` [PATCH v11] drm/xe/vsec: Support BMG devices Andy Shevchenko
2024-08-13 14:29 ` Ruhl, Michael J
2024-08-14 13:56 ` Andy Shevchenko
2024-08-14 16:49 ` Ruhl, Michael J
2024-08-14 18:41 ` Andy Shevchenko
2024-08-14 20:47 ` Ruhl, Michael J
2024-08-15 10:55 ` Andy Shevchenko [this message]
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=Zr3emGSJGy7Y2VAB@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=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.