0eef1069cb
The GPU VIPER TCC protocol accidentally used "TiggerMsg" instead of "TriggerMsg" for the triggerQueue_in port. This was a benign bug beacuse the msg type is not used in the in_port implementation but still makes the SLICC harder to understand, so fixing it is worthwhile. Change-Id: I88cbc72bac93bcc58a66f057a32f7bddf821cac9 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/44905 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Reviewed-by: Matthew Poremba <matthew.poremba@amd.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com>