summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2024-03-06 06:41:39 +0200
committerVille Syrjälä <ville.syrjala@linux.intel.com>2024-04-18 14:06:12 +0300
commit4ed2d06e6ec35328eebac920871cec51c99e36d9 (patch)
treee3a1fdb6f4ab04323d7cd2748024f7504245a80b
parent9265656a0852b04d4a3b8b2f9c421c85286a4056 (diff)
tools/intel_vbt_decode: Dump MIPI sequences in the order they appear in VBT
Dump the MIPI sequence blocks in the order they appear in the VBT (as opposed to being ordered by the sequence type). This makes it easier to compare the hexdump vs. the decoded output, which is what I tend to do occasionally when trying to check whether we are decoding things correctly or not. Reviewed-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
-rw-r--r--tools/intel_vbt_decode.c7
1 files changed, 2 insertions, 5 deletions
diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
index 38de64f65..1bd3d860b 100644
--- a/tools/intel_vbt_decode.c
+++ b/tools/intel_vbt_decode.c
@@ -2471,12 +2471,9 @@ static void dump_mipi_sequence(struct context *context,
fprintf(stderr, "Invalid sequence %u\n", seq_id);
return;
}
- }
- /* Dump the sequences. Corresponds to sequence execution in kernel. */
- for (int j = 0; j < ARRAY_SIZE(sequence_ptrs); j++)
- if (sequence_ptrs[j])
- dump_sequence(sequence_ptrs[j], sequence->version);
+ dump_sequence(sequence_ptrs[seq_id], sequence->version);
+ }
}
}