I am currently working on the development of a driver for cascaded 2243 hardware, for which we are utilizing the mmWaveLink library. In the process of debugging, I have encountered an issue pertaining to the monitor function of the 2243 chipset that I hope to obtain your guidance on.
We have observed that when the monitoring capabilities are activated on the 2243 device, it initiates the transmission of monitor asynchronous events to our driver at regular intervals. However, our driver, when not set up to receive these asynchronous events (due to 2243 interrupt being blocked in a manner that fails to address the 2243 asynchronous events), causes the 2243 to cease the data output after a certain duration.
This observation leads me to seek clarification on the following points:
- Is it mandatory for the upper-level driver to handle the 2243’s async events in real-time when the monitor function is enabled?
- Could the inability of the upper driver to process the interrupts induced by the 2243’s async events in a timely manner—owing to certain constraints—result in abnormal behavior of the 2243 chipset?
Thank you in advance for your support and assistance.
