From: Yoshihiro Shimoda Date: Tue, 11 Jun 2024 12:50:57 +0000 (+0900) Subject: misc: pci_endpoint_test: Document policy about adding pci_device_id X-Git-Tag: microblaze-v6.13~601^2~19^2~2 X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=76084965a91df915c47f59c938bb5b8eb467b16e;p=linux-2.6-microblaze.git misc: pci_endpoint_test: Document policy about adding pci_device_id Add a comment suggesting that if the endpoint controller Vendor and Device ID are programmable, an existing entry might be usable for testing without having to add an entry to pci_endpoint_test_tbl[]. Link: https://lore.kernel.org/linux-pci/20240611125057.1232873-6-yoshihiro.shimoda.uh@renesas.com Signed-off-by: Yoshihiro Shimoda Signed-off-by: Krzysztof Wilczyński Signed-off-by: Bjorn Helgaas Reviewed-by: Manivannan Sadhasivam Reviewed-by: Frank Li --- diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c index 0ffc8e02b863..edced893221e 100644 --- a/drivers/misc/pci_endpoint_test.c +++ b/drivers/misc/pci_endpoint_test.c @@ -1014,6 +1014,10 @@ static const struct pci_endpoint_test_data rk3588_data = { .irq_type = IRQ_TYPE_MSI, }; +/* + * If the controller's Vendor/Device ID are programmable, you may be able to + * use one of the existing entries for testing instead of adding a new one. + */ static const struct pci_device_id pci_endpoint_test_tbl[] = { { PCI_DEVICE(PCI_VENDOR_ID_TI, PCI_DEVICE_ID_TI_DRA74x), .driver_data = (kernel_ulong_t)&default_data,