From: "David E. Box" <david.e.box@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
lee.jones@linaro.org, bhelgaas@google.com,
andy.shevchenko@gmail.com
Cc: mgross@linux.intel.com, srinivas.pandruvada@intel.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Add general DVSEC/VSEC support
Date: Thu, 23 Sep 2021 08:44:17 -0700 [thread overview]
Message-ID: <49c93d8b83d668873fbe6dd5798db7a7e9fb5b61.camel@linux.intel.com> (raw)
In-Reply-To: <da8d9c79-d041-b7fa-6ee3-3abfcfcb0ef6@redhat.com>
On Thu, 2021-09-23 at 11:04 +0200, Hans de Goede wrote:
> Hi,
>
> On 9/22/21 11:30 PM, David E. Box wrote:
> > This patch enables general support for Intel defined PCIe VSEC and DVSEC
> > capabilities in the Intel Platform Monitoring Technology (PMT) driver.
> > Though the driver was written exclusively for PMT capabilities, newer DVSEC
> > and VSEC IDs for other capabilities can exist on the same device requiring
> > that the driver handle them.
> >
> > V3 is mostly a resend of V2. It drops a platform/x86 patch that was picked
> > up separately by Hans in the last cycle. It also adds a new patch to
> > support an upcoming capability.
> >
> > David E. Box (5):
> > PCI: Add #defines for accessing PCIE DVSEC fields
> > MFD: intel_pmt: Support non-PMT capabilities
> > MFD: intel_pmt: Add support for PCIe VSEC structures
> > MFD: intel_pmt: Add DG2 support
> > MFD: intel_extended_cap: Add support for Intel SDSi
>
> Since this mostly touches drivers/mfd/intel_pmt.c, I assume this is
> going to get merged through the MFD trees.
Yes. Thanks.
>
> For the few small drivers/platform/x86 changes:
>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
>
> Regards,
>
> Hans
>
>
>
>
>
> >
> > drivers/mfd/intel_pmt.c | 258 +++++++++++++++------
> > drivers/platform/x86/intel/pmt/class.c | 2 +
> > drivers/platform/x86/intel/pmt/crashlog.c | 2 +-
> > drivers/platform/x86/intel/pmt/telemetry.c | 2 +-
> > include/uapi/linux/pci_regs.h | 4 +
> > 5 files changed, 191 insertions(+), 77 deletions(-)
> >
>
prev parent reply other threads:[~2021-09-23 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 21:30 [PATCH v3 0/5] Add general DVSEC/VSEC support David E. Box
2021-09-22 21:30 ` [PATCH v3 1/5] PCI: Add #defines for accessing PCIE DVSEC fields David E. Box
2021-09-27 17:30 ` Bjorn Helgaas
2021-09-22 21:30 ` [PATCH v3 2/5] MFD: intel_pmt: Support non-PMT capabilities David E. Box
2021-09-27 17:36 ` Greg KH
2021-09-27 18:40 ` David E. Box
2021-09-28 5:01 ` Greg KH
2021-09-28 7:54 ` Lee Jones
2021-09-28 9:10 ` Greg KH
2021-09-28 10:03 ` Lee Jones
2021-09-22 21:30 ` [PATCH v3 3/5] MFD: intel_pmt: Add support for PCIe VSEC structures David E. Box
2021-09-22 21:30 ` [PATCH v3 4/5] MFD: intel_pmt: Add DG2 support David E. Box
2021-09-22 21:30 ` [PATCH v3 5/5] MFD: intel_extended_cap: Add support for Intel SDSi David E. Box
2021-09-23 9:04 ` [PATCH v3 0/5] Add general DVSEC/VSEC support Hans de Goede
2021-09-23 15:44 ` David E. Box [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=49c93d8b83d668873fbe6dd5798db7a7e9fb5b61.camel@linux.intel.com \
--to=david.e.box@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@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;
as well as URLs for NNTP newsgroup(s).