linux-toradex.git/include/linux/net, branch master

libie: add bookkeeping support for control queue messages

2026-08-12T20:56:51+00:00

Small send control queue message buffers are managed and reused by
libie itself, bigger send buffers are consumed. All are tracked with
the unique transaction (Xn) ids until they receive response or time out.

Responses can be received out of order, therefore transactions are stored
in an array and tracked though a bitmap. Rx buffers utilize page_pool.

Pre-allocated DMA memory is used where possible. It reduces the driver
overhead in handling memory allocation/free and message timeouts.

Reviewed-by: Maciej Fijalkowski 
Signed-off-by: Phani R Burra 
Co-developed-by: Victor Raj 
Signed-off-by: Victor Raj 
Co-developed-by: Pavan Kumar Linga 
Signed-off-by: Pavan Kumar Linga 
Tested-by: Bharath R 
Tested-by: Samuel Salin 
Co-developed-by: Larysa Zaremba 
Signed-off-by: Larysa Zaremba 
Signed-off-by: Tony Nguyen

libie: add control queue support

2026-08-12T20:56:51+00:00

Libie will now support control queue setup and configuration APIs. These
are mainly used for mailbox communication between drivers and control
plane.

Make use of the libeth_rx page pool support for managing controlq buffers.

Reviewed-by: Maciej Fijalkowski 
Signed-off-by: Phani R Burra 
Co-developed-by: Victor Raj 
Signed-off-by: Victor Raj 
Co-developed-by: Sridhar Samudrala 
Signed-off-by: Sridhar Samudrala 
Co-developed-by: Pavan Kumar Linga 
Signed-off-by: Pavan Kumar Linga 
Tested-by: Samuel Salin 
Tested-by: Bharath R 
Co-developed-by: Larysa Zaremba 
Signed-off-by: Larysa Zaremba 
Signed-off-by: Tony Nguyen

libie: add PCI device initialization helpers to libie

2026-08-12T20:56:50+00:00

idpf and ixd drivers serve different PCI functions on the same device,
therefore their PCI configuration flow is very similar.

Add support functions for idpf and ixd to configure PCI functionality and
access MMIO space. Add a mapping list which can be traversed by a driver,
e.g. to pass certain I/O mappings to the auxbus devices. Such list is also
traversed by the libie_pci_get_mmio_addr() helper, which allows for easier
memory access.

Reviewed-by: Maciej Fijalkowski 
Signed-off-by: Phani R Burra 
Co-developed-by: Victor Raj 
Signed-off-by: Victor Raj 
Co-developed-by: Sridhar Samudrala 
Signed-off-by: Sridhar Samudrala 
Co-developed-by: Pavan Kumar Linga 
Signed-off-by: Pavan Kumar Linga 
Tested-by: Bharath R 
Tested-by: Samuel Salin 
Co-developed-by: Larysa Zaremba 
Signed-off-by: Larysa Zaremba 
Signed-off-by: Tony Nguyen

virtchnl: move virtchnl and virtchnl2 headers to 'include/linux/net/intel'

2026-08-12T20:56:50+00:00

virtchnl2 headers will be used by both idpf and ixd drivers, so they have
to be moved to an include directory. On top of that, it would be useful to
place all iavf headers together with other intel networking headers.

Move abovementioned intel header files into 'include/linux/net/intel'.

While at it, remove the self-include from iavf_types.h.

Suggested-by: Alexander Lobakin 
Reviewed-by: Sridhar Samudrala 
Signed-off-by: Victor Raj 
Tested-by: Samuel Salin 
Signed-off-by: Larysa Zaremba 
Signed-off-by: Tony Nguyen

ixgbe: E610: add discovering EEE capability

2026-05-03T02:12:36+00:00

Add detecting and parsing EEE device capability.

Recently EEE functionality support has been introduced to E610 FW.
Currently ixgbe driver has no possibility to detect whether NVM
loaded on given adapter supports EEE.

There's dedicated device capability element reflecting FW support
for given EEE link speed.

