Skip to main content
Header: spf/api/modules/nmt_module_calibration_api.h

Structures

nmt_version_t

Members
uint32_t
uint32_t

param_id_nmt_config_t

Members
uint32_t
uint32_t
}

param_id_nmt_output_config_t

Members
uint32_t
uint32_t
NON_BUFFERED - Output of each NMT algo process is immediately sent to client. BUFFERED - Output of each NMT algo process is buffered and sent to client intermittently.}
uint32_t
} // NMT engine controlled default if not configured

nmt_output_status_t

Members
uint32_t
uint32_t
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
uint8_t

nmt_input_status_t

Members
uint32_t
uint32_t
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
uint8_t

nmt_io_status_t

Members
uint32_t
uint32_t
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
}
uint32_t
uint8_t
uint32_t
uint8_t

param_id_nmt_output_t

Members
uint32_t
This can be used by clients to query the corresponding payload. If not configured or invalid, Payload corresponds to output buffers in sequential order as produced by NMT engine.Dummy token (0x7F7F7F7F) is reserved for FORCE_OUTPUT scenario where output buffer doesn’t have valid content but must raise event to client.}
uint32_t
uint32_t
Following this field is the payload of this size. Payload is variable array of type nmt_io_status_t . Size ‘0’ indicates this is an event generated without any valid input/output, for example : in response to a force output param set by client. }

param_id_nmt_force_output_t

Members
uint32_t

event_id_nmt_reg_cfg_t

@parameter @description @toolPolicy Members
uint32_t
INBAND - NMT event has the payload inband in the event. OPTIMAL - NMT event can be INBAND or QUERY based, flag in event payload indicates the mode.}
uint32_t
IN - event payload contains input text only. INOUT - event payload contains combined input and output text.}

event_id_nmt_event_t

Members
uint32_t
Default mode is Query. QUERY = Client will query via getparam upon receiving this event, using the output_token provided as part of this payload. Inband = NMT output payload follows inband after the payload_size field }
uint32_t
Default type is OUT. OUT - event payload contains output text only. IN - event payload contains input text only. INOUT - event payload contains combined input and output text.}
uint32_t
This can be used by clients to query the payload param in ‘QUERY’ mode. Dummy token (0x7F7F7F7F) is reserved for FORCE_OUTPUT scenario where output buffer doesn’t have valid content but must raise event to client.}
uint32_t
uint32_t
Following this field is the payload of this size. Payload is variable array of type nmt_io_status_t . Size ‘0’ indicates this is an event generated without any valid output, for example : in response to a force output param set by client. }

nmt_model_param_t

Members
uint32_t
uint32_t
uint32_t
uint8_t

Type Definitions

nmt_version_t

param_id_nmt_config_t

param_id_nmt_output_config_t

nmt_output_status_t

nmt_input_status_t

nmt_io_status_t

param_id_nmt_output_t

param_id_nmt_force_output_t

event_id_nmt_reg_cfg_t

event_id_nmt_event_t

nmt_model_param_t

NMT_LANGUAGE_CODE_t

nmt_output_mode_t

Enumerations

NMT_LANGUAGE_CODE_t

Values

nmt_output_mode_t

Values

Macros

NMT_NPU_RELEASE_VERSION_MAJOR

NMT_NPU_RELEASE_VERSION_MINOR

PARAM_ID_NMT_VERSION

PARAM_ID_NMT_CONFIG

PARAM_ID_NMT_OUTPUT_CONFIG

MAX_TRANSCRIPTION_CHAR_SIZE

PARAM_ID_NMT_OUTPUT

PARAM_ID_NMT_FORCE_OUTPUT

EVENT_ID_NMT_STATUS

PARAM_ID_NMT_MODEL

MODULE_ID_NMT