All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: [PATCH net-next 01/11] nfp: remove defines for unused control bits
Date: Fri, 11 Mar 2022 11:42:56 +0100	[thread overview]
Message-ID: <20220311104306.28357-2-simon.horman@corigine.com> (raw)
In-Reply-To: <20220311104306.28357-1-simon.horman@corigine.com>

From: Jakub Kicinski <jakub.kicinski@netronome.com>

NFP driver ABI contains bits for L2 switching and ring
prioritization which were never implemented in initially
envisioned form.

Remove the defines, and open up the possibility of
reclaiming the bits for other uses.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: Fei Qin <fei.qin@corigine.com>
Signed-off-by: Simon Horman <simon.horman@corigine.com>
---
 drivers/net/ethernet/netronome/nfp/nfp_net_ctrl.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_ctrl.h b/drivers/net/ethernet/netronome/nfp/nfp_net_ctrl.h
index 50007cc5b580..33fd32478905 100644
--- a/drivers/net/ethernet/netronome/nfp/nfp_net_ctrl.h
+++ b/drivers/net/ethernet/netronome/nfp/nfp_net_ctrl.h
@@ -92,7 +92,6 @@
 #define   NFP_NET_CFG_CTRL_RINGCFG	  (0x1 << 16) /* Ring runtime changes */
 #define   NFP_NET_CFG_CTRL_RSS		  (0x1 << 17) /* RSS (version 1) */
 #define   NFP_NET_CFG_CTRL_IRQMOD	  (0x1 << 18) /* Interrupt moderation */
-#define   NFP_NET_CFG_CTRL_RINGPRIO	  (0x1 << 19) /* Ring priorities */
 #define   NFP_NET_CFG_CTRL_MSIXAUTO	  (0x1 << 20) /* MSI-X auto-masking */
 #define   NFP_NET_CFG_CTRL_TXRWB	  (0x1 << 21) /* Write-back of TX ring*/
 #define   NFP_NET_CFG_CTRL_VXLAN	  (0x1 << 24) /* VXLAN tunnel support */
-- 
2.30.2


  reply	other threads:[~2022-03-11 10:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 10:42 [PATCH net-next 0/11] nfp: preliminary support for NFP-3800 Simon Horman
2022-03-11 10:42 ` Simon Horman [this message]
2022-03-11 10:42 ` [PATCH net-next 02/11] nfp: remove pessimistic NFP_QCP_MAX_ADD limits Simon Horman
2022-03-11 10:42 ` [PATCH net-next 03/11] nfp: use PCI_DEVICE_ID_NETRONOME_NFP6000_VF for VFs instead Simon Horman
2022-03-11 10:42 ` [PATCH net-next 04/11] nfp: use PluDevice register for model for non-NFP6000 chips Simon Horman
2022-03-11 10:43 ` [PATCH net-next 05/11] nfp: sort the device ID tables Simon Horman
2022-03-11 10:43 ` [PATCH net-next 06/11] nfp: introduce dev_info static chip data Simon Horman
2022-03-11 10:43 ` [PATCH net-next 07/11] nfp: use dev_info for PCIe config space BAR offsets Simon Horman
2022-03-11 10:43 ` [PATCH net-next 08/11] nfp: use dev_info for the DMA mask Simon Horman
2022-03-11 10:43 ` [PATCH net-next 09/11] nfp: parametrize QCP offset/size using dev_info Simon Horman
2022-03-11 10:43 ` [PATCH net-next 10/11] nfp: take chip version into account for ring sizes Simon Horman
2022-03-11 10:43 ` [PATCH net-next 11/11] nfp: add support for NFP3800/NFP3803 PCIe devices Simon Horman
2022-03-12  7:40 ` [PATCH net-next 0/11] nfp: preliminary support for NFP-3800 patchwork-bot+netdevbpf

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=20220311104306.28357-2-simon.horman@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.