From: "David E. Box" <david.e.box@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: hdegoede@redhat.com, mgross@linux.intel.com, bhelgaas@google.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-pci@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 2/4] MFD: intel_pmt: Remove OOBMSM device
Date: Wed, 30 Jun 2021 14:11:38 -0700 [thread overview]
Message-ID: <f590ee871d0527a12b307f1494cb4c8a91c5e3c2.camel@linux.intel.com> (raw)
In-Reply-To: <YNxENGGctLXmifzj@dell>
On Wed, 2021-06-30 at 11:15 +0100, Lee Jones wrote:
> On Thu, 17 Jun 2021, David E. Box wrote:
>
> > Unlike the other devices in intel_pmt, the Out of Band Management
> > Services
> > Module (OOBMSM) is actually not a PMT dedicated device. It can also
> > be used
> > to describe non-PMT capabilities. Like PMT, these capabilities are
> > also
> > enumerated using PCIe Vendor Specific registers in config space. In
> > order
> > to better support these devices without the confusion of a
> > dependency on
> > MFD_INTEL_PMT, remove the OOBMSM device from intel_pmt so that it
> > can be
> > later placed in its own driver. Since much of the same code will be
> > used by
> > intel_pmt and the new driver, create a new file with symbols to be
> > used by
> > both.
> >
> > While performing this split we need to also handle the creation of
> > platform
> > devices for the non-PMT capabilities. Currently PMT devices are
> > named by
> > their capability (e.g. pmt_telemetry). Instead, generically name
> > them by
> > their capability ID (e.g. intel_extnd_cap_2). This allows the IDs
> > to be
> > created automatically. However, to ensure that unsupported devices
> > aren't
> > created, use an allow list to specify supported capabilities.
> >
> > Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> > ---
> > MAINTAINERS | 1 +
> > drivers/mfd/Kconfig | 4 +
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/intel_extended_caps.c | 208
> > +++++++++++++++++++++
>
> Please consider moving this <whatever this is> out to either
> drivers/pci or drivers/platform/x86.
None of the cell drivers are in MFD, only the PCI drivers from which
the cells are created. I understood that these should be in MFD. But
moving it to drivers/platform/x86 would be fine with me. That keeps the
code together in the same subsystem. Comment from Hans or Andy?
>
> I suggest Andy should also be on Cc.
>
> > drivers/mfd/intel_extended_caps.h | 40 ++++
> > drivers/mfd/intel_pmt.c | 198 ++---------------
> > ---
> > drivers/platform/x86/intel_pmt_crashlog.c | 2 +-
> > drivers/platform/x86/intel_pmt_telemetry.c | 2 +-
> > 8 files changed, 270 insertions(+), 186 deletions(-)
> > create mode 100644 drivers/mfd/intel_extended_caps.c
> > create mode 100644 drivers/mfd/intel_extended_caps.h
>
next prev parent reply other threads:[~2021-06-30 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 21:54 [PATCH 0/4] MFD: intel_pmt: Split OOBMSM from intel_pmt driver David E. Box
2021-06-17 21:54 ` [PATCH 1/4] PCI: Add #defines for accessing PCIE DVSEC fields David E. Box
2021-06-22 15:04 ` Bjorn Helgaas
2021-06-17 21:54 ` [PATCH 2/4] MFD: intel_pmt: Remove OOBMSM device David E. Box
2021-06-30 10:15 ` Lee Jones
2021-06-30 21:11 ` David E. Box [this message]
2021-07-01 8:01 ` Lee Jones
2021-07-01 8:39 ` Hans de Goede
2021-07-01 11:23 ` Lee Jones
[not found] ` <CAHp75Vfn6GKSj6USUPEWiPdhWRYcJbirqhU6aOeB4gruekmocg@mail.gmail.com>
2021-07-01 12:06 ` Lee Jones
[not found] ` <CAHp75VdmnRJKSBZ8dmU=7XsGOZ-wX6EpZhtC3X6JEE0mz-UJNg@mail.gmail.com>
2021-07-01 12:26 ` Lee Jones
2021-07-01 22:41 ` David E. Box
2021-07-01 9:43 ` Andy Shevchenko
2021-06-17 21:54 ` [PATCH 3/4] MFD: Intel Out of Band Management Services Module (OOBMSM) driver David E. Box
2021-06-30 10:17 ` Lee Jones
2021-06-17 21:54 ` [PATCH 4/4] MFD: intel-extended-cap: Add support for PCIe VSEC structures David E. Box
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=f590ee871d0527a12b307f1494cb4c8a91c5e3c2.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 \
/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).