Correct Kconfigs according to the coding style

2019-01-25 17:10:53 +01:00
parent 7fb3218a33
commit 37126d3451
105 changed files with 7561 additions and 7535 deletions
--- a/examples/bluetooth/a2dp_gatts_coex/main/Kconfig.projbuild
+++ b/examples/bluetooth/a2dp_gatts_coex/main/Kconfig.projbuild
@@ -1,43 +1,42 @@
 menu "A2DP Example Configuration"

-choice A2DP_SINK_OUTPUT
-    prompt "A2DP Sink Output"
-    default A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        Select to use Internal DAC or external I2S driver
+    choice A2DP_SINK_OUTPUT
+        prompt "A2DP Sink Output"
+        default A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            Select to use Internal DAC or external I2S driver

-config A2DP_SINK_OUTPUT_INTERNAL_DAC
-    bool "Internal DAC"
-    help
-        Select this to use Internal DAC sink output
+        config A2DP_SINK_OUTPUT_INTERNAL_DAC
+            bool "Internal DAC"
+            help
+                Select this to use Internal DAC sink output

-config A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    bool "External I2S Codec"
-    help
-        Select this to use External I2S sink output
+        config A2DP_SINK_OUTPUT_EXTERNAL_I2S
+            bool "External I2S Codec"
+            help
+                Select this to use External I2S sink output

-endchoice
+    endchoice

-config I2S_LRCK_PIN
-    int "I2S LRCK (WS) GPIO"
-    default 22
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S LRCK(WS) Driver.
+    config I2S_LRCK_PIN
+        int "I2S LRCK (WS) GPIO"
+        default 22
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S LRCK(WS) Driver.

-config I2S_BCK_PIN
-    int "I2S BCK GPIO"
-    default 26
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S BCK Driver.
-
-config I2S_DATA_PIN
-    int "I2S DATA GPIO"
-    default 25
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S Data Driver.
+    config I2S_BCK_PIN
+        int "I2S BCK GPIO"
+        default 26
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S BCK Driver.

+    config I2S_DATA_PIN
+        int "I2S DATA GPIO"
+        default 25
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S Data Driver.

 endmenu
--- a/examples/bluetooth/a2dp_sink/main/Kconfig.projbuild
+++ b/examples/bluetooth/a2dp_sink/main/Kconfig.projbuild
@@ -1,43 +1,42 @@
 menu "A2DP Example Configuration"

-choice A2DP_SINK_OUTPUT
-    prompt "A2DP Sink Output"
-    default A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        Select to use Internal DAC or external I2S driver
+    choice A2DP_SINK_OUTPUT
+        prompt "A2DP Sink Output"
+        default A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            Select to use Internal DAC or external I2S driver

-config A2DP_SINK_OUTPUT_INTERNAL_DAC
-    bool "Internal DAC"
-    help
-        Select this to use Internal DAC sink output
+        config A2DP_SINK_OUTPUT_INTERNAL_DAC
+            bool "Internal DAC"
+            help
+                Select this to use Internal DAC sink output

-config A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    bool "External I2S Codec"
-    help
-        Select this to use External I2S sink output
+        config A2DP_SINK_OUTPUT_EXTERNAL_I2S
+            bool "External I2S Codec"
+            help
+                Select this to use External I2S sink output

-endchoice
+    endchoice

-config I2S_LRCK_PIN
-    int "I2S LRCK (WS) GPIO"
-    default 22
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S LRCK(WS) Driver.
+    config I2S_LRCK_PIN
+        int "I2S LRCK (WS) GPIO"
+        default 22
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S LRCK(WS) Driver.

-config I2S_BCK_PIN
-    int "I2S BCK GPIO"
-    default 26
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S BCK Driver.
-
-config I2S_DATA_PIN
-    int "I2S DATA GPIO"
-    default 25
-    depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
-    help
-        GPIO number to use for I2S Data Driver.
+    config I2S_BCK_PIN
+        int "I2S BCK GPIO"
+        default 26
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S BCK Driver.

+    config I2S_DATA_PIN
+        int "I2S DATA GPIO"
+        default 25
+        depends on A2DP_SINK_OUTPUT_EXTERNAL_I2S
+        help
+            GPIO number to use for I2S Data Driver.

 endmenu
--- a/examples/bluetooth/ble_ibeacon/main/Kconfig.projbuild
+++ b/examples/bluetooth/ble_ibeacon/main/Kconfig.projbuild
@@ -1,26 +1,26 @@
 menu "iBeacon Example Configuration"

-choice IBEACON_MODE
-    bool "iBeacon Mode"
-    default IBEACON_SENDER
-    help
-        Select the iBeacon Mode.
+    choice IBEACON_MODE
+        bool "iBeacon Mode"
+        default IBEACON_SENDER
+        help
+            Select the iBeacon Mode.

-config IBEACON_SENDER
-    bool "iBeacon Sender Mode"
-    help
-        Select the iBeacon Sender Mode.
+        config IBEACON_SENDER
+            bool "iBeacon Sender Mode"
+            help
+                Select the iBeacon Sender Mode.

-config IBEACON_RECEIVER
-    bool "iBeacon Receiver Mode"
-    help
-        Select the iBeacon Receiver Mode.
+        config IBEACON_RECEIVER
+            bool "iBeacon Receiver Mode"
+            help
+                Select the iBeacon Receiver Mode.

