mgmt: mcumgr: Disable legacy Kconfigs if legacy mode is disabled
It does not make sense to control configuration of legacy
options if legacy mode is diabled.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
diff --git a/subsys/mgmt/mcumgr/Kconfig b/subsys/mgmt/mcumgr/Kconfig
index cdf292b..0aa02b0 100644
--- a/subsys/mgmt/mcumgr/Kconfig
+++ b/subsys/mgmt/mcumgr/Kconfig
@@ -22,6 +22,7 @@
config MCUMGR_SMP_LEGACY_RC_BEHAVIOUR
bool "Legacy rc (result code) response behaviour"
+ depends on MCUMGR_SMP_SUPPORT_ORIGINAL_PROTOCOL
help
This will enable legacy result code response behaviour of having rc
present in responses when the status is 0. With this option disabled,
diff --git a/subsys/mgmt/mcumgr/smp/Kconfig b/subsys/mgmt/mcumgr/smp/Kconfig
index 69f745a..3bd70b7 100644
--- a/subsys/mgmt/mcumgr/smp/Kconfig
+++ b/subsys/mgmt/mcumgr/smp/Kconfig
@@ -81,16 +81,6 @@
This will enable SMP command status notification hooks for when an SMP message is
received or processed.
-config MCUMGR_SMP_VERBOSE_ERR_RESPONSE
- bool "Support verbose error response"
- help
- Support for encoding "rc" code explanation in form of "rsn"
- text string. This is useful, when returning MGMT_ERR_EUNKNOWN,
- to add additional information on the source of an error.
- Note that the "rsn" is string additional to "rc" code,
- so MCUMGR_TRANSPORT_NETBUF_SIZE should be large enough to be able
- to encode both.
-
config MCUMGR_SMP_SUPPORT_ORIGINAL_PROTOCOL
bool "Support original protocol"
default y
@@ -100,3 +90,14 @@
whereby there is a dedicated entry for command error/result codes.
The protocol selection is indicated by the request header sent by the
client.
+
+config MCUMGR_SMP_VERBOSE_ERR_RESPONSE
+ bool "Support verbose error response"
+ depends on MCUMGR_SMP_SUPPORT_ORIGINAL_PROTOCOL
+ help
+ Support for encoding "rc" code explanation in form of "rsn"
+ text string. This is useful, when returning MGMT_ERR_EUNKNOWN,
+ to add additional information on the source of an error.
+ Note that the "rsn" is string additional to "rc" code,
+ so MCUMGR_TRANSPORT_NETBUF_SIZE should be large enough to be able
+ to encode both.
