From: Ming Qian <ming.qian@nxp.com>
To: mchehab@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
mirela.rabulea@oss.nxp.com
Cc: hverkuil-cisco@xs4all.nl, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] imx-jpeg: Support dynamic resolution change
Date: Fri, 11 Mar 2022 15:51:42 +0800 [thread overview]
Message-ID: <cover.1646983646.git.ming.qian@nxp.com> (raw)
These patchset are to support dynamic resolution change.
Avoid decoding error or even kernel panic.
Otherwise, the Gstreamer v4l2videodec will fail to decode jpeg
who is not decoded to yuyv.
Ming Qian (5):
media: imx-jpeg: Refactor function mxc_jpeg_parse
media: imx-jpeg: Identify and handle precision correctly
media: imx-jpeg: Propagate the output frame size to the capture side
media: imx-jpeg: Handle source change in a function
media: imx-jpeg: Support dynamic resolution change
drivers/media/platform/imx-jpeg/mxc-jpeg.c | 244 ++++++++++++++-------
drivers/media/platform/imx-jpeg/mxc-jpeg.h | 3 +
2 files changed, 169 insertions(+), 78 deletions(-)
--
2.33.0
next reply other threads:[~2022-03-11 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:51 Ming Qian [this message]
2022-03-11 7:51 ` [PATCH 1/5] media: imx-jpeg: Refactor function mxc_jpeg_parse Ming Qian
2022-03-11 7:51 ` [PATCH 2/5] media: imx-jpeg: Identify and handle precision correctly Ming Qian
2022-03-11 7:51 ` [PATCH 3/5] media: imx-jpeg: Propagate the output frame size to the capture side Ming Qian
2022-03-11 7:51 ` [PATCH 4/5] media: imx-jpeg: Handle source change in a function Ming Qian
2022-03-11 7:51 ` [PATCH 5/5] media: imx-jpeg: Support dynamic resolution change Ming Qian
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=cover.1646983646.git.ming.qian@nxp.com \
--to=ming.qian@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).