Hi Andrew and David, Thank you for your comments!
The client driver is still work in progress, but it can be seen here: https://source.codeaurora.org/quic/la/kernel/msm-4.19/tree/drivers/platform/msm/ipa/ipa_api.c#n3842 For HW performance reasons, it has to be in subsys_initcall. Here is the register_netdev call: https://source.codeaurora.org/quic/la/kernel/msm-4.19/tree/drivers/platform/msm/ipa/ipa_v3/rmnet_ipa.c#n2497 And it is going to be in the subsys_initcall as well. Thanks, Ilia On Mon, Jul 27, 2020 at 8:32 PM David Miller <da...@davemloft.net> wrote: > > From: Andrew Lunn <and...@lunn.ch> > Date: Sun, 26 Jul 2020 21:45:28 +0200 > > > I also have to wonder why a network device driver is being probed the > > subsys_initcall. > > This makes me wonder how this interface could even be useful. The > only way to fix the problem is to change when the device is probed, > which would mean changing which initcall it uses. So at run time, > this information can't do much.