@@ -101,9 +101,6 @@ class ProController : public AbstractController{
101101public:
102102 // Basic Commands
103103
104- // Required Feature Flags:
105- // - NintendoSwitch_Basic
106-
107104 //
108105 // All commands are enqueued into a FIFO that the controller will execute
109106 // in order preserving the timing semantics as closely as possible
@@ -169,23 +166,20 @@ class ProController : public AbstractController{
169166public:
170167 // Superscalar Commands (the "ssf" framework)
171168
172- // Required Feature Flags:
173- // - NintendoSwitch_SSF
174-
175169 // Tell the scheduler to wait for all pending commands to finish
176170 // (including cooldowns) before executing further instructions.
177171 // This is used to prevent hanging commands from overlapping with new
178172 // commands issued after this barrier.
179173 virtual void issue_barrier (const Cancellable* cancellable) = 0;
180174
181- // Do nothing for this many ticks .
175+ // Do nothing for this much time .
182176 virtual void issue_nop (const Cancellable* cancellable, Milliseconds duration) = 0;
183177
184178 //
185- // delay The # of ticks to wait before moving onto the next command.
186- // hold The # of ticks to hold the button/stick down for.
179+ // delay Time to wait before moving onto the next command.
180+ // hold Time to hold the button/stick down for.
187181 // cooldown After the button has been released, prevent it from being
188- // used again for this many ticks .
182+ // used again for this much time .
189183 //
190184 // For "normal" use, you should always set (delay == hold + cooldown).
191185 // This is the easiest case to understand and is what the "pbf" interface
@@ -239,13 +233,7 @@ class ProController : public AbstractController{
239233
240234
241235public:
242- // High speed RPCs.
243-
244- // Required Feature Flags:
245- // - NintendoSwitch_Macros
246- //
247- // Almost everything uses these. So it might be worth moving these to
248- // "NintendoSwitch_Basic" instead.
236+ // High speed Macros
249237
250238 //
251239 // It is currently unclear if these can be properly executed over wireless.
0 commit comments