Lines Matching refs:subbuf_start

184     subbuf_start(buf, subbuf, prev_subbuf, prev_padding)
309 of the subbuf_start() callback, as described below.  The default if no
310 subbuf_start() callback is defined is 'no-overwrite' mode.  If the
331 client is notified via the subbuf_start() callback that a switch to a
338 an implementation of the subbuf_start() callback something like the
341     static int subbuf_start(struct rchan_buf *buf,
364 buffer will again invoke the subbuf_start() callback with the same
369 The implementation of the subbuf_start() callback for 'overwrite' mode
372     static int subbuf_start(struct rchan_buf *buf,
391 The default subbuf_start() implementation, used if the client doesn't
392 define any callbacks, or doesn't define the subbuf_start() callback,
398 subbuf_start() callback.  This reserved area can be used to store
402 subbuf_start() implementation; the padding value for the previous
403 sub-buffer is passed into the subbuf_start() callback along with a
405 known until a sub-buffer is filled.  The subbuf_start() callback is
425 which case you can detect a failed write in the subbuf_start()