On Tue, Sep 02, 2025 at 08:58:52PM -0700, Pavan Kumar Linga wrote: > At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs > on our current generation hardware. Future hardware exposes a new set of > device IDs for each generation. To avoid adding a new device ID for each > generation and to make the driver forward and backward compatible, > make use of the IDPF PCI programming interface to load the driver. > > Write and read the VF_ARQBAL mailbox register to find if the current > device is a PF or a VF. > > PCI SIG allocated a new programming interface for the IDPF compliant > ethernet network controller devices. It can be found at: > https://members.pcisig.com/wg/PCI-SIG/document/20113 > with the document titled as 'PCI Code and ID Assignment Revision 1.16' > or any latest revisions. > > Tested this patch by doing a simple driver load/unload on Intel IPU E2000 > hardware which supports 0x1452 and 0x145C device IDs and new hardware > which supports the IDPF PCI programming interface. > > Reviewed-by: Sridhar Samudrala <[email protected]> > Signed-off-by: Madhu Chittim <[email protected]> > Reviewed-by: Simon Horman <[email protected]> > Signed-off-by: Pavan Kumar Linga <[email protected]>
Hi Pavan, Should this be targeted at iwl, where it applies cleanly, rather than net-next, where it does not. If the later, I think that a rebase and repost is appropriate. ...
