> From: David Ahern <dsahern@xxxxxxxxx> > Sent: Monday, December 7, 2020 8:19 AM > > On 11/12/20 12:24 PM, Parav Pandit wrote: > > diff --git a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > > b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > > index 485478979b1a..10dfaf671c90 100644 > > --- a/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > > +++ b/drivers/net/ethernet/mellanox/mlx5/core/Kconfig > > @@ -202,3 +202,12 @@ config MLX5_SW_STEERING > > default y > > help > > Build support for software-managed steering in the NIC. > > + > > +config MLX5_SF > > + bool "Mellanox Technologies subfunction device support using auxiliary > device" > > + depends on MLX5_CORE && MLX5_CORE_EN > > + default n > > + help > > + Build support for subfuction device in the NIC. A Mellanox subfunction > > + device can support RDMA, netdevice and vdpa device. > > + It is similar to a SRIOV VF but it doesn't require SRIOV support. > > per Dan's comment about AUXILIARY_BUS being select only, should this config > select AUXILIARY_BUS? Yes. However, my patchset depends on patchset [1]. With introduction of patchset [2], MLX5_CORE depends on AUXILIARY_BUS. MLX5_SF depends on MLX5_CORE. So I omitted explicitly selecting AUXBUS by MLX5_SF. [1] https://lore.kernel.org/linux-rdma/20201204182952.72263-1-saeedm@xxxxxxxxxx/ [2] https://lore.kernel.org/alsa-devel/20201026111849.1035786-6-leon@xxxxxxxxxx/
