bnxt_en: Add VF load path and PF/VF context differentiation
Needs ReviewPublic
Actions

Authored by chandrakanth.patil_broadcom.com on Tue, Mar 31, 6:11 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sat, Apr 18, 7:01 AM

	Unknown Object (File)
	Sat, Apr 18, 7:00 AM

	Unknown Object (File)
	Sat, Apr 18, 5:43 AM

	Unknown Object (File)
	Wed, Apr 15, 6:07 PM

	Unknown Object (File)
	Thu, Apr 9, 5:55 PM

	Unknown Object (File)
	Sun, Apr 5, 11:13 PM

	Unknown Object (File)
	Sun, Apr 5, 12:56 PM

	Unknown Object (File)
	Sun, Apr 5, 5:34 AM

View All 12 Files

Subscribers

None

Details

Reviewers

sumit.saxena_broadcom.com
sreekanth.reddy_broadcom.com
shurd

Summary

Enable the driver to distinguish a Physical Function from a Virtual
Function at probe time and configure each appropriately.
Add VF device IDs for all NetXtreme-C/E generations including Thor1/2
and Hyper-V variants. Refactor the iflib shared context initialisation
so PF and VF instances are selected dynamically at registration time.
Update the firmware capability and configuration query paths to populate
PF and VF specific state separately. Ensure the VF requests PF approval
for its firmware-assigned MAC address during attach and refreshes it on
each bring-up.