From 77098f87367824b0e0c99b9f9deb6b977ab876c4 Mon Sep 17 00:00:00 2001 From: Xiang Xiao Date: Mon, 12 Nov 2018 06:36:26 -0600 Subject: [PATCH] Move NETDEV_LATEINIT from drivers/net/Kconfig to net/Kconfig so that we can select NETDEV_LATEINIT without enabling NETDEVICES since the net driver in arch folder may need to initialize later too. --- drivers/net/Kconfig | 29 ----------------------------- net/Kconfig | 29 +++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+), 29 deletions(-) diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index 6104dfd605..59faf9e681 100644 --- a/drivers/net/Kconfig +++ b/drivers/net/Kconfig @@ -62,35 +62,6 @@ config NETDEV_STATISTICS Enable to collect statistics from the network drivers (if supported by the network driver). -config NETDEV_LATEINIT - bool "Late driver initialization" - default n - ---help--- - Normally, networking initialization occur in the later phase of the - boot process in the function up_initialize() when it calls the - driver initialization function, up_netintialize(). This - initialization occurs after a sufficient about of the OS has been - initialized so that driver registration can be performed, but - before the completion of OS initialization and before the first - application is started. - - In a few situations, however, you may want to suppress this early - network driver initialization. As examples: - - - If you are using SLIP or PPPD, then there will be no network - driver to be initialized, - - Certain multi-network configurations where a simple call to - up_netinitialize() may be insufficient, and - - Situations where there are other board-level hardware - dependencies so that the hardware is not in an appropriate - state for up_netinitialize() to be called. - - Examples of this latter situation includes such things as network - drivers that required some setup via an I2C I/O expander, or network - drivers that depend on USB, SPI, I2C, PCI, serial, or other - interfaces that may not be ready when up_netiniailize() is normally - called. - config NET_DUMPPACKET bool "Enable packet dumping" depends on DEBUG_FEATURES diff --git a/net/Kconfig b/net/Kconfig index 79ea7d9bb7..e5b800e06b 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -231,6 +231,35 @@ config NET_USRSOCK can access standard socket API, with socket descriptors that can be used with NuttX system calls. +config NETDEV_LATEINIT + bool "Late driver initialization" + default n + ---help--- + Normally, networking initialization occur in the later phase of the + boot process in the function up_initialize() when it calls the + driver initialization function, up_netintialize(). This + initialization occurs after a sufficient about of the OS has been + initialized so that driver registration can be performed, but + before the completion of OS initialization and before the first + application is started. + + In a few situations, however, you may want to suppress this early + network driver initialization. As examples: + + - If you are using SLIP or PPPD, then there will be no network + driver to be initialized, + - Certain multi-network configurations where a simple call to + up_netinitialize() may be insufficient, and + - Situations where there are other board-level hardware + dependencies so that the hardware is not in an appropriate + state for up_netinitialize() to be called. + + Examples of this latter situation includes such things as network + drivers that required some setup via an I2C I/O expander, or network + drivers that depend on USB, SPI, I2C, PCI, serial, or other + interfaces that may not be ready when up_netiniailize() is normally + called. + endmenu # Link layer support source "net/netdev/Kconfig"