Change Details

This value is only used in a debug trace. However, the value is also modified to set a bit after being traced and that modified version is never used. Not clear if the modified version was supposed to be written to the register to trigger a reset and the register write is missing or if the |= is just dead code that should be thrown away and that reading from the register triggers the reset.

This variable was flagged as a set but unused warning as its value was read from a register and then modified to set a bit (TI_MBOX_SYSCONFIG_SOFTRST). After the variable is modified, the code then loops waiting for the SOFTRST bit to go clear in the TI_MBOX_SYSCONFIG register. Presumably merely reading from the register does not request a reset as other places in the driver read this register, so most likely the updated value of sysconfig setting the reset bit is supposed to be written to the register to request a reset before the polling loop that waits for the reset to finish.

This value is only used in a debug trace. However, theriable was flagged as a set but unused warning as its value is alsowas modified to set a bit after being tracedread from a register and thaten modified version isto set a bit never used(TI_MBOX_SYSCONFIG_SOFTRST). Not clear ifAfter the modified version was supposed to bevariable is modified, the code written to the register to trigger a reset and the register write isthen loops waiting for the SOFTRST bit to go clear in the missing or if the |= is just dead code that should be thrown away andTI_MBOX_SYSCONFIG register. Presumably merely reading from the that reading from the register triggers the resetregister does not request a reset as other places in the driver read this register, so most likely the updated value of sysconfig setting the reset bit is supposed to be written to the register to request a reset before the polling loop that waits for the reset to finish.