f5cc2eb42f
Current driver creates a join hw-fence from a fence-array, adds its waiting client to it, and then it decides if signal the hw-fence depending in the current state of all the child hw-fences from the fence array. However, if by any reason the fence-array gets all its children cleared within it (which can happen for spec-fences failures), hw-fence driver logic won't signal the new created join-fence. This can lead to the creation of an empty or incomplete join-fence that the waiting-client will be waiting-for, but won't be signaled. Add a check to make sure that if above scenario is ever presented, the register for wait API catches this issue and fails to register for wait in this invalid fence. Change-Id: If3c69405d2a3adfefd12f447257c2560b839d238 Signed-off-by: Ingrid Gallardo <quic_ingridg@quicinc.com>