Removing MUTEX Use

Removing Mutex use in not allowed driver areas. Code cleanup.

Author: AmeNote-Michael

src/api/Drivers/USBMIDI2/Driver/StreamEngine.cpp

@@ -298,7 +298,7 @@ Return Value:
 
     // Current mechanism to determine if currently processing data is that
     // the StreamEngine is not null. TBD this mechanism needs to be fixed.
-    auto lock = m_MidiInLock.acquire();
+    //auto lock = m_MidiInLock.acquire();
 
     if (m_IsRunning)
     {
@@ -579,7 +579,7 @@ StreamEngine::Run()
     {
         // m_IsRunning is used to indicate running state. If m_IsRunning true, the out worker
         // thread will output data to the connected device, otherwise data will be thrown away.
-        auto lock = m_MidiInLock.acquire();
+        //auto lock = m_MidiInLock.acquire();
 
         WDFDEVICE devCtx = AcxCircuitGetWdfDevice(AcxPinGetCircuit(m_Pin));
         PDEVICE_CONTEXT pDevCtx = GetDeviceContext(devCtx);

src/api/Drivers/USBMIDI2/Driver/StreamEngine.h

@@ -235,9 +235,7 @@ class StreamEngine
     wil::kernel_event_auto_reset   m_ThreadExitEvent;
     wil::kernel_event_manual_reset m_ThreadExitedEvent {true};
 
-    // m_StandardStreamingLock m_LoopbackMessageQueue are only used
     // for standard streaming of loopback messages
-    wil::fast_mutex_with_critical_region m_StandardStreamingLock;
     wil::fast_mutex_with_critical_region m_MidiInLock;
     LIST_ENTRY  m_LoopbackMessageQueue {nullptr};
 };