From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: "David E. Box" <david.e.box@linux.intel.com>,
nirmal.patel@linux.intel.com, jonathan.derrick@linux.dev,
lorenzo.pieralisi@arm.com, hch@infradead.org, kw@linux.com,
robh@kernel.org, bhelgaas@google.com,
michael.a.bottini@intel.com, rafael@kernel.org,
me@adhityamohan.in
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V8 RESEND 3/4] PCI: vmd: Create feature grouping for client products
Date: Fri, 18 Nov 2022 21:47:28 -0800 [thread overview]
Message-ID: <a4671c99-4d7f-ca80-e3fd-2042de4fed62@linux.intel.com> (raw)
In-Reply-To: <20221119021411.1383248-4-david.e.box@linux.intel.com>
On 11/18/22 6:14 PM, David E. Box wrote:
> Simplify the device ID list by creating a grouping of features shared by
> client products.
>
> Suggested-by: Jon Derrick <jonathan.derrick@linux.dev>
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> ---
>
Looks good to me.
Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> V8 - New patch.
>
> drivers/pci/controller/vmd.c | 28 ++++++++++------------------
> 1 file changed, 10 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c
> index 9dedca714c18..86f3085db014 100644
> --- a/drivers/pci/controller/vmd.c
> +++ b/drivers/pci/controller/vmd.c
> @@ -68,6 +68,10 @@ enum vmd_features {
> VMD_FEAT_CAN_BYPASS_MSI_REMAP = (1 << 4),
> };
>
> +#define VMD_FEATS_CLIENT (VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP | \
> + VMD_FEAT_HAS_BUS_RESTRICTIONS | \
> + VMD_FEAT_OFFSET_FIRST_VECTOR)
> +
> static DEFINE_IDA(vmd_instance_ida);
>
> /*
> @@ -1001,29 +1005,17 @@ static const struct pci_device_id vmd_ids[] = {
> VMD_FEAT_HAS_BUS_RESTRICTIONS |
> VMD_FEAT_CAN_BYPASS_MSI_REMAP,},
> {PCI_VDEVICE(INTEL, 0x467f),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {PCI_VDEVICE(INTEL, 0x4c3d),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {PCI_VDEVICE(INTEL, 0xa77f),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {PCI_VDEVICE(INTEL, 0x7d0b),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {PCI_VDEVICE(INTEL, 0xad0b),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_VMD_9A0B),
> - .driver_data = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP |
> - VMD_FEAT_HAS_BUS_RESTRICTIONS |
> - VMD_FEAT_OFFSET_FIRST_VECTOR,},
> + .driver_data = VMD_FEATS_CLIENT,},
> {0,}
> };
> MODULE_DEVICE_TABLE(pci, vmd_ids);
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2022-11-19 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 2:14 [PATCH V8 RESEND 0/4] PCI: vmd: Enable PCIe ASPM and LTR on select David E. Box
2022-11-19 2:14 ` [PATCH V8 RESEND 1/4] PCI/ASPM: Add pci_enable_link_state() David E. Box
2022-11-19 5:43 ` Sathyanarayanan Kuppuswamy
2022-11-19 2:14 ` [PATCH V8 RESEND 2/4] PCI: vmd: Use PCI_VDEVICE in device list David E. Box
2022-11-19 2:14 ` [PATCH V8 RESEND 3/4] PCI: vmd: Create feature grouping for client products David E. Box
2022-11-19 5:47 ` Sathyanarayanan Kuppuswamy [this message]
2022-11-19 2:14 ` [PATCH V8 RESEND 4/4] PCI: vmd: Add quirk to configure PCIe ASPM and LTR David E. Box
2022-11-19 5:50 ` Sathyanarayanan Kuppuswamy
2022-11-21 3:30 ` David E. Box
2022-11-21 3:47 ` Sathyanarayanan Kuppuswamy
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=a4671c99-4d7f-ca80-e3fd-2042de4fed62@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=hch@infradead.org \
--cc=jonathan.derrick@linux.dev \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=me@adhityamohan.in \
--cc=michael.a.bottini@intel.com \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@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).