[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47276f4aacbf4ec3729e674a573a28cd6399cfd6.camel@linux.intel.com>
Date: Wed, 30 Sep 2020 09:50:15 -0700
From: "David E. Box" <david.e.box@...ux.intel.com>
To: Lee Jones <lee.jones@...aro.org>, hdegoede@...hat.com,
andriy.shevchenko@...ux.intel.com
Cc: dvhart@...radead.org, andy@...radead.org,
alexander.h.duyck@...ux.intel.com, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH 1/3] mfd: intel_pmt: Add OOBMSM device ID
On Wed, 2020-09-30 at 08:12 +0100, Lee Jones wrote:
> On Tue, 29 Sep 2020, David E. Box wrote:
>
> > On Tue, 2020-09-29 at 10:51 +0100, Lee Jones wrote:
> > > On Fri, 11 Sep 2020, David E. Box wrote:
> > >
> > > > Add Out of Band Management Services Module device ID to Intel
> > > > PMT
> > > > driver.
> > > >
> > > > Signed-off-by: Alexander Duyck <
> > > > alexander.h.duyck@...ux.intel.com>
> > > > Signed-off-by: David E. Box <david.e.box@...ux.intel.com>
> > > > ---
> > > > drivers/mfd/intel_pmt.c | 4 ++++
> > > > 1 file changed, 4 insertions(+)
> > > >
> > > > diff --git a/drivers/mfd/intel_pmt.c b/drivers/mfd/intel_pmt.c
> > > > index 0e572b105101..8f9970ab3026 100644
> > > > --- a/drivers/mfd/intel_pmt.c
> > > > +++ b/drivers/mfd/intel_pmt.c
> > > > @@ -55,6 +55,8 @@ struct pmt_platform_info {
> > > > unsigned long quirks;
> > > > };
> > > >
> > > > +static const struct pmt_platform_info pmt_info;
> > > > +
> > > > static const struct pmt_platform_info tgl_info = {
> > > > .quirks = PMT_QUIRK_NO_WATCHER | PMT_QUIRK_NO_CRASHLOG
> > > > |
> > > > PMT_QUIRK_TABLE_SHIFT,
> > > > @@ -200,8 +202,10 @@ static void pmt_pci_remove(struct pci_dev
> > > > *pdev)
> > > > pm_runtime_get_sync(&pdev->dev);
> > > > }
> > > >
> > > > +#define PCI_DEVICE_ID_INTEL_PMT_OOBMSM 0x09a7
> > > > #define PCI_DEVICE_ID_INTEL_PMT_TGL 0x9a0d
> > > > static const struct pci_device_id pmt_pci_ids[] = {
> > > > + { PCI_DEVICE_DATA(INTEL, PMT_OOBMSM, &pmt_info) },
> > >
> > > Why are you supplying an empty struct?
> >
> > Because the OOBMSM device doesn't need code provided driver data,
> > but
> > info is dereferenced in several areas. We also use kmemdup to copy
> > driver_data under the assumption that it was provided. We could
> > allow
> > for NULL if driver_data is referenced directly.
>
> Just check for NULL. No need to create and send bogus data.
Sure. If you haven't already, please note that this patch was pulled
into the V6 series in the link below. You accepted V5 but Hans
suggested some late changes after reviewing the new crashlog driver in
this patchset. So rather than have separate patchsets with a
dependency, we bundled them all into the original. We'll make these
changes in V7 now.
https://lore.kernel.org/patchwork/patch/1313166/
David
Powered by blists - more mailing lists