Lines Matching full:custom

1 Attaching External Custom Decoders    {#custom_decoders}
9 An external custom decoder is one which decodes a CoreSight trace byte stream from a source other
21 - `ocsd_extern_dcd_fact_t` : This is a decoder "factory" that allows the creation of the custom dec…
34 This registers the custom decoder with the library using the supplied name and factory structure.
35 As part of the registration function the custom decoder will be assigned a protocol ID which may be…
38 …ered, the standard API functions used with the built-in decoders will work with the custom decoder.
42 …he interface that is registered with the library to allow the creation of custom decoder instances.
58 Creating a Custom Decoder Instance
61 Once the custom decoder factory has been registered with the library then using the decoder uses th…
70 To create a custom decoder instance simply use the custom name and a pointer to the custom configur…
72 Calling this on a custom decoder name will result in a call to the factor function `fnCreateCustomD…
84 …itional information to allow the library to correctly call back into the custom decoder using the …
89 …e possible use these functions if being used as part of a combined ARM / custom decoder tree. This…
96 Finally the decoder creation function will interpret the custom configuration (`decoder_cfg`) and f…
105 The echo_test decoder is provided to both test the C-API interfaces provided for using custom decod…
109 In order to use a custom decoder, the header files for that decoder must be included by the client …
127 After this the test uses the same code path as the built in decoders when testing the custom decode…
128 …cd_tree_handle_t dcd_tree_h)` is called if the test parameters indicate a custom decoder is needed.
129 This populates the custom configuration structure specific to the echo_test decoder (`echo_dcd_cfg_…
136         /* setup the custom configuration */