From: Larysa Zaremba <larysa.zaremba@intel.com>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"Tantilov, Emil S" <emil.s.tantilov@intel.com>,
"Chittim, Madhu" <madhu.chittim@intel.com>,
"Hay, Joshua A" <joshua.a.hay@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"Shanmugam, Jayaprakash" <jayaprakash.shanmugam@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Richard Cochran <richardcochran@gmail.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Salin, Samuel" <samuel.salin@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v7 07/14] idpf: refactor idpf to use libie_pci APIs
Date: Tue, 28 Apr 2026 16:14:50 +0200 [thread overview]
Message-ID: <afDA2slh1tx_7jvb@soc-5CG4396X81.clients.intel.com> (raw)
In-Reply-To: <IA3PR11MB898658952B56FC5666A64EE2E5372@IA3PR11MB8986.namprd11.prod.outlook.com>
On Tue, Apr 28, 2026 at 10:47:29AM +0200, Loktionov, Aleksandr wrote:
>
>
> > -----Original Message-----
> > From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf
> > Of Larysa Zaremba
> > Sent: Tuesday, April 28, 2026 10:27 AM
> > To: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L
> > <anthony.l.nguyen@intel.com>
> > Cc: Lobakin, Aleksander <aleksander.lobakin@intel.com>; Samudrala,
> > Sridhar <sridhar.samudrala@intel.com>; Michal Swiatkowski
> > <michal.swiatkowski@linux.intel.com>; Zaremba, Larysa
> > <larysa.zaremba@intel.com>; Fijalkowski, Maciej
> > <maciej.fijalkowski@intel.com>; Tantilov, Emil S
> > <emil.s.tantilov@intel.com>; Chittim, Madhu <madhu.chittim@intel.com>;
> > Hay, Joshua A <joshua.a.hay@intel.com>; Keller, Jacob E
> > <jacob.e.keller@intel.com>; Shanmugam, Jayaprakash
> > <jayaprakash.shanmugam@intel.com>; Jiri Pirko <jiri@resnulli.us>;
> > David S. Miller <davem@davemloft.net>; Eric Dumazet
> > <edumazet@google.com>; Jakub Kicinski <kuba@kernel.org>; Paolo Abeni
> > <pabeni@redhat.com>; Simon Horman <horms@kernel.org>; Jonathan Corbet
> > <corbet@lwn.net>; Richard Cochran <richardcochran@gmail.com>; Kitszel,
> > Przemyslaw <przemyslaw.kitszel@intel.com>; Andrew Lunn
> > <andrew+netdev@lunn.ch>; netdev@vger.kernel.org; linux-
> > doc@vger.kernel.org; linux-kernel@vger.kernel.org; Salin, Samuel
> > <samuel.salin@intel.com>
> > Subject: [Intel-wired-lan] [PATCH iwl-next v7 07/14] idpf: refactor
> > idpf to use libie_pci APIs
> >
> > From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> >
> > Use libie_pci init and MMIO APIs where possible, struct idpf_hw cannot
> > be deleted for now as it also houses control queues that will be
> > refactored later. Use libie_cp header for libie_ctlq_ctx that contains
> > mmio info from the start in order to not increase the diff later.
> >
> > Reviewed-by: Madhu Chittim <madhu.chittim@intel.com>
> > Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> > Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> > Co-developed-by: Larysa Zaremba <larysa.zaremba@intel.com>
> > Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
> > Tested-by: Samuel Salin <Samuel.salin@intel.com>
> > Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> > ---
> > drivers/net/ethernet/intel/idpf/Kconfig | 1 +
> > drivers/net/ethernet/intel/idpf/idpf.h | 70 +-------
> > .../net/ethernet/intel/idpf/idpf_controlq.c | 26 ++-
> > .../net/ethernet/intel/idpf/idpf_controlq.h | 2 -
> > drivers/net/ethernet/intel/idpf/idpf_dev.c | 61 ++++---
> > drivers/net/ethernet/intel/idpf/idpf_idc.c | 38 ++--
> > drivers/net/ethernet/intel/idpf/idpf_lib.c | 7 +-
> > drivers/net/ethernet/intel/idpf/idpf_main.c | 114 ++++++------
> > drivers/net/ethernet/intel/idpf/idpf_vf_dev.c | 57 +++---
> > .../net/ethernet/intel/idpf/idpf_virtchnl.c | 169 +++++++++--------
> > -
> > .../ethernet/intel/idpf/idpf_virtchnl_ptp.c | 58 +++---
> > 11 files changed, 288 insertions(+), 315 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/intel/idpf/Kconfig
> > b/drivers/net/ethernet/intel/idpf/Kconfig
> > index adab2154125b..586df3a4afe9 100644
> > --- a/drivers/net/ethernet/intel/idpf/Kconfig
> > +++ b/drivers/net/ethernet/intel/idpf/Kconfig
> > @@ -6,6 +6,7 @@ config IDPF
> > depends on PCI_MSI
> > depends on PTP_1588_CLOCK_OPTIONAL
> > select DIMLIB
> > + select LIBIE_CP
> > select LIBETH_XDP
> > help
> > This driver supports Intel(R) Infrastructure Data Path
> > Function diff --git a/drivers/net/ethernet/intel/idpf/idpf.h
> > b/drivers/net/ethernet/intel/idpf/idpf.h
> > index 0d08f51be7e3..efdb58990a8b 100644
> > --- a/drivers/net/ethernet/intel/idpf/idpf.h
> > +++ b/drivers/net/ethernet/intel/idpf/idpf.h
> > @@ -23,6 +23,7 @@ struct idpf_rss_data;
> >
> > #include <linux/intel/iidc_rdma.h>
> > #include <linux/intel/iidc_rdma_idpf.h>
> > +#include <linux/intel/libie/controlq.h>
> > #include <linux/intel/virtchnl2.h>
> >
> > #include "idpf_txrx.h"
> > @@ -625,6 +626,7 @@ struct idpf_vc_xn_manager;
> > * @flags: See enum idpf_flags
> > * @reset_reg: See struct idpf_reset_reg
> > * @hw: Device access data
>
> ...
>
> > for (i = 0; i < num_vecs; i++) {
> > struct idpf_q_vector *q_vector = &rsrc->q_vectors[i];
> > u16 vec_id = rsrc->q_vector_idxs[i] - IDPF_MBX_Q_VEC;
> > struct idpf_intr_reg *intr = &q_vector->intr_reg;
> > + struct idpf_vec_regs *reg = ®_vals[vec_id];
> > u32 spacing;
> >
> > - intr->dyn_ctl = idpf_get_reg_addr(adapter,
> > -
> > reg_vals[vec_id].dyn_ctl_reg);
> > + intr->dyn_ctl = libie_pci_get_mmio_addr(mmio,
> > + reg->dyn_ctl_reg);
> Stray TAB after =
Seems so.
>
> > intr->dyn_ctl_intena_m = PF_GLINT_DYN_CTL_INTENA_M;
> > intr->dyn_ctl_intena_msk_m =
> > PF_GLINT_DYN_CTL_INTENA_MSK_M;
> > intr->dyn_ctl_itridx_s = PF_GLINT_DYN_CTL_ITR_INDX_S; @@
>
> ...
>
> >
> > return 0;
> > }
> > --
> > 2.47.0
>
next prev parent reply other threads:[~2026-04-28 14:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:26 [PATCH iwl-next v7 00/14] Introduce iXD driver Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2026-04-28 10:08 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 02/14] libie: add PCI device initialization helpers to libie Larysa Zaremba
2026-04-28 10:09 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 03/14] libeth: allow to create fill queues without NAPI Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 04/14] libie: add control queue support Larysa Zaremba
2026-04-28 10:10 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 05/14] libie: add bookkeeping support for control queue messages Larysa Zaremba
2026-04-28 10:10 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 06/14] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2026-04-28 10:10 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 07/14] idpf: refactor idpf to use libie_pci APIs Larysa Zaremba
2026-04-28 8:47 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:14 ` Larysa Zaremba [this message]
2026-04-28 9:00 ` Loktionov, Aleksandr
2026-04-28 14:16 ` Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 08/14] idpf: refactor idpf to use libie control queues Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 09/14] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2026-04-28 10:11 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 10/14] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 11/14] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2026-04-28 10:11 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 8:26 ` [PATCH iwl-next v7 12/14] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 13/14] ixd: add the core initialization Larysa Zaremba
2026-04-28 8:50 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:12 ` Larysa Zaremba
2026-04-28 8:26 ` [PATCH iwl-next v7 14/14] ixd: add devlink support Larysa Zaremba
2026-04-28 8:53 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-04-28 14:13 ` Larysa Zaremba
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=afDA2slh1tx_7jvb@soc-5CG4396X81.clients.intel.com \
--to=larysa.zaremba@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jayaprakash.shanmugam@intel.com \
--cc=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=madhu.chittim@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=samuel.salin@intel.com \
--cc=sridhar.samudrala@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