DPDK patches and discussions
 help / color / mirror / Atom feed
From: Venkatesh Vemula <venkatesh.vemula@intel.com>
To: dev@dpdk.org, aman.deep.singh@intel.com, shaiq.wani@intel.com,
	david.marchand@redhat.com, bruce.richardson@intel.com
Subject: [PATCH v7 0/2] net/intel: add IDPF PCI class ID support
Date: Tue, 14 Oct 2025 15:50:54 +0530	[thread overview]
Message-ID: <20251014102056.459175-1-venkatesh.vemula@intel.com> (raw)
In-Reply-To: <20250919145125.113028-1-venkatesh.vemula@intel.com>

 Current IDPF supports only the MEV device IDs. MMG has new set of
 device IDs and same might be the case for the future devices. Instead
 of adding new device IDs every time, make use of the IDPF PCI class
 ID(0x20001) to differentiate between PF and VF.

 Write and read the VF_ARQBAL register to find if the current device is
 a PF or a VF.
 ---
 v2:
 *Renamed macro RTE_PCI_CLASS name to IDPF_PCI_CLASS.
 *Renamed macro IDPF_DEV_ID_CPF to CPFL_DEV_ID_MMG and
  CPFL_DEV_ID_MEV

 v3:
 *Moved cls_id variable in idpf_hw struct to avoid more struct padding.
 *Simplified and moved this check "(hw->device_id == IDPF_DEV_ID_SRIOV)"
  to idpf_is_vf_device function also switch case is removed. returns
  true for VF device and false for PF.
 *Simplified the IDPF_CLASS_NETWORK_ETHERNET_PROGIF macro
  logic with detailed fields "PCI_SUB_BASE_CLASS_NETWORK_ETHERNET"
  and PCI_BASE_CLASS_NETWORK_ETHERNET.

 v4:
  *Fixed code styling errors.
  *Removed cls_id variable in the idpf_hw structure no longer needed.

 v5:
  *Fixed merge conflicts.

 v6:
  *Added name in .mailmap file.
  *changed the sign off name format in commit message.
    
 v7:
  *Split into two patches one of idpf and one of cpfl, as both are
   independent
  *Rebased next-net-intel-for-next-net branch and fixed merge conflict
   and compilation error.
  *Changed macro name IDPF_DEV_ID_CPF to CPFL_DEV_ID_MEV in cpfl code.

Venkatesh Vemula (2):
  net/idpf: add IDPF PCI class ID support
  net/cpfl: added CPFL devID for MMG

 .mailmap                                    |  1 +
 drivers/net/intel/cpfl/cpfl_ethdev.c        | 13 +++++++------
 drivers/net/intel/cpfl/cpfl_ethdev.h        |  5 +++--
 drivers/net/intel/idpf/idpf_common_device.c | 20 ++++++++++++++++++--
 drivers/net/intel/idpf/idpf_common_device.h | 18 ++++++++++++++++++
 drivers/net/intel/idpf/idpf_ethdev.c        |  1 +
 6 files changed, 48 insertions(+), 10 deletions(-)

-- 
2.34.1


  parent reply	other threads:[~2025-10-15  8:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 14:51 [PATCH v1] net/idpf: " Vemula Venkatesh
2025-09-22  8:31 ` Wani, Shaiq
2025-09-22 12:09 ` David Marchand
2025-09-22 16:35   ` Singh, Aman Deep
2025-09-23  6:52     ` David Marchand
2025-09-24 12:57 ` [PATCH v2] net/intel: " Vemula Venkatesh
2025-09-24 14:34   ` Bruce Richardson
2025-09-25 10:28     ` Vemula, Venkatesh
2025-09-25 17:47   ` [PATCH v3] " Vemula Venkatesh
2025-09-26 15:26     ` Singh, Aman Deep
2025-09-29 14:00 ` [PATCH v4] " Vemula Venkatesh
2025-10-01 15:30 ` [PATCH v5] " Vemula Venkatesh
2025-10-06 18:12 ` [PATCH v6] " Venkatesh Vemula
2025-10-09 16:10   ` Bruce Richardson
2025-10-14 10:20 ` Venkatesh Vemula [this message]
2025-10-14 10:20   ` [PATCH v7 1/2] net/idpf: " Venkatesh Vemula
2025-10-14 10:20   ` [PATCH v7 2/2] net/cpfl: added CPFL devID for MMG Venkatesh Vemula
2025-10-14 10:44 ` [PATCH v7 0/2] net/intel: add IDPF PCI class ID support Venkatesh Vemula
2025-10-14 10:45 ` Venkatesh Vemula
2025-10-14 10:45   ` [PATCH v7 1/2] net/idpf: " Venkatesh Vemula
2025-10-14 12:47     ` Bruce Richardson
2025-10-14 13:24       ` Bruce Richardson
2025-10-14 10:45   ` [PATCH v7 2/2] net/cpfl: added CPFL devID for MMG Venkatesh Vemula
2025-10-14 12:48     ` Bruce Richardson
2025-10-14 13:34       ` Vemula, Venkatesh

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=20251014102056.459175-1-venkatesh.vemula@intel.com \
    --to=venkatesh.vemula@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=shaiq.wani@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).