From: Mirela Rabulea <mirela.rabulea@nxp.com>
To: "mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>
Cc: dl-linux-imx <linux-imx@nxp.com>,
"s.nawrocki@samsung.com" <s.nawrocki@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vivek.kasireddy@intel.com" <vivek.kasireddy@intel.com>,
"boris.brezillon@collabora.com" <boris.brezillon@collabora.com>,
Robert Chiras <robert.chiras@nxp.com>,
"paul.kocialkowski@bootlin.com" <paul.kocialkowski@bootlin.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"niklas.soderlund+renesas@ragnatech.se"
<niklas.soderlund+renesas@ragnatech.se>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"ezequiel@collabora.com" <ezequiel@collabora.com>
Subject: Re: Re: [PATCH] media: v4l: Add packed YUV444 24bpp pixel format
Date: Thu, 22 Aug 2019 15:00:37 +0000 [thread overview]
Message-ID: <1566486036.21340.20.camel@nxp.com> (raw)
In-Reply-To: <a6b91ccf-8961-d9a9-c007-d113bcba7156@xs4all.nl>
Hi Hans,
On Ma, 2019-08-13 at 08:54 +0200, Hans Verkuil wrote:
>
> This patch looks good, but it can only be merged if we also have a
> driver
> that uses it. This to avoid having lots of pixelformat defines that
> nobody
> is using in the kernel.
>
> Are there plans to upstream this JPEG en/decoder?
>
Apologies for the late response, I was OOO.
Yes, I have plans to send the JPEG encoder/decoder driver upstream, but
I still have failures from v4l2-compliance test. It will take a while
until I will manage to fix those. When I will be ready for upstream, It
would help if this patch would be upstream already, but if it won't, I
can remove the RGB24 support from the driver, and send it later,
together with this patch.
Regards,
Mirela
prev parent reply other threads:[~2019-08-22 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 15:15 [PATCH] media: v4l: Add packed YUV444 24bpp pixel format Mirela Rabulea
2019-07-03 15:15 ` Mirela Rabulea
2019-07-11 8:18 ` Paul Kocialkowski
2019-07-11 13:57 ` Mirela Rabulea
2019-07-12 9:21 ` paul.kocialkowski
2019-07-12 13:02 ` [EXT] " Mirela Rabulea
2019-08-13 6:54 ` Hans Verkuil
2019-08-22 15:00 ` Mirela Rabulea [this message]
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=1566486036.21340.20.camel@nxp.com \
--to=mirela.rabulea@nxp.com \
--cc=boris.brezillon@collabora.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=paul.kocialkowski@bootlin.com \
--cc=robert.chiras@nxp.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@linux.intel.com \
--cc=vivek.kasireddy@intel.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