Lines Matching refs:RCS
37 Engine ids: DEFAULT, RCS, BCS, VCS, VCS1, VCS2, VECS
43 1.RCS.500-1000.-1.0
44 1.RCS.3700.0.0
45 1.RCS.1000.-2.0
47 1.RCS.4700.-1.0
55 2-4. Now three batches are sent to RCS with durations of 0.5-1.5ms (random
60 RCS batch.
61 6. This is followed by a 4.7ms RCS batch with a data dependency on the 2.3ms
63 7. Then a 0.6ms VCS2 batch is sent depending on the previous RCS one. In the
77 1.RCS.3700.0.0
99 1.RCS.500-1000.-1/f-1.0
106 1.RCS.500-1000.0.0
110 VCS1 and VCS2 batches will have a sync fence dependency on the RCS batch.
114 1.RCS.500-1000.0.0
118 1.RCS.500-1000.0.1
125 runnable. When the second RCS batch completes the standalone fence is signaled
139 1.RCS.500-1000.0.0
143 Here VCS1 and VCS2 batches will only be submitted for executing once the RCS
150 1.RCS.1000.0.0
166 1.RCS.1000.0.0
168 1.RCS.1000.0.0
229 M.1.RCS|VECS
233 b.2.VCS1.RCS
236 This tells the driver that if it picked RCS for context one, it has to pick VCS1
247 that valid engine pairs are either RCS + VCS1 (for two contexts respectively),
263 1.RCS.1000.0.0
265 2.RCS.1000.0.0