AlarmMgmtSWFaults.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixed

Fixed

Yes

Yes

REmoved

REmoved

Moved

Moved

Fixed

Fixed

Removed

Removed

Not a float.

Not a float.

Not a float.

Not a float.

Not a float anymore. Use u32Override function and no need to cast the pointer.

Not a float anymore. Use u32Override function and no need to cast the pointer.

Should we publish all registers read?

Should we publish all registers read?

Remove this comment since we have a comment to right.

Remove this comment since we have a comment to right.

Remove comment.

Remove comment.

REG_ADDRESSES

REG_ADDRESSES

DEVICE_ADDRESSES

DEVICE_ADDRESSES

Set them individually instead of with memset.

Set them individually instead of with memset.

Add blank line before a /// comment.

Add blank line before a /// comment.

device and register is fine. Or deviceSel and registerSel.

device and register is fine. Or deviceSel and registerSel.

Which alarm?

Which alarm?

bpPublishTimerCtr is the output?

bpPublishTimerCtr is the output?

Input is none. Add @Alarms

Input is none.
Add @Alarms

Should we list the alarm ids? @Alarms?

Should we list the alarm ids? @Alarms?

requestAbortBPReading is the output?

requestAbortBPReading is the output?

requestPedsBPReading is the output?

requestPedsBPReading is the output?

requestAdultBPReading is the output?

requestAdultBPReading is the output?

pendingVitalsRequest is the output?

pendingVitalsRequest is the output?

We should initialize in the init function?

We should initialize in the init function?

bpMeasurementReady is an output?

bpMeasurementReady is an output?

nextState is the return value. Should we add requestAdultBPMeasurement, bpMeasurementReady and bpDriverError to outputs?

nextState is the return value.
Should we add requestAdultBPMeasurement, bpMeasurementReady and bpDriverError to outputs?

Where are we updating the bpResults?

Where are we updating the bpResults?