Andrew F. Davis 71a3527313 ti: k3: drivers: ti_sci: Retry message receive on bad sequence ID ... When we get a sequence ID that does not match what we expect then the we are looking at is not the one we are expecting and so we error out. We can also assume this message is a stale message left in the queue, in this case we can read in the next message and check again for our message. Switch to doing that here. We only retry a set number of times so we don't lock the system if our message is actually lost and will never show up. Signed-off-by: Andrew F. Davis <afd@ti.com> Change-Id: I6c8186ccc45e646d3ba9d431f7d4c451dcd70c5c		2019-04-23 11:09:13 -04:00
..
sec_proxy	ti: k3: drivers: sec_proxy: Use direction definitions	2019-04-23 11:09:13 -04:00
ti_sci	ti: k3: drivers: ti_sci: Retry message receive on bad sequence ID	2019-04-23 11:09:13 -04:00