From: Lee Jones <lee.jones@linaro.org>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: dvhart@infradead.org, andy@infradead.org,
alexander.h.duyck@linux.intel.com, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/3] mfd: intel_pmt: Add OOBMSM device ID
Date: Tue, 29 Sep 2020 10:51:06 +0100 [thread overview]
Message-ID: <20200929095106.GG6148@dell> (raw)
In-Reply-To: <20200911194549.12780-2-david.e.box@linux.intel.com>
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@linux.intel.com>
> Signed-off-by: David E. Box <david.e.box@linux.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?
> { PCI_DEVICE_DATA(INTEL, PMT_TGL, &tgl_info) },
> { }
> };
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-09-29 9:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 19:45 [PATCH 0/3] intel_pmt: Add Alder Lake and OOB-MSM support David E. Box
2020-09-11 19:45 ` [PATCH 1/3] mfd: intel_pmt: Add OOBMSM device ID David E. Box
2020-09-14 13:01 ` Hans de Goede
2020-09-29 9:51 ` Lee Jones [this message]
2020-09-29 18:19 ` David E. Box
2020-09-30 7:12 ` Lee Jones
2020-09-30 16:50 ` David E. Box
2020-10-01 7:55 ` Lee Jones
2020-09-11 19:45 ` [PATCH 2/3] mfd: intel_pmt: Add Alder Lake (ADL) support David E. Box
2020-09-14 13:01 ` Hans de Goede
2020-09-11 19:45 ` [PATCH 3/3] platform/x86: Intel PMT Crashlog capability driver David E. Box
2020-09-14 13:28 ` Hans de Goede
2020-09-14 18:07 ` Alexander Duyck
2020-09-14 22:35 ` Alexander Duyck
2020-09-17 12:12 ` Hans de Goede
2020-09-17 21:35 ` Alexander Duyck
2020-09-21 13:16 ` Hans de Goede
2020-09-21 13:57 ` Alexander Duyck
2020-09-21 14:02 ` Hans de Goede
2020-09-21 13:18 ` Hans de Goede
2020-09-17 11:48 ` Hans de Goede
2020-09-19 7:58 ` Alexey Budankov
2020-09-21 13:36 ` Alexander Duyck
[not found] ` <69a7e595-1b5c-bfb3-f3e6-16cf5fcc9999@linux.intel.com>
2020-09-21 17:33 ` Alexander Duyck
2020-09-21 17:52 ` Alexey Budankov
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=20200929095106.GG6148@dell \
--to=lee.jones@linaro.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=andy@infradead.org \
--cc=david.e.box@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).