CFRA: handle potential Msg3
Since the parent commit, CFRA is inconditionally marked complete on Msg3 reception (successful or not). This works because the current implementation still sends a UL grant (see parent commit for details). In this commit, handle Msg3 if received in CFRA (notably for TA and power). Note that since we declare RA complete, UE->ra does not exist anymore, and so an intermediate variable is introduced to capture the CFRA flag. The code should be such that if we are in CFRA, we never access any UE->ra variable.
Showing
Please register or sign in to comment