From: James_Lin <Ping-lei.Lin@mediatek.com>
To: <linux-kernel@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Arnd Bergmann <arnd@arndb.de>,
"Ricardo Ribalda" <ribalda@chromium.org>,
Ming Qian <ming.qian@nxp.com>,
"Andrzej Pietrasiewicz" <andrzej.p@collabora.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
<linux-media@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<ping-lei.lin@mediatek.com>, <lecopzer.chen@mediatek.com>,
<max.yan@mediatek.com>, <sherlock.chang@mediatek.com>,
<tm.wu@mediatek.com>, James_Lin <Ping-lei.Lin@mediatek.com>
Subject: [PATCH v2 0/2] media: Add H265 pixel format
Date: Mon, 11 Apr 2022 16:01:18 +0800 [thread overview]
Message-ID: <20220411080120.26008-1-Ping-lei.Lin@mediatek.com> (raw)
Hi All,
This patch series aims to add H265 pixel format (aka hevc).
High Efficiency Video Coding (HEVC), also known as H.265 and MPEG-H Part 2.
They describe the same video encoding method.
So for handling their behavior is the same.
However, when external camera device describes this encoding method,
some use hevc, some use h265.
There is no uniform specification to describe this encoding method.
So if an external camera device use h265 to describe this encoding method,
driver will not recognize it.
Therefore, this patch series aims to add H265 pixel format
to avoid this situation
James_Lin (2):
media: usb: uvc: Add H265 pixel format
media: v4l: Add H265 pixel format
.../userspace-api/media/v4l/pixfmt-compressed.rst | 10 ++++++++++
drivers/media/usb/uvc/uvc_driver.c | 5 +++++
drivers/media/usb/uvc/uvcvideo.h | 3 +++
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
include/uapi/linux/videodev2.h | 1 +
5 files changed, 20 insertions(+)
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-11 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 8:01 James_Lin [this message]
2022-04-11 8:01 ` [PATCH v2 1/2] media: usb: uvc: Add H265 pixel format James_Lin
2022-04-11 8:11 ` Kieran Bingham
2022-04-11 8:01 ` [PATCH v2 2/2] media: v4l: " James_Lin
2022-04-11 8:12 ` Kieran Bingham
2022-04-11 13:50 ` Nicolas Dufresne
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=20220411080120.26008-1-Ping-lei.Lin@mediatek.com \
--to=ping-lei.lin@mediatek.com \
--cc=andrzej.p@collabora.com \
--cc=arnd@arndb.de \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=max.yan@mediatek.com \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sherlock.chang@mediatek.com \
--cc=tm.wu@mediatek.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