tc400: Fix expected turbo response to 'unready_turbo' #929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changed the expected response of the turbo in the
unready_turbodriver call.Motivation and Context
When the turbo receives the
unready_turbocommand it response with aPFEIFFER_FALSE(000000) and not aPFEIFFER_TRUE(111111). We assumed it would respond the opposite, so our check of if the function succeeded always incorrectly returned a failed state. We fixed this for theturn_turbo_offcommand but forgot this call.How Has This Been Tested?
This specifically was not tested but the
turn_turbo_offfix was tested. Indeed when I looked at the agent logs I see that the "setting ready state failed` now instead of the turn off failure.Types of changes
Checklist: