net: Fix misc Kconfig style issues in networking area

rlubos · kartben · commit faa507ef6c92 · 2025-08-21T20:12:48.000+02:00
Fix misc Kconfig style issues in networking area.

Signed-off-by: Robert Lubos &lt;robert.lubos@nordicsemi.no&gt;
diff --git a/subsys/mgmt/osdp/Kconfig b/subsys/mgmt/osdp/Kconfig
@@ -18,14 +18,17 @@ if OSDP
 
 choice
 	prompt "OSDP Mode of Operation"
-	config OSDP_MODE_PD
-		bool "Configure OSDP in Peripheral Device mode"
-		help
-		  Configure this device to operate as a PD (Peripheral Device)
-	config OSDP_MODE_CP
-		bool "Configure OSDP in Control Panel mode"
-		help
-		  Configure this device to operate as a CP (Control Panel)
+
+config OSDP_MODE_PD
+	bool "Configure OSDP in Peripheral Device mode"
+	help
+	  Configure this device to operate as a PD (Peripheral Device)
+
+config OSDP_MODE_CP
+	bool "Configure OSDP in Control Panel mode"
+	help
+	  Configure this device to operate as a CP (Control Panel)
+
 endchoice
 
 config OSDP_UART_BAUD_RATE
diff --git a/subsys/net/l2/ethernet/gptp/Kconfig b/subsys/net/l2/ethernet/gptp/Kconfig
@@ -41,44 +41,63 @@ choice
 	  the actual capabilities of the hardware.
 	  See 7.6.2.5 of IEEE 1588-2008 for more info.
 
-	config NET_GPTP_CLOCK_ACCURACY_UNKNOWN
-		bool "Unknown"
-	config NET_GPTP_CLOCK_ACCURACY_25NS
-		bool "25ns"
-	config NET_GPTP_CLOCK_ACCURACY_100NS
-		bool "100ns"
-	config NET_GPTP_CLOCK_ACCURACY_250NS
-		bool "250ns"
-	config NET_GPTP_CLOCK_ACCURACY_1US
-		bool "1us"
-	config NET_GPTP_CLOCK_ACCURACY_2_5US
-		bool "2.5us"
-	config NET_GPTP_CLOCK_ACCURACY_10US
-		bool "10us"
-	config NET_GPTP_CLOCK_ACCURACY_25US
-		bool "25us"
-	config NET_GPTP_CLOCK_ACCURACY_100US
-		bool "100us"
-	config NET_GPTP_CLOCK_ACCURACY_250US
-		bool "250us"
-	config NET_GPTP_CLOCK_ACCURACY_1MS
-		bool "1ms"
-	config NET_GPTP_CLOCK_ACCURACY_2_5MS
-		bool "1.5ms"
-	config NET_GPTP_CLOCK_ACCURACY_10MS
-		bool "10ms"
-	config NET_GPTP_CLOCK_ACCURACY_25MS
-		bool "25ms"
-	config NET_GPTP_CLOCK_ACCURACY_100MS
-		bool "100ms"
-	config NET_GPTP_CLOCK_ACCURACY_250MS
-		bool "250ms"
-	config NET_GPTP_CLOCK_ACCURACY_1S
-		bool "1s"
-	config NET_GPTP_CLOCK_ACCURACY_10S
-		bool "10s"
-	config NET_GPTP_CLOCK_ACCURACY_GT_10S
-		bool "> 10s"
+config NET_GPTP_CLOCK_ACCURACY_UNKNOWN
+	bool "Unknown"
+
+config NET_GPTP_CLOCK_ACCURACY_25NS
+	bool "25ns"
+
+config NET_GPTP_CLOCK_ACCURACY_100NS
+	bool "100ns"
+
+config NET_GPTP_CLOCK_ACCURACY_250NS
+	bool "250ns"
+
+config NET_GPTP_CLOCK_ACCURACY_1US
+	bool "1us"
+
+config NET_GPTP_CLOCK_ACCURACY_2_5US
+	bool "2.5us"
+
+config NET_GPTP_CLOCK_ACCURACY_10US
+	bool "10us"
+
+config NET_GPTP_CLOCK_ACCURACY_25US
+	bool "25us"
+
+config NET_GPTP_CLOCK_ACCURACY_100US
+	bool "100us"
+
+config NET_GPTP_CLOCK_ACCURACY_250US
+	bool "250us"
+
+config NET_GPTP_CLOCK_ACCURACY_1MS
+	bool "1ms"
+
+config NET_GPTP_CLOCK_ACCURACY_2_5MS
+	bool "1.5ms"
+
+config NET_GPTP_CLOCK_ACCURACY_10MS
+	bool "10ms"
+
+config NET_GPTP_CLOCK_ACCURACY_25MS
+	bool "25ms"
+
+config NET_GPTP_CLOCK_ACCURACY_100MS
+	bool "100ms"
+
+config NET_GPTP_CLOCK_ACCURACY_250MS
+	bool "250ms"
+
+config NET_GPTP_CLOCK_ACCURACY_1S
+	bool "1s"
+
+config NET_GPTP_CLOCK_ACCURACY_10S
+	bool "10s"
+
+config NET_GPTP_CLOCK_ACCURACY_GT_10S
+	bool "> 10s"
+
 endchoice
 
 config NET_GPTP_CLOCK_ACCURACY
diff --git a/subsys/net/lib/config/Kconfig b/subsys/net/lib/config/Kconfig
@@ -24,8 +24,7 @@ if NET_CONFIG_SETTINGS
 
 config NET_CONFIG_AUTO_INIT
 	bool "Init networking support automatically during device startup"
-	default n if USB_DEVICE_NETWORK || USBD_CDC_ECM_CLASS || USBD_CDC_NCM_CLASS
-	default y
+	default y if !(USB_DEVICE_NETWORK || USBD_CDC_ECM_CLASS || USBD_CDC_NCM_CLASS)
 	help
 	  If this option is set, then the networking system is automatically
 	  initialized when the device is started. If you do not wish to do
diff --git a/subsys/net/lib/lwm2m/Kconfig b/subsys/net/lib/lwm2m/Kconfig
@@ -143,7 +143,7 @@ config LWM2M_ENGINE_ALWAYS_REPORT_OBJ_VERSION
 	  always report all object versions.
 
 choice
-prompt "Socket handling at idle state"
+	prompt "Socket handling at idle state"
 
 config LWM2M_RD_CLIENT_CLOSE_SOCKET_AT_IDLE
 	bool "Close socket when entering RX idle"
diff --git a/subsys/net/lib/mqtt_sn/Kconfig b/subsys/net/lib/mqtt_sn/Kconfig
@@ -41,9 +41,9 @@ config MQTT_SN_LIB_MAX_ADDR_SIZE
 	default 21
 	range 1 $(UINT8_MAX)
 	help
-		The MQTT_SN library stores addresses internally and thus
-		needs to know how long your addresses are. Set this to the maximum
-		length in bytes of the address data structure for your implemented transport.
+	  The MQTT_SN library stores addresses internally and thus
+	  needs to know how long your addresses are. Set this to the maximum
+	  length in bytes of the address data structure for your implemented transport.
 
 config MQTT_SN_LIB_BROADCAST_RADIUS
 	int "Radius for broadcast messages"
diff --git a/subsys/net/lib/ptp/Kconfig b/subsys/net/lib/ptp/Kconfig
@@ -55,17 +55,18 @@ choice
 	help
 	  Specifies type of PTP Clock implemented on the target device
 
-	config PTP_ORDINARY_CLOCK
-		bool "Ordinary Clock"
+config PTP_ORDINARY_CLOCK
+	bool "Ordinary Clock"
 
-	config PTP_BOUNDARY_CLOCK
-		bool "Boundary Clock"
+config PTP_BOUNDARY_CLOCK
+	bool "Boundary Clock"
 
-	config PTP_TRANSPARENT_P2P_CLOCK
-		bool "Transparent Peer-to-Peer Clock"
+config PTP_TRANSPARENT_P2P_CLOCK
+	bool "Transparent Peer-to-Peer Clock"
+
+config PTP_TRANSPARENT_E2E_CLOCK
+	bool "Transparent End-to-End Clock"
 
-	config PTP_TRANSPARENT_E2E_CLOCK
-		bool "Transparent End-to-End Clock"
 endchoice
 
 config PTP_CLOCK_TYPE
@@ -89,15 +90,16 @@ choice
 	prompt "PTP Networking Protocol used by PTP Stack"
 	default PTP_UDP_IPv4_PROTOCOL
 
-	config PTP_UDP_IPv4_PROTOCOL
-		bool "UDP with IPv4"
-		depends on NET_IPV4
-		select NET_IPV4_IGMP
+config PTP_UDP_IPv4_PROTOCOL
+	bool "UDP with IPv4"
+	depends on NET_IPV4
+	select NET_IPV4_IGMP
+
+config PTP_UDP_IPv6_PROTOCOL
+	bool "UDP with IPv6"
+	depends on NET_IPV6
+	select NET_IPV6_MLD
 
-	config PTP_UDP_IPv6_PROTOCOL
-		bool "UDP with IPv6"
-		depends on NET_IPV6
-		select NET_IPV6_MLD
 endchoice
 
 choice
@@ -108,44 +110,63 @@ choice
 	  the actual capabilities of the hardware.
 	  See 7.6.2.5 of IEEE 1588-2019 for more info.
 
