[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220615204436.137377-1-jernej.skrabec@gmail.com>
Date: Wed, 15 Jun 2022 22:44:34 +0200
From: Jernej Skrabec <jernej.skrabec@...il.com>
To: mripard@...nel.org, paul.kocialkowski@...tlin.com
Cc: mchehab@...nel.org, wens@...e.org, jernej.skrabec@...il.com,
samuel@...lland.org, hverkuil-cisco@...all.nl,
benjamin.gaignard@...labora.com, nicolas.dufresne@...labora.com,
gregkh@...uxfoundation.org, linux-media@...r.kernel.org,
linux-staging@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] media: cedrus: fix HEVC decoding
After detailed comparison of register names to vendor library I noticed
that one register has completely different name. After some testing I
discovered that it was misnamed and used incorrectly. This patch series
fixes it. With that, 3 more reference bitstreams are now correctly
decoded. It is also possible that this fixes instability issue I had
after decoding such bitstreams. Running Fluster test suite very often
locked up my board, but after applying this fix, I never experienced it
again. It might still be completely coincidental, but I doubt this is
the case.
Note: Patch 2 clashes with HEVC uAPI destaging. In current form, it can
be easily backported. However, there are few users of Cedrus HEVC and
skipping this fix wouldn't be that bad.
Please let me know which way to go:
1) wait for destaging, send rebased v2 and not care about backporting
2) merge before destaging, but v9 of HEVC uAPI destaging would need to
be rebased.
3) something else?
Best regards,
Jernej
Jernej Skrabec (2):
media: cedrus: h265: Fix flag name
media: cedrus: h265: Fix logic for not low delay flag
.../staging/media/sunxi/cedrus/cedrus_h265.c | 29 ++++++++++++++++++-
.../staging/media/sunxi/cedrus/cedrus_regs.h | 3 +-
2 files changed, 29 insertions(+), 3 deletions(-)
--
2.36.1
Powered by blists - more mailing lists