From: ming.qian@oss.nxp.com
To: mchehab@kernel.org, hverkuil-cisco@xs4all.nl, mirela.rabulea@oss.nxp.com
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, xiahong.bao@nxp.com,
eagle.zhou@nxp.com, linux-imx@nxp.com, imx@lists.linux.dev,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] media: imx-jpeg: Fix some motion-jpeg decoding issues
Date: Thu, 27 Mar 2025 10:37:04 +0800 [thread overview]
Message-ID: <20250327023710.549-1-ming.qian@oss.nxp.com> (raw)
From: Ming Qian <ming.qian@oss.nxp.com>
To support decoding motion-jpeg without DHT, driver will try to decode a
pattern jpeg before actual jpeg frame by use of linked descriptors
(This is called "repeat mode"), then the DHT in the pattern jpeg can be
used for decoding the motion-jpeg.
But there is some hardware limitation in the repeat mode, that may cause
corruption or decoding timeout.
Try to make workaround for these limitation in this patchset.
Ming Qian (3):
media: imx-jpeg: Enhance error handling in buffer allocation
media: imx-jpeg: Change the pattern size to 128x64
media: imx-jpeg: Check decoding is ongoing for motion-jpeg
.../media/platform/nxp/imx-jpeg/mxc-jpeg-hw.h | 1 +
.../media/platform/nxp/imx-jpeg/mxc-jpeg.c | 109 +++++++++++++-----
.../media/platform/nxp/imx-jpeg/mxc-jpeg.h | 5 +
3 files changed, 86 insertions(+), 29 deletions(-)
--
2.43.0-rc1
next reply other threads:[~2025-03-27 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 2:37 ming.qian [this message]
2025-03-27 2:37 ` [PATCH 1/3] media: imx-jpeg: Enhance error handling in buffer allocation ming.qian
2025-03-27 14:35 ` Frank Li
2025-03-28 1:22 ` Ming Qian(OSS)
2025-03-27 2:37 ` [PATCH 2/3] media: imx-jpeg: Change the pattern size to 128x64 ming.qian
2025-03-27 2:37 ` [PATCH 3/3] media: imx-jpeg: Check decoding is ongoing for motion-jpeg ming.qian
2025-03-27 14:41 ` Frank Li
2025-03-28 1:30 ` Ming Qian(OSS)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250327023710.549-1-ming.qian@oss.nxp.com \
--to=ming.qian@oss.nxp.com \
--cc=eagle.zhou@nxp.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mirela.rabulea@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiahong.bao@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox