Please allow me to rephrase my concerns back in 3months ago:
To prevent tester to execute graphic job that is generated for performance mode on power-saving mode, vice versa.
On hybrid graphics system, will generate job like this: 1_FirstGraphic_1st_job, 2_SecondGraphic_1st_job, in a linear ordering, and only being distinguish by a switch_card job, so if anything happen then messed up graphic mode settings, it would be a nice to have a way to help tester avoid testing on wrong graphic chip.
Please allow me to rephrase my concerns back in 3months ago:
To prevent tester to execute graphic job that is generated for performance mode on power-saving mode, vice versa.
On hybrid graphics system, will generate job like this: 1_FirstGraphic_ 1st_job, 2_SecondGraphic _1st_job, in a linear ordering, and only being distinguish by a switch_card job, so if anything happen then messed up graphic mode settings, it would be a nice to have a way to help tester avoid testing on wrong graphic chip.