From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: [net-next V2 01/15] net/mlx5: Add MPIR bit in mcam_access_reg
Date: Wed, 7 Feb 2024 19:53:38 -0800 [thread overview]
Message-ID: <20240208035352.387423-2-saeed@kernel.org> (raw)
In-Reply-To: <20240208035352.387423-1-saeed@kernel.org>
From: Tariq Toukan <tariqt@nvidia.com>
Add a cap bit in mcam_access_reg to check for MPIR support.
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Reviewed-by: Gal Pressman <gal@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
---
include/linux/mlx5/mlx5_ifc.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h
index c726f90ab752..8bc35f221ee9 100644
--- a/include/linux/mlx5/mlx5_ifc.h
+++ b/include/linux/mlx5/mlx5_ifc.h
@@ -10253,7 +10253,9 @@ struct mlx5_ifc_mcam_access_reg_bits {
u8 mcqi[0x1];
u8 mcqs[0x1];
- u8 regs_95_to_87[0x9];
+ u8 regs_95_to_90[0x6];
+ u8 mpir[0x1];
+ u8 regs_88_to_87[0x2];
u8 mpegc[0x1];
u8 mtutc[0x1];
u8 regs_84_to_68[0x11];
--
2.43.0
next prev parent reply other threads:[~2024-02-08 3:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:53 [pull request][net-next V2 00/15] mlx5 socket direct Saeed Mahameed
2024-02-08 3:53 ` Saeed Mahameed [this message]
2024-02-08 3:53 ` [net-next V2 02/15] net/mlx5: SD, Introduce SD lib Saeed Mahameed
2024-02-08 3:53 ` [net-next v2 03/15] net/mlx5: SD, Implement basic query and instantiation Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 04/15] net/mlx5: SD, Implement devcom communication and primary election Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 05/15] net/mlx5: SD, Implement steering for primary and secondaries Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 06/15] net/mlx5: SD, Add informative prints in kernel log Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 07/15] net/mlx5: SD, Add debugfs Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 08/15] net/mlx5e: Create single netdev per SD group Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 09/15] net/mlx5e: Create EN core HW resources for all secondary devices Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 10/15] net/mlx5e: Let channels be SD-aware Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 11/15] net/mlx5e: Support cross-vhca RSS Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 12/15] net/mlx5e: Support per-mdev queue counter Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 13/15] net/mlx5e: Block TLS device offload on combined SD netdev Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 14/15] net/mlx5: Enable SD feature Saeed Mahameed
2024-02-08 3:53 ` [net-next V2 15/15] Documentation: net/mlx5: Add description for Socket-Direct netdev combining Saeed Mahameed
2024-02-10 6:27 ` Jakub Kicinski
2024-02-13 1:11 ` Samudrala, Sridhar
2024-02-10 5:54 ` [pull request][net-next V2 00/15] mlx5 socket direct Jakub Kicinski
2024-02-10 5:54 ` Jakub Kicinski
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=20240208035352.387423-2-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).