-	config PTP_CLOCK_ACCURACY_UNKNOWN
-		bool "Unknown"
-	config PTP_CLOCK_ACCURACY_25NS
-		bool "25ns"
-	config PTP_CLOCK_ACCURACY_100NS
-		bool "100ns"
-	config PTP_CLOCK_ACCURACY_250NS
-		bool "250ns"
-	config PTP_CLOCK_ACCURACY_1US
-		bool "1us"
-	config PTP_CLOCK_ACCURACY_2_5US
-		bool "2.5us"
-	config PTP_CLOCK_ACCURACY_10US
-		bool "10us"
-	config PTP_CLOCK_ACCURACY_25US
-		bool "25us"
-	config PTP_CLOCK_ACCURACY_100US
-		bool "100us"
-	config PTP_CLOCK_ACCURACY_250US
-		bool "250us"
-	config PTP_CLOCK_ACCURACY_1MS
-		bool "1ms"
-	config PTP_CLOCK_ACCURACY_2_5MS
-		bool "1.5ms"
-	config PTP_CLOCK_ACCURACY_10MS
-		bool "10ms"
-	config PTP_CLOCK_ACCURACY_25MS
-		bool "25ms"
-	config PTP_CLOCK_ACCURACY_100MS
-		bool "100ms"
-	config PTP_CLOCK_ACCURACY_250MS
-		bool "250ms"
-	config PTP_CLOCK_ACCURACY_1S
-		bool "1s"
-	config PTP_CLOCK_ACCURACY_10S
-		bool "10s"
-	config PTP_CLOCK_ACCURACY_GT_10S
-		bool "> 10s"
+config PTP_CLOCK_ACCURACY_UNKNOWN
+	bool "Unknown"
+
+config PTP_CLOCK_ACCURACY_25NS
+	bool "25ns"
+
+config PTP_CLOCK_ACCURACY_100NS
+	bool "100ns"
+
+config PTP_CLOCK_ACCURACY_250NS
+	bool "250ns"
+
+config PTP_CLOCK_ACCURACY_1US
+	bool "1us"
+
+config PTP_CLOCK_ACCURACY_2_5US
+	bool "2.5us"
+
+config PTP_CLOCK_ACCURACY_10US
+	bool "10us"
+
+config PTP_CLOCK_ACCURACY_25US
+	bool "25us"
+
+config PTP_CLOCK_ACCURACY_100US
+	bool "100us"
+
+config PTP_CLOCK_ACCURACY_250US
+	bool "250us"
+
+config PTP_CLOCK_ACCURACY_1MS
+	bool "1ms"
+
+config PTP_CLOCK_ACCURACY_2_5MS
+	bool "1.5ms"
+
+config PTP_CLOCK_ACCURACY_10MS
+	bool "10ms"
+
+config PTP_CLOCK_ACCURACY_25MS
+	bool "25ms"
+
+config PTP_CLOCK_ACCURACY_100MS
+	bool "100ms"
+
+config PTP_CLOCK_ACCURACY_250MS
+	bool "250ms"
+
+config PTP_CLOCK_ACCURACY_1S
+	bool "1s"
+
+config PTP_CLOCK_ACCURACY_10S
+	bool "10s"
+
+config PTP_CLOCK_ACCURACY_GT_10S
+	bool "> 10s"
+
 endchoice
 
 config PTP_CLOCK_ACCURACY
@@ -248,7 +269,6 @@ config PTP_PRE_TIME_TRANSMITTER_PRESENT
 
 config PTP_UNCALIBRATED_PRESENT
 	bool
-	default n
 
 config PTP_FOREIGN_TIME_TRANSMITTER_FEATURE
 	bool
@@ -268,14 +288,15 @@ choice PTP_DSCP_PRIORITY
 	prompt "Priority of PTP packets classification"
 	default PTP_DSCP_NONE_PRIORITY
 
-	config PTP_DSCP_HIGH_PRIORITY
-		bool "High priority of PTP packet classification"
+config PTP_DSCP_HIGH_PRIORITY
+	bool "High priority of PTP packet classification"
+
+config PTP_DSCP_MEDIUM_PRIORITY
+	bool "Medium priority of PTP packet classification"
 
-	config PTP_DSCP_MEDIUM_PRIORITY
-		bool "Medium priority of PTP packet classification"
+config PTP_DSCP_NONE_PRIORITY
+	bool "Default priority of PTP packet classification"
 
-	config PTP_DSCP_NONE_PRIORITY
-		bool "Default priority of PTP packet classification"
 endchoice
 
 config PTP_DSCP_VALUE
diff --git a/subsys/net/lib/sockets/Kconfig b/subsys/net/lib/sockets/Kconfig
@@ -236,12 +236,12 @@ config NET_SOCKETS_TLS_MAX_APP_PROTOCOLS
 	  By default, no supported application layer protocol is set.
 
 config NET_SOCKETS_TLS_MAX_CLIENT_SESSION_COUNT
-	  int "Maximum number of stored client TLS/DTLS sessions"
-	  default 1
-	  depends on NET_SOCKETS_SOCKOPT_TLS
-	  help
-	    This variable specifies maximum number of stored TLS/DTLS sessions,
-	    used for TLS/DTLS session resumption.
+	int "Maximum number of stored client TLS/DTLS sessions"
+	default 1
+	depends on NET_SOCKETS_SOCKOPT_TLS
+	help
+	  This variable specifies maximum number of stored TLS/DTLS sessions,
+	  used for TLS/DTLS session resumption.
 
 config NET_SOCKETS_TLS_CERT_VERIFY_CALLBACK
 	bool "TLS certificate verification callback support"
