Controllers

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-7395: Addressed code review comments

  1. … 1 more file in changeset.
Addressed.

Addressed.

Addressed.

Addressed.

This should be compare to SELF_TEST_STATUS_PASSED now.

This should be compare to SELF_TEST_STATUS_PASSED now.

Recommend adding _MS to the end to indicate the metric in milliseconds.

Recommend adding _MS to the end to indicate the metric in milliseconds.

DEN-7395: Addressed header needed change based on code review comment

Addressed.

Addressed.

DEN-7395: Addressed code review comments

  1. … 1 more file in changeset.
Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

No action item.

No action item.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

No action item.

No action item.

Addressed.

Addressed.

The clearAlarmCondition() function will check if the alarm is active or not and only clears if the alarm has been raised.

The clearAlarmCondition() function will check if the alarm is active or not and only clears if the alarm has been raised.

Typecasting the variables is not needed here. The macro typecasts them.

Typecasting the variables is not needed here. The macro typecasts them.

Should probably go to normal state on fail as well - otherwise you get stuck here in self-test state.

Should probably go to normal state on fail as well - otherwise you get stuck here in self-test state.

Can we clear this alarm when it is raised? If no, do we need this else statement? Because if the alarm has not been raised, we do not need to clear it either.

Can we clear this alarm when it is raised? If no, do we need this else statement? Because if the alarm has not been raised, we do not need to clear it either.

I think better to use self test status enum (mentioned in .h comment). This enum will have pass/fail/in progress. I think if we're still in INIT, zero, or self-test state, in-progress is appropriat...

I think better to use self test status enum (mentioned in .h comment). This enum will have pass/fail/in progress. I think if we're still in INIT, zero, or self-test state, in-progress is appropriate return value. I think you should have a BOOL variable defined to remember whether self-test passed or failed (instead of inferring from current state). Then if in normal state, return pass if self-test passed, failed if not.

Recommend typecasting bloodLeakState to (U32)bloodLeakState. Outside of this driver the enums are only U32s until they are converted to states again in Dialin.

Recommend typecasting bloodLeakState to (U32)bloodLeakState. Outside of this driver the enums are only U32s until they are converted to states again in Dialin.

Same comment as above re: timeout.

Same comment as above re: timeout.

Should AND this bit off from register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector). Should be something like fpgaActuatorSetPoints.fpgaSensor...

Should AND this bit off from register so we don't interfere with other bits that may have been set by other drivers (e.g. bubble detector).
Should be something like fpgaActuatorSetPoints.fpgaSensorTest &= ~FPGA_BLOOD_LEAK_SELF_TEST_CMD;