> -----Original Message----- > From: Hillf Danton <hdanton@xxxxxxxx> > Sent: Tuesday, February 14, 2023 4:36 PM > > On Tue, 14 Feb 2023 06:25:35 +0000 Wentong Wu <wentong.wu@xxxxxxxxx> > > > > This allows new command(e.g. 'get status' command to check current > > firmware= > > status) to be downloaded to firmware for debugging purpose in case no > > resp= onse for current command though I have never saw this happen. > > =20 > > Thanks for your specification. > > Another question, is it likely for the wakeup to come after reinit because of for > instance timeout on the waiter side? Thanks, first I want to clarify why we have timeout here, in case firmware stuck somehow or IVSC device is removed suddenly, calling thread can't be wakeup if wait forever here. And firmware gets high priority to handle command and response, also there is timeout mechanism inside firmware, I think there will be some problem with firmware if driver gets command response after 5s which will be captured by driver code(if (csi->cmd_response.cmd_id != cmd->cmd_id)) but I have never saw this happen. BR, Wentong
