On Fri, 21 Feb 2025 10:49:35 +0000, Alessio Belle wrote:
> When firmware traces are enabled, the firmware dumps 48-bit timestamps
> for each trace as two 32-bit values, highest 32 bits (of which only 16
> useful) first.
>
> The driver was reassembling them the other way round i.e. interpreting
> the first value in memory as the lowest 32 bits, and the second value
> as the highest 32 bits (then truncated to 16 bits).
>
> [...]
Applied, thanks!
[1/1] drm/imagination: Fix timestamps in firmware traces
commit: 1d2eabb6616433ccaa13927811bdfa205e91ba60
Best regards,
--
Matt Coster <matt.coster@xxxxxxxxxx>
