Apply restyled

Author: adabreuti

docs/guides/ti/matter-migration-guide/matter_cc2674_migration.md

@@ -50,9 +50,9 @@ The GPIO pin values for SPI will need to be adjusted based on your design.
 4. Select _Board_ as _None_ and _Device_ as _`CC2674P10RGZ`_, Unselect
    _`Lock PinMux`_, and click _Confirm_.
 5. To fix errors, make the following module changes:
-    - _RF Design_ and _RF Stacks -> Bluetooth LE -> Radio_: click on _accepting the
-      current value_, which should be _`LP_CC2674P10_RGZ`_ in the drop down menu
-      for _Based On RF Design_
+    - _RF Design_ and _RF Stacks -> Bluetooth LE -> Radio_: click on _accepting
+      the current value_, which should be _`LP_CC2674P10_RGZ`_ in the drop down
+      menu for _Based On RF Design_
     - _TI DEVICES -> Device Configuration_: Clear
       _`XOSC Cap Array Modification`_
     - _TI DRIVERS -> RF_: Set _Global Event Mask_ as _None_ and _No. of Antenna

docs/guides/ti/matter-users-guide/ti_factory_data_user_guide.md

@@ -50,8 +50,8 @@ Each element is described in more detail below:
 ## How to use
 
 Out of box factory data location is configured to be on second to last page of
-flash. For CC13x4_CC26x4, the starting address is `0xFE800`. This can be configured in
-the linker file.
+flash. For CC13x4_CC26x4, the starting address is `0xFE800`. This can be
+configured in the linker file.
 
 To configure:
 

docs/guides/ti/matter-users-guide/ti_matter_overview.md

@@ -107,7 +107,7 @@ as reference for your own application.
 -   [pump-app](../../../../examples/pump-app/cc13x4_26x4/README.md)
 -   [pump-controller-app](../../../../examples/pump-controller-app/cc13x4_26x4/README.md)
 -   [lighting-app](../../../../examples/lighting-app/cc13x4_26x4/README.md)
-<hr>
+    <hr>
 
 ### Build system
 

docs/guides/ti/matter-users-guide/ti_openthread_library_usage.md

@@ -2,13 +2,19 @@
 
 ## Overview
 
-TI Matter example applications provide configuration options for how Thread code is included in the build. Thread code can be included in as:
+TI Matter example applications provide configuration options for how Thread code
+is included in the build. Thread code can be included in as:
 
-  1. Thread certified library optimized for Matter (recommended for development and production)
-  2. Full Source (can be used for development)
-  3. Custom option where customers can update the Thread config file to change the included OpenThread feature set
+1. Thread certified library optimized for Matter (recommended for development
+   and production)
+2. Full Source (can be used for development)
+3. Custom option where customers can update the Thread config file to change the
+   included OpenThread feature set
 
-The library builds have been optimized for Matter to disable features such as Thread Joiner capability in order to save on Flash/RAM usage. Refer to the `ti_matter_production_certification.md` to get the cert ID for your Matter certification application when using the certified Thread libraries from TI.
+The library builds have been optimized for Matter to disable features such as
+Thread Joiner capability in order to save on Flash/RAM usage. Refer to the
+`ti_matter_production_certification.md` to get the cert ID for your Matter
+certification application when using the certified Thread libraries from TI.
 
 Build arguments have been added to enable Matter applications to link against
 certified OpenThread FTD/MTD libraries or custom user libraries.
@@ -26,8 +32,8 @@ chip_openthread_ftd = true
 ```
 
 -   **TI Certified OpenThread Library**:
-    
-    * Typically this is used for development.
+
+    -   Typically this is used for development.
 
     1. `ot_ti_lib_dir` Is set to an empty string
 
@@ -66,7 +72,10 @@ chip_openthread_ftd = true
         ```
 
 -   **Custom OpenThread Library**:
-    * The custom OpenThread library is used to implement extra features, or when modifying the stack in anyway.
+
+    -   The custom OpenThread library is used to implement extra features, or
+        when modifying the stack in anyway.
+
     1.  `ot_ti_lib_dir` Points to a library directory containing a custom
         `libopenthread-ftd/mtd` variant
 

examples/all-clusters-app/cc13x4_26x4/main/AppTask.cpp

@@ -106,7 +106,7 @@ TimerHandle_t sOTAInitTimer = 0;
 
 // The OTA Init Timer is only started upon the first Thread State Change
 // detected if the device is already on a Thread Network, or during the AppTask
-// Init sequence if the device is not yet on a Thread Network. Once the timer 
+// Init sequence if the device is not yet on a Thread Network. Once the timer
 // has been started once, it does not need to be started again so the flag will
 // be set to false.
 bool isAppStarting = true;
@@ -157,13 +157,15 @@ void DeviceEventCallback(const ChipDeviceEvent * event, intptr_t arg)
         PLAT_LOG("Thread State Change");
         bool isThreadAttached = ThreadStackMgrImpl().IsThreadAttached();
 
