From: Paul Greenwalt <paul.greenwalt@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, andrew@lunn.ch, horms@kernel.org,
anthony.l.nguyen@intel.com,
Pawel Chmielewski <pawel.chmielewski@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Paul Greenwalt <paul.greenwalt@intel.com>
Subject: [PATCH net-next v5 6/6] ice: Hook up 4 E830 devices by adding their IDs
Date: Wed, 18 Oct 2023 19:16:43 -0400 [thread overview]
Message-ID: <20231018231643.2356-7-paul.greenwalt@intel.com> (raw)
In-Reply-To: <20231018231643.2356-1-paul.greenwalt@intel.com>
From: Pawel Chmielewski <pawel.chmielewski@intel.com>
As the previous patches provide support for E830 hardware, add E830
specific IDs to the PCI device ID table, so these devices can now be
probed by the kernel.
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: Pawel Chmielewski <pawel.chmielewski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: Paul Greenwalt <paul.greenwalt@intel.com>
---
drivers/net/ethernet/intel/ice/ice_main.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
index f47db07df679..66095e9b094e 100644
--- a/drivers/net/ethernet/intel/ice/ice_main.c
+++ b/drivers/net/ethernet/intel/ice/ice_main.c
@@ -5611,6 +5611,10 @@ static const struct pci_device_id ice_pci_tbl[] = {
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E823L_1GBE) },
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E823L_QSFP) },
{ PCI_VDEVICE(INTEL, ICE_DEV_ID_E822_SI_DFLT) },
+ { PCI_VDEVICE(INTEL, ICE_DEV_ID_E830_BACKPLANE) },
+ { PCI_VDEVICE(INTEL, ICE_DEV_ID_E830_QSFP56) },
+ { PCI_VDEVICE(INTEL, ICE_DEV_ID_E830_SFP) },
+ { PCI_VDEVICE(INTEL, ICE_DEV_ID_E830_SFP_DD) },
/* required last entry */
{}
};
--
2.41.0
next prev parent reply other threads:[~2023-10-18 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 23:16 [PATCH net-next v5 0/6] ice: Add basic E830 support Paul Greenwalt
2023-10-18 23:16 ` [PATCH net-next v5 1/6] ice: Add E830 device IDs, MAC type and registers Paul Greenwalt
2023-10-25 21:11 ` [Intel-wired-lan] " Brelinski, Tony
2023-10-18 23:16 ` [PATCH net-next v5 2/6] ice: Add 200G speed/phy type use Paul Greenwalt
2023-10-25 21:11 ` [Intel-wired-lan] " Brelinski, Tony
2023-10-18 23:16 ` [PATCH net-next v5 3/6] ice: Add ice_get_link_status_datalen Paul Greenwalt
2023-10-25 21:10 ` [Intel-wired-lan] " Brelinski, Tony
2023-10-18 23:16 ` [PATCH net-next v5 4/6] ice: Add support for E830 DDP package segment Paul Greenwalt
2023-10-25 21:09 ` [Intel-wired-lan] " Brelinski, Tony
2023-10-18 23:16 ` [PATCH net-next v5 5/6] ice: Remove redundant zeroing of the fields Paul Greenwalt
2023-10-25 21:07 ` [Intel-wired-lan] " Brelinski, Tony
2023-10-18 23:16 ` Paul Greenwalt [this message]
2023-10-25 21:05 ` [Intel-wired-lan] [PATCH net-next v5 6/6] ice: Hook up 4 E830 devices by adding their IDs Brelinski, Tony
2023-10-20 0:49 ` [PATCH net-next v5 0/6] ice: Add basic E830 support Jakub Kicinski
2023-10-20 16:54 ` Greenwalt, Paul
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=20231018231643.2356-7-paul.greenwalt@intel.com \
--to=paul.greenwalt@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.chmielewski@intel.com \
/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).