Fix metric types for new experimental types

Fix order and values of experimental metrics types

Signed-off-by: Matias Cabral <[email protected]>

Author: matcabral

scripts/tools/EXT_Exp_MetricExportMemory.rst

@@ -78,7 +78,7 @@ The following pseudo-code demonstrates how to map memory exported by metrics:
        metricProperties.stype = ${T}_STRUCTURE_TYPE_METRIC_PROPERTIES;
        zetMetricGetProperties(hMetric, &metricProperties);
 
-       if(metricProperties.metricType == ZET_METRIC_TYPE_EXPORT_DMA_BUF){
+       if(metricProperties.metricType == ZET_METRIC_TYPE_EXP_EXPORT_DMA_BUF){
             zet_export_dma_buf_exp_properties_t dmaBufProperties;
             dmaBufProperties.stype = ${T}_STRUCTURE_TYPE_EXPORT_DMA_EXP_PROPERTIES;
             metricProperties.pNext = &dmaBufProperties;

scripts/tools/metric.yml

@@ -130,7 +130,7 @@ etors:
       desc: "Metric type: value of the event is a monotonically increasing value that can wrap around"
       version: "1.10"
       value: "0x7ffffffc"
-    - name: EXPORT_DMA_BUF_EXP
+    - name: EXP_EXPORT_DMA_BUF
       desc: "Metric which exports linux dma_buf, which could be imported/mapped to the host process"
       version: "1.11"
       value: "0x7ffffffd"