-        if(isThreadAttached){
+        if (isThreadAttached)
+        {
             PLAT_LOG("Device is on the Thread Network");
 #if CHIP_DEVICE_CONFIG_ENABLE_OTA_REQUESTOR
-            if(isAppStarting){
+            if (isAppStarting)
+            {
                 StartTimer(OTAREQUESTOR_INIT_TIMER_DELAY_MS);
                 isAppStarting = false;
-            }   
+            }
 #endif
         }
         break;
@@ -174,7 +176,8 @@ void DeviceEventCallback(const ChipDeviceEvent * event, intptr_t arg)
 #endif
 }
 
-void OTAInitTimerEventHandler(TimerHandle_t xTimer){
+void OTAInitTimerEventHandler(TimerHandle_t xTimer)
+{
     InitializeOTARequestor();
 }
 
@@ -222,17 +225,17 @@ int AppTask::Init()
     }
 
     // Create FreeRTOS sw timer for OTA timer.
-    sOTAInitTimer = xTimerCreate("OTAInitTmr",                 // Just a text name, not used by the RTOS kernel
-                            OTAREQUESTOR_INIT_TIMER_DELAY_MS,  // timer period (mS)
-                            false,                             // no timer reload (==one-shot)
-                            (void *) this,                     // init timer id = light obj context
-                            OTAInitTimerEventHandler           // timer callback handler
+    sOTAInitTimer = xTimerCreate("OTAInitTmr",                     // Just a text name, not used by the RTOS kernel
+                                 OTAREQUESTOR_INIT_TIMER_DELAY_MS, // timer period (mS)
+                                 false,                            // no timer reload (==one-shot)
+                                 (void *) this,                    // init timer id = light obj context
+                                 OTAInitTimerEventHandler          // timer callback handler
     );
 
     if (sOTAInitTimer == NULL)
     {
         PLAT_LOG("sOTAInitTimer timer create failed");
-    } 
+    }
     else
     {
         PLAT_LOG("sOTAInitTimer timer created successfully ");
@@ -286,8 +289,8 @@ int AppTask::Init()
     PLAT_LOG("Initialize Server");
     static chip::CommonCaseDeviceServerInitParams initParams;
     static DefaultTestEventTriggerDelegate sTestEventTriggerDelegate{ ByteSpan(sTestEventTriggerEnableKey) };
-    initParams.testEventTriggerDelegate = &sTestEventTriggerDelegate; 
-    
+    initParams.testEventTriggerDelegate = &sTestEventTriggerDelegate;
+
     (void) initParams.InitializeStaticResourcesBeforeServerInit();
 
     // Initialize info provider
@@ -309,17 +312,17 @@ int AppTask::Init()
     // We only have network commissioning on endpoint 0.
     emberAfEndpointEnableDisable(kNetworkCommissioningEndpointSecondary, false);
 
-
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.
     PlatformMgr().AddEventHandler(DeviceEventCallback, reinterpret_cast<intptr_t>(nullptr));
 
     bool isThreadEnabled = ThreadStackMgrImpl().IsThreadEnabled();
-    if(!isThreadEnabled && isAppStarting){
+    if (!isThreadEnabled && isAppStarting)
+    {
 #if CHIP_DEVICE_CONFIG_ENABLE_OTA_REQUESTOR
-    PLAT_LOG("Thread is Disabled, enable OTA Requestor");
-    StartTimer(OTAREQUESTOR_INIT_TIMER_DELAY_MS);
-    isAppStarting = false;
+        PLAT_LOG("Thread is Disabled, enable OTA Requestor");
+        StartTimer(OTAREQUESTOR_INIT_TIMER_DELAY_MS);
+        isAppStarting = false;
 #endif
     }
     // QR code will be used with CHIP Tool
@@ -346,20 +349,20 @@ void AppTask::AppTaskMain(void * pvParameter)
 
 void StartTimer(uint32_t aTimeoutMs)
 {
-        PLAT_LOG("Start OTA Init Timer")
-        if (xTimerIsTimerActive(sOTAInitTimer))
-        {
-            PLAT_LOG("app timer already started!");
-            CancelTimer();
-        }
+    PLAT_LOG("Start OTA Init Timer")
+    if (xTimerIsTimerActive(sOTAInitTimer))
+    {
+        PLAT_LOG("app timer already started!");
+        CancelTimer();
+    }
 
-        // timer is not active, change its period to required value (== restart).
-        // FreeRTOS- Block for a maximum of 100 ticks if the change period command
-        // cannot immediately be sent to the timer command queue.
-        if (xTimerChangePeriod(sOTAInitTimer, pdMS_TO_TICKS(aTimeoutMs), 100) != pdPASS)
-        {
-            PLAT_LOG("sOTAInitTimer timer start() failed");
-        }  
+    // timer is not active, change its period to required value (== restart).
+    // FreeRTOS- Block for a maximum of 100 ticks if the change period command
+    // cannot immediately be sent to the timer command queue.
+    if (xTimerChangePeriod(sOTAInitTimer, pdMS_TO_TICKS(aTimeoutMs), 100) != pdPASS)
+    {
+        PLAT_LOG("sOTAInitTimer timer start() failed");
+    }
 }
 
 void CancelTimer(void)
@@ -370,7 +373,6 @@ void CancelTimer(void)
     }
 }
 
-
 void AppTask::PostEvent(const AppEvent * aEvent)
 {
     if (xQueueSend(sAppEventQueue, aEvent, 0) != pdPASS)