Fri, Jun 29, 2018 at 04:19:05AM CEST, da...@davemloft.net wrote: >From: Carlos Munoz <cmu...@cavium.com> >Date: Thu, 28 Jun 2018 14:20:05 -0700 > >> >> >> On 06/28/2018 01:41 AM, Andrew Lunn wrote: >>> External Email >>> >>>> +static char *mix_port; >>>> +module_param(mix_port, charp, 0444); >>>> +MODULE_PARM_DESC(mix_port, "Specifies which ports connect to MIX >>>> interfaces."); >>>> + >>>> +static char *pki_port; >>>> +module_param(pki_port, charp, 0444); >>>> +MODULE_PARM_DESC(pki_port, "Specifies which ports connect to the PKI."); >>> Module parameters are generally not liked. Can you do without them? >> >> These parameters change the kernel port assignment required by user >> space applications. We rather keep them as they simplify the >> process. > >This is actually a terrible user experience. > >Please provide a way to do this by performing operations on a device object >after the driver loads. > >Use something like devlink or similar if you have to.
Devlink params should be used for this. They are not upstream yet. We will push it most likely early next week.