-endchoice
+    endchoice

-config IBEACON_MODE
-    int
-    default 0 if IBEACON_SENDER
-    default 1 if IBEACON_RECEIVER
+    config IBEACON_MODE
+        int
+        default 0 if IBEACON_SENDER
+        default 1 if IBEACON_RECEIVER

 endmenu
--- a/examples/bluetooth/ble_throughput/throughput_client/main/Kconfig
+++ b/examples/bluetooth/ble_throughput/throughput_client/main/Kconfig
@@ -1,14 +1,14 @@
 menu "Example 'GATT CLIENT THROUGHPUT' Config"

-config GATTS_NOTIFY_THROUGHPUT
-    bool "test the gatts notify throughput"
-	help
-        If this config item is set, then the 'GATTC_WRITE_THROUGHPUT' config should be close, it can't test both write or notify at the same time at this demo
+    config GATTS_NOTIFY_THROUGHPUT
+        bool "test the gatts notify throughput"
+        help
+            If this config item is set, then the 'GATTC_WRITE_THROUGHPUT' config should be close, it can't test both
+            write or notify at the same time at this demo

-config GATTC_WRITE_THROUGHPUT
-    bool "test the gattc write throughput"
-	help
-        If this config item is set, then the 'GATTS_NOTIFY_THROUGHPUT' config should be close, it can't test both write or notify at the same time at this demo
+    config GATTC_WRITE_THROUGHPUT
+        bool "test the gattc write throughput"
+        help
+            If this config item is set, then the 'GATTS_NOTIFY_THROUGHPUT' config should be close, it can't test both
+            write or notify at the same time at this demo
 endmenu
-
-
--- a/examples/bluetooth/ble_throughput/throughput_server/main/Kconfig
+++ b/examples/bluetooth/ble_throughput/throughput_server/main/Kconfig
@@ -1,23 +1,27 @@
 menu "Example 'GATT SERVER THROUGHPUT' Config"

-config SET_RAW_ADV_DATA
-    bool "Use raw data for advertising packets and scan response data"
-    help
-        If this config item is set, raw binary data will be used to generate advertising & scan response data.
-        This option uses the esp_ble_gap_config_adv_data_raw() and esp_ble_gap_config_scan_rsp_data_raw() functions.
+    config SET_RAW_ADV_DATA
+        bool "Use raw data for advertising packets and scan response data"
+        help
+            If this config item is set, raw binary data will be used to generate advertising & scan response data.
+            This option uses the esp_ble_gap_config_adv_data_raw() and esp_ble_gap_config_scan_rsp_data_raw()
+            functions.

-        If this config item is unset, advertising & scan response data is provided via a higher-level esp_ble_adv_data_t structure.
-        The lower layer will generate the BLE packets. This option has higher overhead at runtime.
-		
-config GATTS_NOTIFY_THROUGHPUT
-    bool "test the gatts notify throughput"
-	help
-        If this config item is set, then the 'GATTC_WRITE_THROUGHPUT' config should be close, it can't test both write or notify at the same time at this demo
+            If this config item is unset, advertising & scan response data is provided via a higher-level
+            esp_ble_adv_data_t structure. The lower layer will generate the BLE packets. This option has higher
+            overhead at runtime.

-config GATTC_WRITE_THROUGHPUT
-    bool "test the gattc write throughput"
-	help
-        If this config item is set, then the 'GATTS_NOTIFY_THROUGHPUT' config should be close, it can't test both write or notify at the same time at this demo
+    config GATTS_NOTIFY_THROUGHPUT
+        bool "test the gatts notify throughput"
+        help
+            If this config item is set, then the 'GATTC_WRITE_THROUGHPUT' config should be close, it can't test both
+            write or notify at the same time at this demo
+
+    config GATTC_WRITE_THROUGHPUT
+        bool "test the gattc write throughput"
+        help
+            If this config item is set, then the 'GATTS_NOTIFY_THROUGHPUT' config should be close, it can't test both
+            write or notify at the same time at this demo
 endmenu


--- a/examples/bluetooth/gatt_server/main/Kconfig
+++ b/examples/bluetooth/gatt_server/main/Kconfig
@@ -1,12 +1,14 @@
 menu "Example 'GATT SERVER' Config"

-config SET_RAW_ADV_DATA
-    bool "Use raw data for advertising packets and scan response data"
-    help
-        If this config item is set, raw binary data will be used to generate advertising & scan response data.
-        This option uses the esp_ble_gap_config_adv_data_raw() and esp_ble_gap_config_scan_rsp_data_raw() functions.
+    config SET_RAW_ADV_DATA
+        bool "Use raw data for advertising packets and scan response data"
+        help
+            If this config item is set, raw binary data will be used to generate advertising & scan response data.
+            This option uses the esp_ble_gap_config_adv_data_raw() and esp_ble_gap_config_scan_rsp_data_raw()
+            functions.

-        If this config item is unset, advertising & scan response data is provided via a higher-level esp_ble_adv_data_t structure.
-        The lower layer will generate the BLE packets. This option has higher overhead at runtime.
+            If this config item is unset, advertising & scan response data is provided via a higher-level
+            esp_ble_adv_data_t structure. The lower layer will generate the BLE packets. This option has higher
+            overhead at runtime.

 endmenu