From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.neti, kuba@kernel.org
Cc: Jeb Cramer <jeb.j.cramer@intel.com>,
netdev@vger.kernel.org, sassmann@redhat.com,
anthony.l.nguyen@intel.com, Aaron Brown <aaron.f.brown@intel.com>
Subject: [net-next v2 09/15] ice: Enable Support for FW Override (E82X)
Date: Fri, 13 Nov 2020 13:34:01 -0800 [thread overview]
Message-ID: <20201113213407.2131340-10-anthony.l.nguyen@intel.com> (raw)
In-Reply-To: <20201113213407.2131340-1-anthony.l.nguyen@intel.com>
From: Jeb Cramer <jeb.j.cramer@intel.com>
The driver is able to override the firmware when it comes to supporting
a more lenient link mode. This feature was limited to E810 devices. It
is now extended to E82X devices.
Signed-off-by: Jeb Cramer <jeb.j.cramer@intel.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
---
drivers/net/ethernet/intel/ice/ice_common.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/net/ethernet/intel/ice/ice_common.c b/drivers/net/ethernet/intel/ice/ice_common.c
index 3c600808d0da..59459b6ccb9c 100644
--- a/drivers/net/ethernet/intel/ice/ice_common.c
+++ b/drivers/net/ethernet/intel/ice/ice_common.c
@@ -4261,10 +4261,6 @@ ice_sched_query_elem(struct ice_hw *hw, u32 node_teid,
*/
bool ice_fw_supports_link_override(struct ice_hw *hw)
{
- /* Currently, only supported for E810 devices */
- if (hw->mac_type != ICE_MAC_E810)
- return false;
-
if (hw->api_maj_ver == ICE_FW_API_LINK_OVERRIDE_MAJ) {
if (hw->api_min_ver > ICE_FW_API_LINK_OVERRIDE_MIN)
return true;
--
2.26.2
next prev parent reply other threads:[~2020-11-13 21:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 21:33 [net-next v2 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2020-11-13 Tony Nguyen
2020-11-13 21:33 ` [net-next v2 01/15] ice: cleanup stack hog Tony Nguyen
2020-11-13 21:33 ` [net-next v2 02/15] ice: rename shared Flow Director functions Tony Nguyen
2020-11-13 21:33 ` [net-next v2 03/15] ice: initialize ACL table Tony Nguyen
2020-11-13 22:59 ` Alexander Duyck
2020-11-14 0:15 ` Nguyen, Anthony L
2020-11-14 1:50 ` Alexander Duyck
2020-11-21 0:39 ` Nguyen, Anthony L
2020-11-13 21:33 ` [net-next v2 04/15] ice: initialize ACL scenario Tony Nguyen
2020-11-13 21:33 ` [net-next v2 05/15] ice: create flow profile Tony Nguyen
2020-11-13 21:33 ` [net-next v2 06/15] ice: create ACL entry Tony Nguyen
2020-11-13 21:33 ` [net-next v2 07/15] ice: program " Tony Nguyen
2020-11-13 21:34 ` [net-next v2 08/15] ice: don't always return an error for Get PHY Abilities AQ command Tony Nguyen
2020-11-13 21:34 ` Tony Nguyen [this message]
2020-11-13 21:34 ` [net-next v2 10/15] ice: Remove gate to OROM init Tony Nguyen
2020-11-13 21:34 ` [net-next v2 11/15] ice: Remove vlan_ena from vsi structure Tony Nguyen
2020-11-13 21:34 ` [net-next v2 12/15] ice: cleanup misleading comment Tony Nguyen
2020-11-13 21:34 ` [net-next v2 13/15] ice: silence static analysis warning Tony Nguyen
2020-11-13 21:34 ` [net-next v2 14/15] ice: join format strings to same line as ice_debug Tony Nguyen
2020-11-13 21:34 ` [net-next v2 15/15] ice: Add space to unknown speed Tony Nguyen
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=20201113213407.2131340-10-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aaron.f.brown@intel.com \
--cc=davem@davemloft.neti \
--cc=jeb.j.cramer@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).