Reviewed-by: Aleksandr Loktionov 
Signed-off-by: Jedrzej Jagielski 
Tested-by: Rinitha S 
Signed-off-by: Jacob Keller 
Link: https://patch.msgid.link/20260430-jk-iwl-net-next-2026-04-30-v1-1-6f27ae1cd073@intel.com
Signed-off-by: Jakub Kicinski

libie: depend on DEBUG_FS when building LIBIE_FWLOG

2025-11-06T01:38:03+00:00

LIBIE_FWLOG is unusable without DEBUG_FS. Mark it in Kconfig.

Fix build error on ixgbe when DEBUG_FS is not set. To not add another
layer of #if IS_ENABLED(LIBIE_FWLOG) in ixgbe fwlog code define debugfs
dentry even when DEBUG_FS isn't enabled. In this case the dummy
functions of LIBIE_FWLOG will be used, so not initialized dentry isn't a
problem.

Fixes: 641585bc978e ("ixgbe: fwlog support for e610")
Reported-by: Guenter Roeck 
Closes: https://lore.kernel.org/lkml/f594c621-f9e1-49f2-af31-23fbcb176058@roeck-us.net/
Signed-off-by: Michal Swiatkowski 
Reviewed-by: Simon Horman 
Reviewed-by: Aleksandr Loktionov 
Tested-by: Rinitha S  (A Contingent worker at Intel)
Signed-off-by: Tony Nguyen 
Link: https://patch.msgid.link/20251104172333.752445-1-anthony.l.nguyen@intel.com
Signed-off-by: Jakub Kicinski

ice, libie: move fwlog code to libie

2025-09-11T19:10:47+00:00

Move whole code from ice_fwlog.c/h to libie/fwlog.c/h.

Reviewed-by: Przemek Kitszel 
Signed-off-by: Michal Swiatkowski 
Tested-by: Rinitha S  (A Contingent worker at Intel)
Reviewed-by: Simon Horman 
Signed-off-by: Tony Nguyen

ice: prepare for moving file to libie

2025-09-11T19:10:34+00:00

s/ice/libie

There is no function for filling default descriptor in libie. Zero
descriptor structure and set opcode without calling the function.

Make functions that are caled only in ice_fwlog.c static.

Reviewed-by: Przemek Kitszel 
Signed-off-by: Michal Swiatkowski 
Tested-by: Rinitha S  (A Contingent worker at Intel)
Reviewed-by: Simon Horman 
Signed-off-by: Tony Nguyen

libie, ice: move fwlog admin queue to libie

2025-09-11T19:10:25+00:00

Copy the code and:
- change ICE_AQC to LIBIE_AQC
- change ice_aqc to libie_aqc
- move definitions outside the structures

Reviewed-by: Przemek Kitszel 
Signed-off-by: Michal Swiatkowski 
Tested-by: Rinitha S  (A Contingent worker at Intel)
Reviewed-by: Simon Horman 
Signed-off-by: Tony Nguyen

ice: Implement support for SRIOV VFs across Active/Active bonds

2025-08-14T22:50:47+00:00

This patch implements the software flows to handle SRIOV VF
communication across an Active/Active link aggregate.  The same
restrictions apply as are in place for the support of Active/Backup
bonds.

- the two interfaces must be on the same NIC
- the FW LLDP engine needs to be disabled
- the DDP package that supports VF LAG must be loaded on device
- the two interfaces must have the same QoS config
- only the first interface added to the bond will have VF support
- the interface with VFs must be in switchdev mode

With the additional requirement of
- the version of the FW on the NIC needs to have VF Active/Active support
This requirement is indicated in the capabilities struct associated
with the NVM loaded on the NIC.

The balancing of traffic between the two interfaces is done on a queue
basis.  Taking the queues allocated to all of the VFs as a whole, one
half of them will be distributed to each interface.  When a link goes
down, then the queues allocated to the down interface will migrate to
the active port.  When the down port comes back up, then the same
queues as were originally assigned there will be moved back.

Co-developed-by: Marcin Szycik 
Signed-off-by: Marcin Szycik 
Signed-off-by: Dave Ertman 
Tested-by: Sujai Buvaneswaran 
Signed-off-by: Tony Nguyen