On Thu, Jun 4, 2020 at 11:56 PM Sudeep Holla <sudeep.holla@xxxxxxx> wrote: > > > >> bash-1526 [000] 1149.472553: scmi_xfer_begin: transfer_id=1538 msg_id=6 protocol_id=21 seq=0 poll=0 > > >> <idle>-0 [001] 1149.472733: scmi_xfer_begin: transfer_id=1539 msg_id=7 protocol_id=19 seq=1 poll=1 > > > > > Here another request is started before the first is finished. > > Ah, the prints are when the client requested. It is not when the mailbox > started it. So this just indicates the beginning of the transfer from the > client. > There maybe condition on a sensor read to finish within 1ms, but there is no condition for the read to _start_ at this very moment (usually there are sleeps in the path to sensor requests). > > If you want this to work you have to serialise access to the single > > physical channel and/or run the remote firmware in asynchronous mode - > > that is, the firmware ack the bit as soon as it sees and starts > > working in the background, so that we return in ~3usec always, while > > the data returns whenever it is ready. > > Yes it does that for few requests like DVFS while it uses synchronous > mode for few others. While ideally I agree everything in asynchronous > most is better, I don't know there may be reasons for such design. > The reason is that, if the firmware works asynchronously, every call would return in ~3usec and you won't think you need virtual channels. You have shared only 'bad' log without serialising access. Please share log after serialising access to the channel and the 'good' log with virtual channels. That should put the topic to rest. thanks.
