Lines Matching refs:callback

208 for two callback functions, create_buf_file() and remove_buf_file().
211 to represent the corresponding channel buffer.  The callback should
221  * create_buf_file() callback.  Creates relay file in debugfs.
234  * remove_buf_file() callback.  Removes relay file from debugfs.
256 If the create_buf_file() callback fails, or isn't defined, channel
312 of the subbuf_start() callback, as described below.  The default if no
313 subbuf_start() callback is defined is 'no-overwrite' mode.  If the
334 client is notified via the subbuf_start() callback that a switch to a
335 new sub-buffer is about to occur.  The client uses this callback to 1)
341 an implementation of the subbuf_start() callback something like the
361 the callback returns 0 to indicate that the buffer switch should not
367 buffer will again invoke the subbuf_start() callback with the same
372 The implementation of the subbuf_start() callback for 'overwrite' mode
389 callback always returns 1, causing the buffer switch to occur
395 define any callbacks, or doesn't define the subbuf_start() callback,
401 subbuf_start() callback.  This reserved area can be used to store
406 sub-buffer is passed into the subbuf_start() callback along with a
408 known until a sub-buffer is filled.  The subbuf_start() callback is
411 previous sub-buffer pointer passed into the callback will be NULL, so
429 callback by calling the relay_buf_full() helper function.